# Allium MCP connector

The Allium connector brings on-chain data into Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so your team can run explorer queries, check token prices, and review wallet balances and transactions with each person signed in as themselves.

Source: https://elaichi.ai/connectors/allium/

## Facts

| | |
| --- | --- |
| Application | Allium |
| Category | Analytics |
| AI tools | 90 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Allium is connected

- Show me the latest token price history for ETH.
- Which Allium query runs finished overnight, and their results?
- Search Allium tokens on Polygon and list the top ten.

## Connect Allium in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Allium.
2. Optionally set Share with, then press Connect.
3. Paste an Allium API key. One person generates a token in Allium and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Allium tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Allium MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Allium MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Allium MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Allium MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Allium MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Allium to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a Allium tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Run your connected tools, which can also delete in connected apps and cannot be undone.

## What teams do with Allium through Elaichi

### Run an explorer query in plain language

Research. Ask for the top tokens by transfer volume this week, let the agent start the query run in Allium, wait for it to finish, and read back the results.

### Check treasury wallet balances and holdings

Finance. Pull the current balances for the organization's wallets and see how holdings have shifted over the month before the close.

### Report profit and loss per wallet

Finance. Get realized and unrealized profit and loss for a wallet, along with its history, so a treasury report is ready without a spreadsheet export.

### Trace transfers for a flagged wallet

Compliance. List the transactions and token transfers for a wallet address that came up in a review and summarize the counterparties.

### Look up token prices and price history

Product. Get the current price of a token, its price history over a range, and a quick stat like average or high before a launch decision.

### Review NFT holdings on Polygon

Data. List the Polygon NFTs tied to a collection or wallet and search Allium's token and asset catalog to confirm what they are.

## Elaichi vs Zapier MCP vs Composio for Allium

All three can connect Allium to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Allium tools | Allow or restrict single Allium tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Allium call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Allium to Claude?

Connect Allium in Elaichi first: pick Allium from the catalog and paste in the API key from your Allium account, which is the whole sign-in step. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi, and Allium is available in your next conversation.

### Does Allium work with ChatGPT and Cursor as well as Claude?

Yes. Once Allium is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. You connect Allium once and each client picks it up with the same access and the same audit log.

### What can an AI agent actually do with my Allium data?

An agent connected to Allium can start an explorer query, check its status, and read the results, so you can ask questions about on-chain activity in plain language. It can also look up token prices and price history, search tokens and assets, list token transfers, and pull a wallet's balances, transactions, holdings history, and profit and loss. Because Allium exposes many actions, short concrete asks like "balances for this wallet" work better than long paragraphs.

### Does connecting Allium give the AI everything in my account?

No. Every request to Allium runs with the API key of the person who connected it, so the agent can reach only what that Allium account can already reach. Elaichi can narrow that further with restrictions on specific actions, and it can never widen what the Allium account itself allows.

### Can my team share one Allium connection?

Yes. One person connects Allium with their API key and shares the connection with a team in Elaichi, and nobody else on the team ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log records who ran which Allium query or looked up which wallet.

### Can I stop an agent from deleting or changing things in Allium?

Yes. Restrictions in Elaichi apply per action, so you can allow reading token prices and wallet balances while restricting anything that cancels a query run or starts long-running jobs in Allium. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

### What happens to an Allium connection when someone leaves?

When you offboard someone in Elaichi, their access to Allium through every connected client ends at once. If they shared an Allium connection with a team, it keeps working for everyone else, and you can rotate the API key when you are ready. Disconnecting Allium once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.

### Does the Allium MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Allium is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Allium?

Yes. Both let Claude, ChatGPT or Cursor use Allium. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Allium call.

### How is Elaichi different from Composio for Allium?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Allium: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 90 Allium tools

Every tool below is callable through https://api.elaichi.ai/mcp once Allium is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Allium querie run** (Create). Execute a saved allium query by its query_id and return the results. The request body is a free-form JSON object that maps query parameter names to string values; the required keys depend on the saved query's parameter definitions. Returns query execution results as a dynamic payload whose schema depends on the query's column definitions. Required: query_id.
- **Create a Allium querie run async** (Create). Execute an Allium Explorer query asynchronously and receive a run identifier for polling results. Returns: run_id. Required: query_id.
- **List all Allium explorer query runs** (List). Get the latest query run for a given query in allium. Returns: run_id, query_id, query_config, creator_id, created_at, completed_at, status, stats, error, results, zed_token. Required: query_id.
- **Allium explorer query runs cancel** (Search). Cancel a running query run in allium by run_id. Returns a 200 response on success; the response body structure is not enumerated by the source. Required: run_id.
- **List all Allium query run status** (List). Get the current execution status of an Allium Explorer query run. Returns a status string indicating the run's progress — one of: created, queued, running, success, failed, or canceled. Required: run_id.
- **List all Allium query run results** (List). List results of a completed Allium Explorer query run. Returns: sql, data, meta, queried_at, run_id. Required: run_id.
- **List all Allium polygon nfts** (List). List NFTs on the Polygon blockchain via Allium. Returns: id, created_at, updated_at.
- **List all Allium pings** (List). List pings in allium. Returns: id, name, created_at, updated_at.
- **Create a Allium token price** (Create). Fetch the latest price and OHLC values for a list of tokens in allium. Returns an items array with each token's timestamp, chain, address, price, open, high, close, low, and decimals, plus a cursor and message. Required: a request body array of token_address and chain pairs (up to 200 tokens).
- **Get single Allium token price by ID** (Get). Get token prices at or before a specific timestamp in allium, falling back to the closest prior price when no exact match exists. Returns an items array with input_timestamp, price_timestamp, mint, chain, and price per token, plus a cursor and message. Required: addresses, timestamp, time_granularity.
- **Create a Allium token price history** (Create). Fetch historical OHLC price data in allium for up to 50 token/chain pairs over a specified time window. Returns items containing mint, chain, decimals, and a prices array with timestamp, price, open, high, close, and low values; also returns cursor and message. Required: addresses, start_timestamp, end_timestamp, time_granularity.
- **Create a Allium token price stat** (Create). Fetch token price statistics for up to 200 tokens in allium based on on-chain DEX activity. Returns: filter. Required: a request body array with token_address and chain per token entry. Maximum 200 tokens per request.
- **List all Allium tokens** (List). List the top allium tokens ordered by a specified metric. Returns: chain, address, object, price, decimals, info, attributes. Supports optional filtering by chain and minimum volume thresholds.
- **Allium tokens search** (Search). Search allium tokens by keyword matched case-insensitively against token name and symbol. Returns: chain, address, object, price, decimals, info, attributes. Required: q.
- **Get single Allium token by ID** (Get). Fetch detailed token data in allium for one or more specific token addresses by supplying an array of chain/address pairs. Returns: object, allocation_amounts, consumed_amounts. Required: token_address, chain (per array item). Accepts 1–200 pairs per request.
- **List all Allium token transfers** (List). List token transfers in allium for a given blockchain chain. Returns records including block_slot, block_height, block_timestamp, txn_id, from_account, to_account, from_token_account, to_token_account, mint, value, decimals, and signer. Required: chain. transfer_type filter can only be used when address is also specified.
- **List all Allium assets** (List). List assets in Allium. Returns a paginated collection of asset records; each item includes id, slug, source, name, symbol, image_url, circulating_supply, chain_specific_data, and token_creation_time. No required parameters.
- **Get single Allium asset by ID** (Get). Get a batch of assets in Allium by ID, slug, or chain and address. Returns an array of asset records each with id, slug, source, name, symbol, image_url, circulating_supply, chain_specific_data, and token_creation_time. Supply at least one lookup field per item in the request body.
- **Create a Allium wallet balance** (Create). Fetch the latest fungible token balances for one or more wallet addresses across supported chains in Allium. Returns: address, block_hash, block_number, block_timestamp, chain, raw_balance, raw_balance_str, token. Required: array body with chain and address per entry. Accepts 1–100 wallet entries per request.
- **Create a Allium wallet balance history** (Create). Fetch historical fungible token balances for up to 5 wallet addresses in allium. Returns balance records including address, block_hash, block_slot, block_timestamp, chain, raw_balance, raw_balance_str, token, txn_id, and txn_index. Required: addresses, start_timestamp, end_timestamp.
- **Create a Allium wallet transaction** (Create). Fetch wallet transactions in allium for one or more wallet address and chain pairs, supporting up to 20 wallets per request. Returns items containing each transaction's id, hash, chain, block_timestamp, fee, from_address, to_address, asset_transfers, and activities, plus a cursor for pagination. Required: request body array with chain and address per wallet.
- **Create a Allium wallet holdings history** (Create). Fetch historical USD holdings value for wallet addresses in allium, returning aggregated snapshots at regular time intervals sorted by timestamp descending. Returns: filter. Required: addresses, start_timestamp, end_timestamp, granularity. Accepts 1–15 address/chain pairs per request; the finest allowed granularity depends on the requested time range.
- **Create a Allium wallet pnl** (Create). Fetch current PnL metrics for one or more wallet addresses in allium. Returns: filter. Accepts 1–20 wallet/chain pairs per request. Required: array body with chain and address for each entry.
- **Create a Allium wallet pnl history** (Create). Fetch historical realized and unrealized PnL for wallet addresses in Allium over a specified time range and granularity. Returns: filter. Required: addresses, start_timestamp, end_timestamp, granularity. Addresses array is limited to 1–20 entries; allowed granularity depends on the requested time range.
- **Create a Allium wallet pnl by token** (Create). Fetch current PnL metrics for specific wallet and token address combinations in allium. Returns data and items each containing chain, address, token_address, current_tokens, current_balance, current_price, unrealized_pnl, realized_pnl, average_cost, unrealized_pnl_ratio_change, attributes, and historical_breakdown per token. Required: chain, address, token_address per item. Accepts an array of…
- **Create a Allium wallet pnl by token history** (Create). Fetch historical PnL breakdown by token for one or more wallets in allium. Returns data and items arrays each containing chain, address, token_address, and a pnl array of timestamped unrealized_pnl and realized_pnl entries, plus error and cursor. Required: addresses (1–20 wallet/chain/token triples), start_timestamp, end_timestamp, granularity.
- **Create a Allium wallet position** (Create). Fetch DeFi wallet positions in allium for up to 5 address/chain pairs in a single request. Returns items (a list of positions with position_id, position_type, protocol, address, chain, total_value_usd, token0, token1, and unclaimed_fees_usd), cursor, and total. Required: chain and address for each entry in the request array.
- **Create a Allium hyperliquid fill** (Create). Fetch fill data for a Hyperliquid user address in Allium. Returns an array of fill records including closedPnl, coin, hash, oid, px, side, sz, time, fee, feeToken, tid, liquidation, builderFee, builderAddress, and twapId. Required: type, user. Note: startTime is required when type is userFillsByTime.
- **Create a Allium hyperliquid order history** (Create). Fetch historical order data for a Hyperliquid user address via Allium. Returns an array of order records each containing order (with coin, side, limitPx, sz, oid, orderType, tif, cloid, and more), status, and statusTimestamp. Required: type, user. The interval between startTime and endTime cannot exceed 30 days; omit both to retrieve the most recent orders.
- **Create a Allium hyperliquid order status** (Create). Get order status information for a Hyperliquid user address. Returns the order object (including coin, side, limitPx, sz, oid, orderType, tif, and cloid), along with status and statusTimestamp. Required: type, user, oid.
- **List all Allium hyperliquid orderbook** (List). List all Hyperliquid orderbook snapshots across every trading pair with approximately 5-second data freshness. Returns an array of per-pair snapshots; each snapshot includes pair (trading pair identifier) and book_orders (two-element array of bids at index 0 and asks at index 1), where every order entry contains coin, side, limitPx, sz, oid, timestamp, orderType, tif, reduceOnly, origSz,…
- **Create a Allium hyperliquid event** (Create). Retrieve Hyperliquid user event history from Allium, returning funding payments or non-funding ledger updates for a given wallet address. Returns an array of event objects each containing time (Unix ms timestamp), hash (transaction hash), and a delta payload with type-specific fields such as coin, usdc, szi, and fundingRate. Required: type, user.
- **List all Allium markets** (List). List allium markets with optional filters by venue, instrument type, base/quote asset, and active status. Returns: market_id, venue, base_asset, quote_asset, settlement, active, tick_size, contract_size, perp.
- **Allium markets search** (Search). Search allium markets by free-text query for ticker lookups and symbol disambiguation across venues and instrument types. Returns: market_id, venue, match_type. Required: q (max 1024 characters).
- **Get single Allium market by ID** (Get). Get a single allium market by id. Returns `data`, the full market reference object, including market_id, venue, base_asset, quote_asset, settlement, active, tick_size, contract_size, and perp funding metadata. Required: id.
- **List all Allium market prices** (List). Get the latest price snapshot for a market in allium. Returns: market_id, as_of, mark, index, mid. Required: market_id, instrument (either `perps` or `spot`, consistent with the market_id). Snapshots are cached for ~60 seconds.
- **List all Allium market ohlcv** (List). List historical OHLCV candles for a market in allium. Returns: market_id, open_time, close_time, open, high, low, close, volume, trade_count. Required: market_id, interval, start_timestamp, end_timestamp. Query window is capped at 7 days per request.
- **List all Allium market funding** (List). List historical funding rates for a perpetual market in allium, collapsed into hourly buckets. Returns: market_id, ts, funding_rate, premium_index, interval_seconds. Required: market_id, start_timestamp, end_timestamp. Query window is capped at 7 days per request.
- **List all Allium market open interest** (List). List open interest timeseries for a perpetual market in allium. Returns: market_id, ts, oi_base, oi_quote_usd. Required: market_id, interval, start_timestamp, end_timestamp. Query window is capped at 7 days per request.
- **List all Allium market liquidations** (List). List historical liquidation events for a perpetual market in allium, returned newest first. Returns: market_id, ts, size_base, price, notional_usd, side. Required: market_id, start_timestamp, end_timestamp. Query window is capped at 7 days per request.
- **List all Allium organization usage** (List). Get your Allium organization's current unit usage for the active billing and allocation period. Returns: billing_period_start, billing_period_end, allocation_period_start, allocation_period_end, allocation_cadence, allocation_amounts, consumed_amounts.
- **List all Allium beam configs** (List). List all allium Beam pipeline configurations accessible to the authenticated user. Returns an array of BeamConfig objects, each including id, name, description, pipeline_config, owner_org_team_user_id, organization_id, tags, static_egress_ip, pod_size, created_at, and updated_at.
- **Create a Allium beam config** (Create). Create a new allium Beam pipeline configuration. Returns the created BeamConfig including id, name, description, owner_org_team_user_id, pipeline_config, organization_id, created_at, updated_at, tags, static_egress_ip, and pod_size. Required: name, description, pipeline_config.
- **Get single Allium beam config by ID** (Get). Get a single allium Beam pipeline configuration by id. Returns the full BeamConfig object including id, name, description, pipeline_config, owner_org_team_user_id, organization_id, created_at, updated_at, tags, static_egress_ip, and pod_size. Required: id.
- **Update a Allium beam config by ID** (Update). Update an existing allium Beam pipeline configuration by id. Returns the updated BeamConfig including id, name, description, owner_org_team_user_id, pipeline_config, organization_id, created_at, updated_at, tags, static_egress_ip, and pod_size. Required: id, name, description, owner_org_team_user_id, pipeline_config.
- **Delete a Allium beam config by ID** (Delete). Delete an allium Beam pipeline configuration by id, permanently removing the config and tearing down all active deployment resources including Kafka topics, workers, and subscriptions. Returns: message. Required: id.
- **List all Allium beam sources** (List). List all available Allium Beam pipeline sources — the catalog of chain/entity combinations that can be used as a Beam pipeline input. Returns: chain, entity, is_zerolag. Optionally filter by chain, entity, or zerolag.
- **Create a Allium beam deployment** (Create). Deploy an Allium Beam pipeline config, creating Kafka topics, provisioning credentials, and spinning up workers. Deployment is idempotent — safe to call again after updating a config to apply changes with zero downtime. Returns: message. Required: config_id.
- **Delete a Allium beam deployment by ID** (Delete). Tear down a deployed Allium Beam pipeline, removing workers, Kafka topics, and subscriptions while preserving the pipeline config for future redeployment. Returns: message. Required: config_id.
- **List all Allium beam deployment stats** (List). Get deployment stats for an Allium Beam pipeline configuration. Returns workers_health containing total_workers, healthy_workers, unhealthy_workers, crashing_workers, oom_killed_workers, and a workers array with per-worker fields including name, status, is_ready, is_crash_looping, is_oom_killed, restart_count, and start_time. Required: config_id.
- ...and 40 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
