Skip to content

Allium MCP connector

The Allium connector brings on-chain data into Claude, ChatGPT, Cursor, 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.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Allium to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Allium once

  1. Open Connections, choose Add connection, and pick Allium.

  2. Optionally set Share with to give a team access, 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.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

allium
Allium
Amplitude
Artie
AthenaHQ
Botify
CallRail
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Allium MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

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

Allium MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Connect Allium to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Use cases

What teams do with Allium through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Research

    Run an explorer query in plain language

    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.

  • Finance

    Check treasury wallet balances and holdings

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

  • Finance

    Report profit and loss per wallet

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

  • Compliance

    Trace transfers for a flagged wallet

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

  • Product

    Look up token prices and price history

    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.

  • Data

    Review NFT holdings on Polygon

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

Try asking

  • “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.”

See all 90 Allium tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Allium, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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 $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Allium tools for your AI agents

90 tools are ready to call through Elaichi's MCP endpoint the moment you connect Allium, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Allium gets you

6 screens from the product, each doing one job for your Allium account.

The agent

Ask about token prices, read live answers.

Type a question in plain language and Elaichi answers from live Allium query runs.

  • query runs
  • tokens
  • token prices
  • nfts

Ask Elaichi to work across your apps.

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.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Allium together.

One governed MCP endpoint over OAuth, no SDK to build and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

All 90 Allium tools arrive ready to call.

Query runs, tokens, token prices and Polygon NFTs, with no custom code to write.

  • Create a Allium querie run
  • Create a Allium querie run async
  • List all Allium explorer query runs
  • Allium explorer query runs cancel
ElaichiTools
Tool Action Description
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.

Toolboxes

Every team gets its own Allium toolbox.

Curate one toolbox per team so research, data and finance see different Allium tools.

  • Research
  • Data
  • Finance
  • Trading
ElaichiToolboxes
Name Source template Tools Created

Research toolbox

Allium · token prices and price history

Allium starter 18 Mar 4, 2026

Data toolbox

Allium · query runs and results

— 9 Mar 2, 2026

Finance toolbox

Allium · token price stats and reporting

— 24 Feb 27, 2026

Trading toolbox

Allium · live token prices and tokens

Allium starter 6 Feb 19, 2026

Risk toolbox

Allium · query run status and history

— 31 Jan 30, 2026

Product toolbox

Allium · Polygon NFTs and token search

— 12 Jan 22, 2026

Shared connections

Teammates run Allium queries without a key.

See who connected each Allium account and how many teams and members share it.

  • Research
  • Data Platform
  • Finance
  • Trading Desk
ElaichiConnections
Connection Scope Status Access
AL

Allium (Research)

Connected by Emily Carter

Personal • Active 1 team · 6 members
AL

Allium (Data Platform)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
AL

Allium (Finance)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
AL

Allium (Trading Desk)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
AL

Allium (Risk)

Connected by Ryan Hayes

Personal • Active Not shared
AL

Allium (Product Analytics)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Allium call is written down.

When, who, what happened, type and resource, appended for each Allium query run.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Allium Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Allium Query runs Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Allium Query runs List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Allium records into a digest.

Six steps fetch Allium query results, group them, draft a digest and post it back after approval.

Allium digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch query runs

    Allium

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Allium

    Queued

Collections and dashboards

Allium health arrives before anyone asks.

Four metrics, 14 days of records created and a team breakdown, computed on a schedule.

Allium health

Refreshed 4 minutes ago · every 15 minutes · from the query runs collection

Live

Query runs

1,284 ↓ 12%

Tokens

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Query runs created

Last 14 days

By team

Share of activity

Research 34%

Data Platform 27%

Finance 21%

Trading Desk 18%

FAQ

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, 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 blocking anything that cancels a query run or starts long-running jobs in Allium. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

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, 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, 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.

Put Allium in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.