Overview

The MCP Server lets your AI agents query blockchain data using structured tool calls—no REST or custom glue code required. Agents can run saved Explorer queries, execute raw SQL, and introspect Allium schemas via the Model Context Protocol (MCP). Endpoint: https://mcp.allium.so

What is MCP?

The Model Context Protocol (MCP) is an open standard that enables AI applications to securely access external data sources and tools. Allium’s MCP Server provides your AI agents with direct access to blockchain data across 80+ chains, with structured tool calls that eliminate the need for custom REST API integrations.

Key Benefits

Structured Tool Calls

No REST API glue code needed—agents use standard MCP tool calls

Schema Discovery

Semantic search and introspection of Allium’s data schemas

Universal Compatibility

Works with any MCP-compatible agent framework

Production Ready

Reliable access to Allium’s enterprise-grade blockchain data

Authentication

All tools require an API key via HTTP header:

X-API-KEY: <your-api-key>

Generate and manage API keys at app.allium.so/settings/api-keys.

Client Setup

Run this command to add Allium MCP globally:

claude mcp add --scope user --transport http allium https://mcp.allium.so --header "X-API-KEY: <your-api-key>"

Then restart Claude Code.

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

{
  "mcpServers": {
    "allium": {
      "url": "https://mcp.allium.so",
      "headers": {
        "X-API-KEY": "<your-api-key>"
      }
    }
  }
}

Then restart Cursor.

Add the server:

codex mcp add allium --url https://mcp.allium.so

Then add your API key to ~/.codex/config.toml:

[mcp_servers.allium]
url = "https://mcp.allium.so"
http_headers = { "X-API-KEY" = "<your-api-key>" }

Then restart Codex.

{
  "tools": [
    {
      "name": "explorer_run_query",
      "server": "https://mcp.allium.so",
      "headers": {
        "X-API-KEY": "<YOUR_API_KEY>"
      }
    },
    {
      "name": "explorer_run_sql",
      "server": "https://mcp.allium.so",
      "headers": {
        "X-API-KEY": "<YOUR_API_KEY>"
      }
    }
  ]
}

Add explorer_fetch_schema and explorer_search_schemas the same way. You can also add any of the Realtime API tools.

For streamable-http or other CLI-based setups:

{
  "mcpServers": {
    "allium": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.allium.so",
        "--header",
        "X-API-KEY:${API_KEY}"
      ],
      "env": {
        "API_KEY": "<your-api-key>"
      }
    }
  }
}

This enables local agent tool streaming with auth injected from environment variables.

Configure your MCP client to connect to https://mcp.allium.so with the X-API-KEY header set to your API key.Most MCP clients support HTTP transport with custom headers. Refer to your client’s documentation for specific configuration details.

Tools Reference

Detailed documentation for all MCP tools

Examples

Real interaction transcripts

Run Queries

Learn how to save queries in Explorer and obtain a query ID

Explorer API

REST endpoints for running queries and retrieving results

Use Cases

Allium Intelligence

Allium App

Allium Datashares

Allium Datastreams

What is MCP?

Key Benefits

Structured Tool Calls

Schema Discovery

Universal Compatibility

Production Ready

Authentication

Client Setup

Tools Reference

Examples

Run Queries

Explorer API

Use Cases

Allium Intelligence

Allium App

Allium Datashares

Allium Datastreams

​What is MCP?

​Key Benefits

Structured Tool Calls

Schema Discovery

Universal Compatibility

Production Ready

​Authentication

​Client Setup

​Related Resources

Tools Reference

Examples

Run Queries

Explorer API

What is MCP?

Key Benefits

Authentication

Client Setup

Related Resources