Documentation
How to connect your AI client to MCP.city.
Quick Start
MCP.city uses the Model Context Protocol (MCP) over Streamable HTTP.
1. Get the endpoint
https://mcp.city/v1/mcp
2. Connect with Devin CLI
mcp login https://mcp.city/v1/mcp
3. List available tools
tools/list
4. Call a tool
tools/call bitbeam__identity.whoami
Authentication
MCP.city uses OAuth 2.1 with PKCE.
OAuth Discovery
https://mcp.city/.well-known/oauth-authorization-server
Dynamic Client Registration
POST https://mcp.city/mcp/oauth/register
Authorize
https://mcp.city/mcp/oauth/authorize
Token
https://mcp.city/mcp/oauth/token
JWKS
https://mcp.city/mcp/oauth/jwks
Server Card
The MCP server card describes the endpoint:
https://mcp.city/.well-known/mcp.json
Example response
{
"version": "1.0",
"protocolVersion": "2025-11-25",
"serverInfo": {
"name": "bitbeam",
"title": "BitBeam Capability Marketplace"
},
"transport": {
"type": "streamable-http",
"url": "https://mcp.city/v1/mcp"
}
}
Access Tiers
| Tier | Access |
|---|---|
| Free | tools/list, ping, initialize, public tools |
| OAuth | Tenant-scoped tools/call (RBAC) |
| x402 | Premium per-call tools (USDC) |
| License | Subscription tiers bypass x402 |
REST API
BitBeam REST API is also available alongside MCP:
https://mcp.city/wp-json/bitbeam/v1/
Key endpoints
GET /wp-json/bitbeam/v1/identity
GET /wp-json/bitbeam/v1/providers
GET /wp-json/bitbeam/v1/features
POST /wp-json/bitbeam/v1/auth/token
GET /wp-json/bitbeam/v1/organizations
POST /wp-json/bitbeam/v1/sites/register