Skip to content

Payment Gateway

Circle MCP connector

The Circle connector brings wallets, wallet sets, balances, monitored tokens, and notification subscriptions into Claude, ChatGPT, Cursor, and the Elaichi Agent, so your team can ask about and manage Circle wallets in plain language.

  • 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 Circle to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Circle once

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

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Circle API key. One person generates a token in Circle 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.

circle
Circle
Chimoney
Dwolla
Finexio
Flutterwave
GoCardless
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.

Connect Circle to 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.

Connect Circle to 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.

Connect Circle to 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 Circle 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 Circle through Elaichi

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

  • Finance

    Check balances across every wallet

    Ask for the current balances across all Circle wallets in one go instead of opening each wallet set. Get a plain answer you can paste into the morning report.

  • Treasury

    Set up a new wallet set

    Create a Circle wallet set for a new product line or region, then add the developer wallets under it, all from a conversation.

  • Operations

    Keep wallet names and details tidy

    Rename a Circle wallet or wallet set after a reorganization so the labels match the team that actually owns it.

  • Engineering

    Fund a test wallet quickly

    Request a faucet drip for a Circle test wallet while building or debugging, without leaving the editor to hunt for the right form.

  • Compliance

    Review which tokens are monitored

    List the tokens Circle is watching for your entity, add a new one, or adjust the scope of several at once before a review.

  • Platform

    Manage notification subscriptions

    See every notification subscription Circle is sending to, create one for a new endpoint, update it when a URL changes, and remove ones nobody uses.

Try asking

  • “List monitored tokens added to Circle this week.”
  • “Which Circle notification subscriptions are active per entity?”
  • “Summarize Circle public keys by config entity.”

See all 294 Circle tools below

AI tools

Circle tools for your AI agents

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

See it in Elaichi

What connecting Circle gets you

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

The agent

Ask about monitored tokens, get real answers.

Plain language questions run against live Circle tokens, subscriptions and entities.

  • monitored tokens
  • notification subscriptions
  • public keys
  • config entities

Ask Elaichi to work across your apps.

List monitored tokens added to Circle this week.

Which Circle notification subscriptions are active per entity?

Summarize Circle public keys by config entity.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Circle here.

One org MCP endpoint over OAuth, no SDK 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

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

294 Circle tools are cataloged and ready.

Monitored tokens, subscriptions, public keys and entities, with no custom code written.

  • List all Circle entity monitored tokens
  • Create a Circle entity monitored token
  • Circle entity monitored tokens bulk update
  • Circle monitored tokens scopes bulk update
ElaichiTools
Tool Action Description
List all Circle entity monitored tokens List List monitored tokens in Circle, optionally filtered by blockchain, token address, or token symbol. Returns: id.
Create a Circle entity monitored token Create Add a new token to Circle's monitored token list. Returns the monitored token object including id, blockchain, tokenAddress, and tokenSymbol. A 200 response indicates the token was already present (no update); a 201 indicates it was newly added. Required: blockchain, tokenAddress.
Circle entity monitored tokens bulk update Update Upsert the monitored token list for the Circle entity, adding or updating tokens to monitor across blockchains. Returns the updated monitored tokens including token items with their blockchain, token address, and token symbol. Required: tokenItems.
Circle monitored tokens scopes bulk update Update Update the monitored tokens scope in Circle to select between monitoring all tokens or only selected tokens from the monitored tokens list. Returns an empty 200 response on success. Requires a request body specifying the desired monitoring scope.
Delete a Circle monitored tokens delete by ID Delete Delete tokens from the monitored token list in Circle. Returns an empty response on success. Requires a request body identifying the tokens to remove.

Toolboxes

Every team gets its own Circle toolbox.

Curate toolboxes scoped to Treasury, Payments or Engineering from one Circle catalog.

  • Treasury
  • Payments
  • Engineering
  • Compliance
ElaichiToolboxes
Name Source template Tools Created

Treasury toolbox

Circle · monitored tokens and entities

Circle starter 18 Mar 4, 2026

Payments toolbox

Circle · notification subscriptions

9 Mar 2, 2026

Engineering toolbox

Circle · public keys and pings

24 Feb 27, 2026

Compliance toolbox

Circle · token scopes and entities

Circle starter 6 Feb 19, 2026

Finance Ops toolbox

Circle · faucet drips and balances

31 Jan 30, 2026

Support toolbox

Circle · subscriptions and pings

12 Jan 22, 2026

Shared connections

Teammates use Circle accounts without seeing keys.

The connections table shows who connected each Circle account and its shared teams.

  • Treasury Prod
  • Payments EMEA
  • Engineering Sandbox
  • Compliance
ElaichiConnections
Connection Scope Status Access
CI

Circle (Treasury Prod)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
CI

Circle (Payments EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
CI

Circle (Engineering Sandbox)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
CI

Circle (Compliance)

Connected by Daniel Ortega

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

Circle (Finance Ops)

Connected by Clara Nowak

Personal • Active Not shared
CI

Circle (Support)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Circle call is written down permanently.

When, who, what happened, type and resource, in an append only log.

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

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Circle Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Circle Monitored tokens Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Circle Monitored tokens 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 fires and Circle work finishes.

Six steps fetch monitored tokens, group them, draft a digest, then await approval.

Circle digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch monitored tokens

    Circle

    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

    Circle

    Queued

Collections and dashboards

Circle health numbers arrive without being asked.

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

Circle health

Refreshed 4 minutes ago · every 15 minutes · from the monitored tokens collection

Live

Monitored tokens

1,284 ↓ 12%

Notification subscriptions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Monitored tokens created

Last 14 days

By team

Share of activity

Treasury Prod 34%

Payments EMEA 27%

Engineering Sandbox 21%

Compliance 18%

FAQ

Frequently asked questions

How do I connect Circle to Claude?

First, add Circle in Elaichi and paste in the API key from your Circle developer console when asked. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can then work with your Circle wallets, balances, and monitored tokens.

Does Circle work with ChatGPT and Cursor as well as Claude?

Yes. Once Circle is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Circle once and every client you use picks it up.

What can an AI agent actually do with my Circle data?

With Circle connected, an agent can list your wallets and wallet sets, report balances, create new developer wallets, update wallet details, manage the tokens Circle monitors for your entity, and create or change notification subscriptions. It can also request a faucet drip for a test wallet. Circle offers a lot of actions, so short, specific asks such as "show balances for the treasury wallet set" work better than long paragraphs.

Does connecting Circle give the AI access to everything in my Circle account?

No. Every request runs under the Circle API key that was connected, so the agent can only reach what that key is already allowed to reach in Circle. Elaichi can narrow that further by blocking specific actions for a team, but it can never widen access beyond what Circle itself grants.

Can my team share one Circle connection?

Yes. One person connects Circle in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every wallet lookup or balance check in the audit log is tied to the person who asked for it, not to a shared account.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading Circle wallets and balances while blocking the creation of wallets, changes to monitored tokens, or the deletion of notification subscriptions. A blocked action is never shown to Claude, ChatGPT, or any other client at all, so no prompt, however worded, can reach it.

What happens to a Circle connection when someone leaves?

When you offboard a person in Elaichi, their access to Circle through every client ends immediately. If they had shared a Circle connection with a team, that connection keeps working for everyone else. If you want Circle gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put Circle in front of your team

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