Skip to content

SSO

World MCP connector

The World connector brings World ID verifications, incognito actions, mini app notifications, transactions and account recovery into Claude, ChatGPT, Cursor and any MCP client, so your team can ask about them in plain language, with every call logged.

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

Two steps, about a minute.

1

In Elaichi

Connect World once

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

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

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

world
World
Auth0
Google
Google Workspace
Okta
Torii
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 World 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 World 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 World 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 World 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 World through Elaichi

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

  • Product

    Check how a new action is verifying

    Ask how many people have completed the sign-up action this week and whether verifications are going through, then create the next action when the flow is ready.

  • Support

    Find out why a verification failed

    When a user says they could not prove they are human, pull up their verification and the precheck result to see what went wrong before you reply.

  • Trust and safety

    Confirm a proof is genuine

    Verify a proof against a specific action and check that the root it came from is still valid, so duplicate or replayed proofs never slip through.

  • Growth

    Send a notification to mini app users

    Draft a message to people who have used your mini app, check the wording and send it without leaving the chat.

  • Finance

    Reconcile mini app transactions

    Look up a transaction by its reference, review pricing across mini apps and check the current grant cycle when the month closes.

  • Operations

    Help someone recover their account

    Start, execute or cancel a recovery for a user who lost their device, and add or remove authenticators once they are back in.

Try asking

  • “How many World verifies completed for the onboarding action?”
  • “List World minikit transactions from yesterday over 100 tokens.”
  • “Summarize World actions created this month by team.”

See all 31 World tools below

AI tools

World tools for your AI agents

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

See it in Elaichi

What connecting World gets you

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

The agent

Ask about World verifies, get real answers.

Type a question in plain language and read live World records back.

  • verifies
  • transactions
  • actions
  • notifications

Ask Elaichi to work across your apps.

How many World verifies completed for the onboarding action?

List World minikit transactions from yesterday over 100 tokens.

Summarize World actions created this month by team.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach World here.

One governed MCP endpoint for World, 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

31 World tools arrive ready to call.

Browse verifies, minikit transactions and jwks methods without writing custom code.

  • Create a World verify
  • World verifies create legacy
  • List all World verifies
  • Create a World minikit send notification
ElaichiTools
Tool Action Description
Create a World verify Create Verify a World ID proof for a Cloud action in World. Returns: success, action, nullifier_hash, created_at. Required: verify_id.
World verifies create legacy Create Verify a World ID proof for a Cloud action using the legacy v2 verify endpoint in World. Returns: success, action, nullifier_hash, created_at. Required: verify_id.
List all World verifies List List World ID verifications in World. Returns records with: success, action, nullifier, created_at, environment, session_id, results, message.
Create a World minikit send notification Create Send notifications to users of your World mini app by wallet address. Returns per-recipient results with walletAddress, sent, and reason. Required: app_id, wallet_addresses, mini_app_path. Either title and message (legacy) or localisations (localized) must also be provided; if both are given, localisations is used. Max 1000 wallet addresses per call.
Get single World minikit transaction by ID Get Get a World MiniKit transaction by id to query its current on-chain status. Returns the transaction object including reference, transaction_hash, transaction_status, from, to, token_amount, token, chain, timestamp, and app_id. Required: id, app_id.

Toolboxes

Every team gets its own World toolbox.

Scope minikit tools to the mini app team and verifies to identity.

  • Identity Engineering
  • Mini App Team
  • Trust and Safety
  • Growth
ElaichiToolboxes
Name Source template Tools Created

Identity Engineering toolbox

World · verifies and actions

World starter 18 Mar 4, 2026

Mini App Team toolbox

World · minikit transactions and notifications

9 Mar 2, 2026

Trust and Safety toolbox

World · recovery agents and verifies

24 Feb 27, 2026

Growth toolbox

World · notifications and grant cycles

World starter 6 Feb 19, 2026

Platform Engineering toolbox

World · jwks and graphql calls

31 Jan 30, 2026

Finance toolbox

World · miniapp prices and transactions

12 Jan 22, 2026

Shared connections

Teammates use World accounts, never the credential.

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

  • Identity Prod
  • Mini App Staging
  • Trust and Safety
  • Growth
ElaichiConnections
Connection Scope Status Access
WO

World (Identity Prod)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
WO

World (Mini App Staging)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
WO

World (Trust and Safety)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
WO

World (Growth)

Connected by Daniel Ortega

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

World (Platform)

Connected by Clara Nowak

Personal • Active Not shared
WO

World (Finance)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every World call is on the record.

When, who, what happened, type and resource for each World request.

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

World Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

World Verifies Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

World Verifies 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 World records into work.

Fetch World verifies, group them, draft a digest, approve, then post back.

World digest

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

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch verifies

    World

    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

    World

    Queued

Collections and dashboards

World health counted, refreshed on a schedule.

Four metrics, 14 days of World verifies created, and a team breakdown.

World health

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

Live

Verifies

1,284 ↓ 12%

Transactions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Verifies created

Last 14 days

By team

Share of activity

Identity Prod 34%

Mini App Staging 27%

Trust and Safety 21%

Growth 18%

FAQ

Frequently asked questions

How do I connect World to Claude?

First connect World in Elaichi, which asks for your World API key from the developer portal, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. There is no OAuth application to register and no client ID or secret to generate. Once it is added, Claude can work with World verifications, actions and mini app records as you.

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

Yes. The World connector uses the same endpoint, https://api.elaichi.ai/mcp, for Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect World once in Elaichi and each person signs in with their own login from whichever client they use.

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

An agent connected to World can verify a proof, create a new incognito action, run a precheck, list recent verifications and check whether a root is still valid. It can look up mini app transactions and prices, send a notification to mini app users, and start or cancel an account recovery. World has a large set of tools, so short concrete asks such as "list this week's verifications" work better than long sentences.

Does connecting World give the AI everything in my developer account?

No. Every call to World runs inside the access of the person who signed in, so the agent sees the apps and actions that person's World API key can reach and nothing more. Elaichi can narrow that access further by team or by action, but it can never widen it beyond what the person already has.

Can my team share one World connection?

Yes. One person connects World with the API key and shares the connection with a team, and nobody else handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every verification or notification.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading verifications and transactions while blocking sending notifications, removing authenticators or executing a recovery. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

What happens to a World connection when someone leaves?

Offboarding a person in Elaichi ends their access to World at once, across every client they used. If they had shared a World connection, it keeps working for everyone else on the team. Disconnecting World once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Put World in front of your team

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