Allium MCP

Overview

Allium MCP is an official, API-key-gated MCP server run by Allium Labs at mcp.allium.so. It exposes tools to run and manage Explorer SQL queries, fetch and search schemas, and access Allium's Realtime API, covering enterprise blockchain data infrastructure across 80+ chains. An agent builder plugs it in to pull structured, queryable on-chain data instead of building its own indexing pipeline; requires an Allium API key from app.allium.so.

Tool inventory — 48 tools, probed live 2026-08-30

• search_docs — Search Allium's public documentation (https://docs.allium.so). Use this tool when you need: - Information about blockchain data tables and schemas - Details about Allium's data models (DEX, NFT, DeFi
• browse_docs — Browse Allium's public documentation hierarchy like a filesystem. The documentation is organized hierarchically. Every directory contains an `_index.md` file that lists its contents with descriptions
• search_schemas — Search schemas or fetch one schema entry by id. `query` runs the chosen `search_mode` against the prebuilt schema index. `id` fetches a single entry by its dotted table id (e.g. `ethereum.public.tran
• search_terminal — Search Allium's public Terminal dashboards (app.allium.so/terminal). Returns ranked dashboard discovery hits — label, path, category, status, tags, and (optionally) the full rendered dashboard markdo
• get_terminal_results — Fetch SQL or latest precomputed result rows for one Terminal dashboard chart. Use search_terminal first to find a dashboard id, then call get_terminal_results without chart_id for the chart manifest.
• run_sql_query — Run an ephemeral, throwaway SQL query on Allium's blockchain data. **Call `get_skill(name="sql-optimization")` before writing or running any SQL.** Use ONLY when the result is not reused — inspectin
• get_query_run_results — Retrieve results of a query run by its run_id. Use this for both ad-hoc SQL queries, or a saved Explorer query run. Returns the query run status, and if the run succeeded, the result data, columns, r
• create_explorer_query — Create and save a SQL query in the user's Allium Explorer. **Call `get_skill(name="sql-optimization")` before writing or running any SQL.** The DEFAULT path whenever the result will be reused — visu
• get_explorer_query — Retrieve a saved Explorer query by ID. Returns the full SQL, row limit, template parameters, tags, URL, and latest result field metadata when available. Use this to inspect a query before editing or
• update_explorer_query — Update an existing Explorer query. Requires query_id. Only provide fields you want to change - others will be preserved.
• list_explorer_queries — List user's saved Explorer queries with field metadata and tags. Use the tags parameter to filter queries by tag (e.g., to find all queries tagged for a specific dashboard or topic).
• run_explorer_query — Run an existing saved Explorer query by ID. Queues the query for execution and returns a run_id. Use get_query_run_results to wait for results or for a non-blocking status check.
• delete_explorer_query — Permanently delete an Explorer query by ID.
• create_explorer_visual — Create or replace a visual on an existing Allium Explorer query. Visuals are persisted to the caller's account and render on the query page; the returned `url` deep-links to the visual this call wrote
• get_explorer_visual — Read one visual saved on an Allium Explorer query, including its full `spec`. Use this to tweak a field of an existing visual, or to match its style in a new one — get_explorer_query lists a query's
• delete_explorer_visual — Delete one visual from an Allium Explorer query. The query and its other visuals are untouched. Get the `visual_id` from get_explorer_query's `visuals`. Editor permission on the query is required, an
• share_explorer_query — Share an Explorer query publicly and return shareable + embeddable links. What gets shared depends on `visual_id`: - omitted: the query. The shared page shows the results table plus a tab per saved
• list_compute_profiles — List the organization's Explorer compute profiles, each with its current query-queue depth. Each compute profile maps to a dedicated Snowflake warehouse (sized as a speed multiplier - "1x", "2x", "4x
• share_dashboard — Share a dashboard publicly and return a shareable link. Returns a URL of the form https://app.allium.so/s/dashboard/{share_id}. Idempotent: if the dashboard already has a public share, the existing
• read_dashboard — Inspect a dashboard at any depth. Pass `dashboard_id` alone for a root summary (name, settings, list of pages). Add `page_id` / `section_id` / `element_id` to drill down — each level returns the targ
• set_dashboard — Upsert or delete any node in a dashboard tree. Call get_skill(name='dashboard-design') first — it covers the build order, element catalog, layout, and design/SQL rules. For an element, `config.type`
• delete_dashboard — Delete an entire dashboard, including every page, section, and element inside it. This is irreversible. Confirm with the user which dashboard before calling, and read_dashboard first if you are unsur
• list_skills — List available Allium skill guides and their descriptions. Returns skills the authenticated user has access to. Each skill provides in-depth guidance on a specific topic — use get_skill to retrieve t
• get_skill — Get the full instructions for a specific skill. Use this for detailed guidance on how to perform a task. If the skill has reference files, they are listed at the end by title; fetch one by calling th
• realtime_get_supported_chains — Check which blockchain chains each realtime /developer/ endpoint supports. **Call this ONCE per session** before making any realtime tool calls (prices, wallets, etc.) or using the realtime APIs in g
• realtime_token_latest_price — Get the latest price for the given token addresses and chains. Before calling, use browse_docs with path 'api/developer/prices/token-latest-price.md' for detailed docs on supported chains, edge cases,
• realtime_token_price_history — Get the price history for the given token and the given time granularity. Before calling, use browse_docs with path 'api/developer/prices/token-price-history.md' for detailed docs on supported chains,
• realtime_token_price_stats — Get tokens price stats like volume, high and low, price and volume change. Before calling, use browse_docs with path 'api/developer/prices/token-price-stats.md' for detailed docs on supported chains,
• realtime_token_price_at_timestamp — Price of a token at a given timestamp. Before calling, use browse_docs with path 'api/developer/prices/token-price-at-timestamp.md' for detailed docs on supported chains, edge cases, and response form
• realtime_latest_token_balances — Fetch the latest fungible token balances for wallet addresses across supported chains, optionally including liquidity totals. Before calling, use browse_docs with path 'api/developer/wallets/latest-to
• realtime_historical_token_balances — Fetch paginated historical fungible token balances for wallet addresses over a requested time range. Before calling, use browse_docs with path 'api/developer/wallets/historical-token-balances.md' for
• realtime_get_positions — Retrieve DeFi positions for a wallet across multiple protocols and chains Before calling, use browse_docs with path 'api/developer/defi-positions/get-positions.md' for detailed docs on supported chain
• realtime_transactions — Get rich transaction activity data for wallets, including activities, asset transfers, and labels. Before calling, use browse_docs with path 'api/developer/wallets/transactions.md' for detailed docs o
• realtime_list_tokens — List tokens, optionally sorted by a field. Before calling, use browse_docs with path 'api/developer/tokens/list-tokens.md' for detailed docs on supported chains, edge cases, and response format.
• realtime_search_tokens — Search tokens with a query string. Before calling, use browse_docs with path 'api/developer/tokens/search-tokens.md' for detailed docs on supported chains, edge cases, and response format.
• realtime_get_tokens_by_chain_address — Get token details for the given token addresses and chains. Before calling, use browse_docs with path 'api/developer/tokens/get-tokens-by-chain-address.md' for detailed docs on supported chains, edge
• realtime_holdings_history — Get historical aggregated USD holdings for one or more addresses. Before calling, use browse_docs with path 'api/developer/holdings/holdings-history.md' for detailed docs on supported chains, edge cas
• realtime_holdings_pnl — Get the PnL for a given wallet address. Before calling, use browse_docs with path 'api/developer/holdings/holdings-pnl.md' for detailed docs on supported chains, edge cases, and response format.
• realtime_holdings_pnl_history — Get the Historical PnL for a given wallet address. Before calling, use browse_docs with path 'api/developer/holdings/holdings-pnl-history.md' for detailed docs on supported chains, edge cases, and res
• realtime_holdings_pnl_by_token — Get the PnL for a given wallet and token address. Before calling, use browse_docs with path 'api/developer/holdings/holdings-pnl-by-token.md' for detailed docs on supported chains, edge cases, and res
• realtime_holdings_pnl_by_token_history — Get the Historical PnL for a given wallet address and token address. Before calling, use browse_docs with path 'api/developer/holdings/holdings-pnl-by-token-history.md' for detailed docs on supported
• realtime_info — Query Hyperliquid account, market, and exchange information by request type through Allium's rate-limit-free proxy. Before calling, use browse_docs with path 'api/developer/hyperliquid/info.md' for de
• realtime_fills — Endpoint providing fills by user address Before calling, use browse_docs with path 'api/developer/hyperliquid/fills.md' for detailed docs on supported chains, edge cases, and response format.
• realtime_order_history — Endpoint providing order history by user address Before calling, use browse_docs with path 'api/developer/hyperliquid/order-history.md' for detailed docs on supported chains, edge cases, and response
• realtime_order_status — Endpoint providing order status by user address Before calling, use browse_docs with path 'api/developer/hyperliquid/order-status.md' for detailed docs on supported chains, edge cases, and response fo
• realtime_orderbook_snapshot — Get complete orderbook snapshot for all pairs. Before calling, use browse_docs with path 'api/developer/hyperliquid/orderbook-snapshot.md' for detailed docs on supported chains, edge cases, and respon
• realtime_list_assets — List assets. Before calling, use browse_docs with path 'api/developer/assets/list-assets.md' for detailed docs on supported chains, edge cases, and response format.
• realtime_get_assets — Get assets by ID, slug, or (chain, address). Before calling, use browse_docs with path 'api/developer/assets/get-assets.md' for detailed docs on supported chains, edge cases, and response format.

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality.

Where Allium MCP fits

Related concepts: What Are MCPs? The Standard Way to Give Agents Tools, What Are Onchain Agents?