MCP Tools
Overview
Belong CheckIn's AI assistant acts through MCP (Model Context Protocol) tools to create NFT collections, manage events, and run venue operations. The public assistant connector and the backend MCP intentionally use different auth models.
- Public assistant MCP:
https://join.belong.net/functions/v1/belong-agent-mcp/mcp(OAuth 2.1 with email-code sign-in) - Backend MCP:
https://api.belong.net/mcp(trusted integrations only, authenticate withx-api-key) - Setup: see MCP Integration
- Backend tool reference: the MCP Cheat Sheet documents the API-key backend MCP tools
The public assistant MCP is the safe external connector: it uses scoped OAuth tokens, audit logging, and Belong confirmation links for wallet or payment operations. The backend MCP exposes lower-level API and transaction primitives and should stay inside trusted server-side or first-party contexts.
56) is the default network; the EVM order is BSC → Polygon → SKALE → Base → Ethereum.LONG token vs. token gating
Two separate systems power the platform — don't conflate them:
- $LONG token (BEP-20 on BNB Chain) powers CheckIn rewards: promoter rewards, venue marketing budgets, and user spend rewards.
- Token gating uses NFT collections for event ticketing and access control — users must hold a specific NFT to gain entry.
Tool categories
| Category | Representative tools | Reference |
|---|---|---|
| CheckIn | Backend venue deposit and customer payment primitives | CheckIn Tools |
| EVM NFT collections | deploy, complete, evm-mint, mint-complete | Minting Tools |
| Sequential NFT (Sui) | publish-collection → create-collection → save-collection | Minting Tools |
| Sponsored collections | create-sponsored-collection (gasless) | Sponsored Gas |
| Vesting | deploy-vesting-wallet (LONG, cliff + linear) | Vesting Tools |
| Events | create-event, update-event | Events Tools |
| Media | add-event-media, reorder-event-media | — |
| StarkNet | StarkNet-specific minting | StarkNet Tools |
The sequential NFT workflow
Creating a collection runs a three-step workflow that the platform triggers automatically when publish-collection is called with collection data:
flowchart LR;
A[publish-collection<br/>prepare tx] --> B[create-collection<br/>execute on chain]
B --> C[save-collection<br/>persist to backend]
C --> D[Collection ready]
style A fill:#e1f5fe
style D fill:#c8e6c9
Each step streams real-time status (Step 1/3 … 3/3) over Server-Sent Events, with per-step error handling.
Choosing EVM vs. Sui
- Use EVM (BSC) for LONG token operations, token-gated events, and default NFT collections
- Use Sui only when explicitly requested or when the user's blockchain preference is set to Sui
Related
- MCP Cheat Sheet — backend API-key MCP tools with parameters
- MCP Integration — connect a client
- Event Creation — the user-facing flow these tools drive