Skip to content

Conversational Intelligence

Anthropic MCP connector

The Anthropic connector brings your organization's Anthropic Console into Claude, ChatGPT, Cursor, and other MCP clients, so you can review users, workspaces, API keys, usage, and spend by asking in plain language.

Connect on Elaichi How to connect

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

Two steps, about a minute.

1

In Elaichi

Connect Anthropic once

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

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

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

anthropic
Anthropic
AssemblyAI
Chorus
Fathom
Granola
Groq
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 Anthropic 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 Anthropic 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 Anthropic 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 Anthropic 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.

Connect Anthropic on Elaichi See pricing

Use cases

What teams do with Anthropic through Elaichi

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

  • Finance

    Pull this month's Anthropic spend by workspace

    Ask for the Anthropic cost report broken down by workspace before the invoice lands. Compare it with last month and flag the team whose spend jumped.

  • IT

    Invite a new hire and place them

    Send the Anthropic organization invite, then add the person to the right workspace with the right role once they accept. No console clicking, no waiting on an admin.

  • IT

    Offboard someone from Anthropic in one ask

    Remove a departing colleague from every Anthropic workspace they belong to and delete their user record. Confirm afterward that nothing is still assigned to them.

  • Security

    Find API keys nobody has touched

    List every Anthropic API key with who created it, which workspace it lives in, and when it was last used. Rename or disable the stale ones on the spot.

  • Engineering

    Stand up a workspace for a new project

    Create an Anthropic workspace, add the engineers who need it, and check the message usage report as the project ramps up. Archive it when the work is done.

  • Operations

    Answer who has access to what

    Ask for every Anthropic user, their organization role, and the workspaces they belong to. Hand the list to an auditor or a manager without exporting anything by hand.

Try asking

  • “Which Anthropic workspaces have no members right now?”
  • “List Anthropic users added to the billing workspace.”
  • “Show workspace members archived in the last 30 days.”

See all 43 Anthropic tools below

AI tools

Anthropic tools for your AI agents

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

See it in Elaichi

What connecting Anthropic gets you

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

The agent

Ask about Anthropic users, get real answers.

Plain language questions run against live Anthropic workspaces, members and users.

  • users
  • workspaces
  • workspace members
  • invites

Ask Elaichi to work across your apps.

Which Anthropic workspaces have no members right now?

List Anthropic users added to the billing workspace.

Show workspace members archived in the last 30 days.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Every client reaches Anthropic over OAuth through one org endpoint, no shared 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

43 Anthropic tools are ready to call.

Users, workspaces and workspace members are covered already, with no custom code.

  • List all Anthropic users
  • Get single Anthropic user by ID
  • Update a Anthropic user by ID
  • Delete a Anthropic user by ID
ElaichiTools
Tool Action Description
List all Anthropic users List List users in Anthropic. Returns id, name, email, role, type, and added_at for each user. Also includes first_id, last_id, and has_more for pagination.
Get single Anthropic user by ID Get Get details of a specific user in Anthropic. Requires id. Returns added_at (when user joined), email, id, name, role, and type (always 'user').
Update a Anthropic user by ID Update Update user role in Anthropic. Requires id. Returns added_at (when user joined), email (user email), id (user identifier), name (user name), role (organization role), and type (always 'user').
Delete a Anthropic user by ID Delete Delete a user in Anthropic. Requires id. Returns id of the deleted user and type confirming deletion as user_deleted.
List all Anthropic workspaces List List workspaces in Anthropic. Returns id, name, display_color, created_at, archived_at, and type for each workspace, along with pagination fields first_id, last_id, and has_more.

Toolboxes

Each team gets its own Anthropic toolbox.

Curate one toolbox for platform admins and another for finance, scoped per team.

  • Platform
  • IT operations
  • Security
  • Finance
ElaichiToolboxes
Name Source template Tools Created

Platform toolbox

Anthropic · workspaces and archives

 Anthropic starter 18 Mar 4, 2026

IT operations toolbox

Anthropic · users and access

 — 9 Mar 2, 2026

Security toolbox

Anthropic · member roles and removals

 — 24 Feb 27, 2026

Finance toolbox

Anthropic · workspace ownership and spend

 Anthropic starter 6 Feb 19, 2026

Data science toolbox

Anthropic · workspaces and members

 — 31 Jan 30, 2026

Support toolbox

Anthropic · user lookups

 — 12 Jan 22, 2026

Shared connections

Teammates use Anthropic without seeing credentials.

Each connection shows who added the account and which teams and members use it.

  • Platform admin
  • IT operations
  • Security
  • Finance
ElaichiConnections
Connection Scope Status Access
AN

Anthropic (Platform admin)

Connected by Emma Laurent

 Personal • Active 1 team · 6 members
AN

Anthropic (IT operations)

Connected by James Whitfield

 Organization • Active 3 teams · 24 members
AN

Anthropic (Security)

Connected by Sofia Ricci

 Organization • Active 2 teams · 11 members
AN

Anthropic (Finance)

Connected by Daniel Ortega

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

Anthropic (Data science)

Connected by Clara Nowak

 Personal • Active Not shared
AN

Anthropic (Support)

Connected by Michael Brennan

 Personal • Active 2 teams · 9 members

Audit log

Every Anthropic call has a name on it.

When, who, what happened, type and resource for each workspace and user change.

  • 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]

 Anthropic Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
C

Clara Nowak

[email protected]

 Anthropic Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
M

Michael Brennan

[email protected]

 Anthropic Users 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 the digest ships.

Anthropic workspace members are fetched, grouped, drafted, approved by a person, then posted back.

Anthropic digest

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

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch users

    Anthropic

    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

    Anthropic

    Queued

Collections and dashboards

Anthropic numbers arrive without anyone asking.

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

Anthropic health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Workspaces

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Platform admin 34%

IT operations 27%

Security 21%

Finance 18%

Related connectors

More from the catalog

Browse all 400+ connectors →

FAQ

Frequently asked questions

How do I connect Anthropic to Claude?

Connecting Anthropic takes two steps. In Elaichi, choose the Anthropic connector and paste an admin API key from your Anthropic Console, which is the only sign-in step, with 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. Sign in to Elaichi when Claude asks and Anthropic is ready.

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

Yes. Once Anthropic 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 Anthropic once and every client you use picks it up.

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

With Anthropic connected, an agent can list your organization's users and their roles, create and archive workspaces, add or remove workspace members, send and cancel organization invites, and review API keys and their status. It can also pull message usage reports and cost reports so you can see what each workspace consumed and what it cost. Because Anthropic exposes many actions, short concrete asks such as "show cost by workspace for March" work better than long paragraphs.

Does connecting Anthropic give the AI everything in my organization?

No. Every call to Anthropic runs with the admin API key the person connected, so the agent can only reach what that key is allowed to reach in the Anthropic Console. Elaichi can narrow that further, for example to reports only, but it can never grant more than the key itself has.

Can my team share one Anthropic connection?

Yes. One person connects Anthropic in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every user change, invite, or report pulled from Anthropic.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading Anthropic users, workspaces, and cost reports while blocking anything that deletes a user, removes a workspace member, or changes an API key. A blocked action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.

What happens to an Anthropic connection when someone leaves?

When you offboard a person in Elaichi, their access to the Anthropic connection ends at once, in every client they had set up. If the connection was shared, it keeps working for everyone else on the team. If you ever want Anthropic gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.

Put Anthropic in front of your team

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

Connect Anthropic Talk to us