Discover MCP servers and set up connections.
Browse Available Servers
1# List all servers2belt mcp list34# Filter by category5belt mcp list --category developer6belt mcp list --category productivity78# Show only featured servers9belt mcp list --featured1011# Search by name or description12belt mcp search "slack"13belt mcp search "issue tracking"Output shows slug, category, auth type, connection status, and description:
1mcp servers2slug category auth status description3linear developer oauth connected Project management and issue tracking4slack communication oauth — Team messaging and notifications5github developer oauth — Code hosting and collaborationGet Server Details
1belt mcp get linear1Linear23Project management and issue tracking45 slug linear6 category developer7 auth oauth8 server https://mcp.linear.app9 docs https://linear.app/docs/mcp10 status connected1112 tools: belt mcp tools linearConnect
When you connect with a bare origin URL (for example https://mcp.example.com), the platform resolves the actual MCP endpoint before OAuth:
- Server card —
GET /.well-known/mcp-server-card(MCP remote discovery) - UCP —
GET /.well-known/ucpwhen the server advertises an MCP transport (Universal Commerce Protocol)
You can paste either the origin or the full MCP URL. The workspace and API use the same resolution when you provide server_url in a connect request.
OAuth Servers
Most connectors use OAuth. The CLI opens your browser to authorize:
1belt mcp connect linear1Authorize Linear:23https://linear.app/oauth/authorize?client_id=...&scope=...45Waiting for authorization...67Connected to Linear8 tools: belt mcp tools linearThe flow:
- CLI opens your browser to the service's authorization page
- You approve the requested permissions
- Tokens are exchanged and stored encrypted on your team
- CLI confirms the connection
When you connect a custom MCP server URL (not a pre-registered slug), the API resolves the endpoint before OAuth:
- Server Card (SEP-2127) — if the URL is a bare origin (e.g.
https://mcp.example.com),GET /.well-known/mcp-server-cardmay redirect to the real MCP endpoint. - UCP discovery — if still a bare origin,
GET /.well-known/ucpis checked for a transport with"transport": "mcp"and anendpointURL (Universal Commerce Protocol merchants).
You do not need to discover endpoints manually; pass the merchant or vendor origin and the platform follows redirects to the MCP URL.
REST discovery proxy (for custom UIs; avoids browser CORS on redirects):
1GET https://api.inference.sh/mcps/discover?url=https://mcp.example.comRequires authentication. The API tries /.well-known/mcp-server-card, then OAuth metadata on the URL. Returns the server card or OAuth discovery JSON with Cache-Control: public, max-age=300. Use the same URL shapes as when connecting via CLI or workspace.
API Key Servers
Some servers use API keys instead of OAuth. The key is stored as an encrypted secret.
No-Auth Servers
Public servers that don't require credentials connect immediately.
Custom server URLs
The directory covers known servers (belt mcp connect linear). To connect an arbitrary HTTPS MCP server, use Settings → MCP servers in the web app, or POST /integrations with provider: "mcp" and metadata.server_url set to the server URL.
When server_url is a bare origin (scheme + host, path / or empty), the API resolves the actual MCP endpoint before OAuth:
- MCP server card —
GET /.well-known/mcp-server-card(SEP-2127); uses the firstremotes[].urlwhen present. - UCP discovery —
GET /.well-known/ucp; uses the first service transport with"transport": "mcp"and a non-emptyendpoint.
If discovery fails, the original URL is used. Paste the full MCP path when you already know it (for example https://mcp.linear.app).
Check Connection Status
Connection status is shown in belt mcp list and belt mcp get:
| Status | Meaning |
|---|---|
| connected | Active, ready to use |
| — | Not connected |
Disconnect
Revoke a connection and delete stored credentials:
1belt mcp disconnect slack1Disconnected from SlackNext
- Using Tools — call tools on connected servers
- Agent Tools — add connector tools to your agents