# MCP The AIXBT MCP server gives AI agents direct access to projects, intel, momentum, recipes, and market grounding. It uses the Streamable HTTP transport. ## Connection URL [#connection-url] ``` https://api.aixbt.tech/mcp ``` Two authentication methods are supported: 1. **OAuth 2.1** (recommended for interactive clients like Claude Desktop, Claude.ai, and Claude Code). The client handles login, consent, and token refresh for you. 2. **API key** (recommended for scripts, agents, and SDKs). Generate a key once and pass it on every request. Use OAuth when the client supports it. Fall back to the API key flow when you need fully unattended access. ## OAuth (Recommended) [#oauth-recommended] AIXBT implements the OAuth 2.1 authorization code flow with PKCE, dynamic client registration ([RFC 7591](https://www.rfc-editor.org/rfc/rfc7591)), and resource indicators ([RFC 8707](https://www.rfc-editor.org/rfc/rfc8707)). Most MCP clients that advertise OAuth support will auto-discover the endpoints from the protected resource metadata. You will sign in with your AIXBT account, approve the requested scope, and the client receives a token scoped to `https://api.aixbt.tech/mcp`. Discovery documents: * `https://api.aixbt.tech/.well-known/oauth-protected-resource` * `https://api.aixbt.tech/.well-known/oauth-authorization-server` Connectors installed in Claude.ai or Claude Desktop sync across Claude.ai (web), Claude Desktop, and Claude Code automatically — you only need to add AIXBT in one of them. ### Claude Desktop [#claude-desktop] 1. Open Claude Desktop Settings and navigate to **Connectors** (or **Custom Connectors**). 2. Add a connector with URL `https://api.aixbt.tech/mcp`. 3. Claude Desktop will open a browser window for AIXBT login and consent. Approve the request to complete setup. 4. The connector appears as **AIXBT** in the tool menu after the handshake completes. ### Claude.ai [#claudeai] 1. Open [claude.ai/customize/connectors](https://claude.ai/customize/connectors). 2. Click the **+** icon and choose **Add custom connector**. 3. Enter `https://api.aixbt.tech/mcp` as the URL. 4. Complete the login and consent flow in the browser popup. ### Claude Code [#claude-code] 1. Run `claude mcp add --transport http aixbt https://api.aixbt.tech/mcp` in your terminal. 2. Claude Code launches the browser for AIXBT login and consent. 3. The server shows up in `claude mcp list` once authorized. ### Other OAuth-capable clients [#other-oauth-capable-clients] Any MCP client that supports OAuth via Streamable HTTP can connect by pointing at `https://api.aixbt.tech/mcp` and following the client's custom-server flow. Clients known to work at time of writing: Cursor, VS Code (Copilot Chat), Windsurf. Consult your client's documentation for the exact menu path; the AIXBT side only needs the MCP URL. ## API Key (Programmatic / SDK) [#api-key-programmatic--sdk] Use this path for scripts, agents, CI jobs, or any environment where a browser-based consent flow is not practical. API keys carry the same scopes as OAuth-issued tokens and share the same rate limits. ### Config with Bearer header [#config-with-bearer-header] ```json { "mcpServers": { "aixbt": { "type": "streamable-http", "url": "https://api.aixbt.tech/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } } ``` ### Query-parameter fallback [#query-parameter-fallback] Some clients (including Claude.ai's legacy custom-server flow) do not forward custom headers. Pass the key as a query string instead: ``` https://api.aixbt.tech/mcp?api_key=YOUR_API_KEY ``` Never commit API keys to version control. Use environment variables, a secrets manager, or a short-lived x402 key pass in production. ## Managing Authorized Apps [#managing-authorized-apps] Once you authorize an MCP client via OAuth, it appears in your AIXBT settings under **Connected Apps**. From there you can see when each client last used its token and revoke access at any time. Revocation takes effect immediately and the client will need to run through the consent flow again to regain access. ## Available Tools [#available-tools] | Tool | Description | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | `list_projects` | Search and list projects by name, ticker, chain, momentum | | `get_project` | Get full project details including intel and market data | | `get_momentum` | Hourly momentum history with cluster breakdown | | `get_rank` | Rank position history for a project | | `get_top_climbing` | Projects ranked by climbingScore for 72h attention accumulation | | `list_intel` | Timeline of detected market events with filters | | `list_intel_categories` | List available intel categories | | `list_clusters` | List tracked community clusters | | `list_chains` | List supported blockchain networks | | `get_grounding` | Real-time market context snapshot | | `list_recipes` | Browse the recipe catalog | | `get_recipe` | Get recipe details and parameters | | `run_recipe` | Execute a recipe pipeline | | `validate_recipe` | Validate a recipe YAML before running | | `get_usage_guide` | Detailed usage guide (call this for help) | | `chat_with_aixbt` | Conversational analysis agent. Requires `agents` scope (Pro/Holder); debits one credit per call from the daily chat quota. See [Chat](/builders/chat) | ## Resources [#resources] MCP clients that support resources can access: | URI | Content | | ------------------------------------- | -------------------------------------------------------- | | `aixbt://docs/guide` | Data guide: concepts, query patterns, analysis workflows | | `aixbt://docs/recipe-specification` | Recipe YAML schema | | `aixbt://docs/recipe-building-blocks` | Provider actions and examples | ## Getting Access [#getting-access] See [Getting Started](/builders/getting-started) for access tiers and pricing. Purchase a key pass via [x402](/builders/x402) or subscribe at [aixbt.tech](https://aixbt.tech/subscribe).