Skip to content

Compliance

Alloy MCP connector

The Alloy connector brings customer accounts, bank accounts, review cases, evidence, alerts, batches, and custom lists into Claude, ChatGPT, Cursor, and any MCP client, so your compliance team can ask questions and work cases 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 Alloy to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Alloy once

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

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

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

alloy
Alloy
Cakewalk
Comp AI
ComplyCube
Drata
Lumos
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 Alloy 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 Alloy 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 Alloy 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 Alloy 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 Alloy through Elaichi

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

  • Compliance

    Work through the open case queue

    Ask for the cases waiting on review, pull up a single case with its evidence and alerts, and get a plain summary of what triggered it before you decide.

  • Fraud

    Attach evidence and notes to a case

    After looking into a suspicious application, add the evidence you found and record the work you did on the case, in the same conversation where you reviewed it.

  • Compliance

    Keep custom lists current

    Add a new entry to a blocklist or allowlist, publish a new version, and check which version is live, without opening the Alloy console.

  • Operations

    Check on batch runs

    Ask which batches are still in progress, which finished, and what came back for a specific batch by its ID.

  • Onboarding

    Look up an applicant's account and bank details

    Find an account, see the bank accounts tied to it, and correct account details when a customer sends updated information.

  • Risk

    Review alerts across recent cases

    List the evidence alerts raised this week, group them by type, and spot the patterns that need a closer look.

Try asking

  • “List open Alloy cases created this week by reviewer.”
  • “Summarize evidence attached to Alloy case 4821.”
  • “Which Alloy accounts have bank accounts pending review?”

See all 138 Alloy tools below

AI tools

Alloy tools for your AI agents

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

See it in Elaichi

What connecting Alloy gets you

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

The agent

Ask about Alloy cases in plain language.

The agent reads live Alloy cases, accounts and evidence to answer.

  • cases
  • accounts
  • bank accounts
  • case evidences

Ask Elaichi to work across your apps.

List open Alloy cases created this week by reviewer.

Summarize evidence attached to Alloy case 4821.

Which Alloy accounts have bank accounts pending review?

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Alloy 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

138 Alloy tools ready without custom code.

Browse Alloy accounts, cases, batches, evidence and case works with their methods.

  • Create a Alloy account
  • Update a Alloy account by ID
  • List all Alloy bank accounts
  • Get single Alloy bank account by ID
ElaichiTools
Tool Action Description
Create a Alloy account Create Create a new account in alloy (deprecated in favor of the Events API). Returns the created account object including bank_account_token, external_account_id, account_number, account_class, account_name, and account_type. The request body must include at least one of external_account_id or account_number.
Update a Alloy account by ID Update Update an existing alloy account by id. Returns the updated account object including bank_account_token, external_account_id, account_number, account_class, account_name, routing_number, is_linked_account, and other account attributes. Required: id.
List all Alloy bank accounts List List bank accounts in alloy associated with a given account identifier or token. Returns: bank_account_token, external_account_id, account_number, account_number_last4, account_class, account_name, routing_number, account_type, is_linked_account, link_timestamp, unlink_timestamp, opening_date, closing_date, maturity_date, country_code, currency, cif_number, product_code, product_name,…
Get single Alloy bank account by ID Get Get a single bank account in alloy by its bank account token, including historical and entity data. Returns: bank_account_token, external_account_id, account_number, account_number_last4, account_class, account_name, routing_number, account_type, is_linked_account, link_timestamp, unlink_timestamp, opening_date, closing_date, maturity_date, country_code, currency, cif_number, product_code,…
List all Alloy batches List Retrieve an Alloy batch by its batch_token. Returns the Batch object including batch_token and associated batch attributes. Required: batch_token.

Toolboxes

Every team gets its own Alloy toolbox.

Compliance, fraud ops and onboarding each see the Alloy tools they need.

  • Compliance
  • Fraud operations
  • Onboarding
  • Risk
ElaichiToolboxes
Name Source template Tools Created

Compliance toolbox

Alloy · cases and case works

Alloy starter 18 Mar 4, 2026

Fraud operations toolbox

Alloy · case evidence and reviews

9 Mar 2, 2026

Onboarding toolbox

Alloy · accounts and applications

24 Feb 27, 2026

Risk toolbox

Alloy · batches and decision outcomes

Alloy starter 6 Feb 19, 2026

Support toolbox

Alloy · account lookups and status

31 Jan 30, 2026

Audit toolbox

Alloy · case history and evidence trails

12 Jan 22, 2026

Shared connections

Teammates use Alloy accounts without the credential.

See who connected each Alloy account and which teams and members share it.

  • Compliance US
  • Fraud operations
  • Onboarding
  • Risk review
ElaichiConnections
Connection Scope Status Access
AL

Alloy (Compliance US)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
AL

Alloy (Fraud operations)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
AL

Alloy (Onboarding)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
AL

Alloy (Risk review)

Connected by Daniel Ortega

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

Alloy (Support)

Connected by Clara Nowak

Personal • Active Not shared
AL

Alloy (Audit)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who touched which Alloy case.

Every call lands append only with time, person, action, type and resource.

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

Alloy Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Alloy Cases Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Alloy Cases 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, an Alloy digest ships.

Six steps fetch Alloy cases, group them, draft, wait for approval, post back.

Alloy digest

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

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch cases

    Alloy

    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

    Alloy

    Queued

Collections and dashboards

Alloy case volume computed, not asked for.

Four metrics, 14 days of new Alloy cases, split by team, refreshed on schedule.

Alloy health

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

Live

Cases

1,284 ↓ 12%

Accounts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Cases created

Last 14 days

By team

Share of activity

Compliance US 34%

Fraud operations 27%

Onboarding 21%

Risk review 18%

FAQ

Frequently asked questions

How do I connect Alloy to Claude?

Connect Alloy in Elaichi first: paste your Alloy API key when asked, and the connection is ready. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi with your own account and Alloy appears in Claude.

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

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

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

With Alloy connected, an agent can look up accounts and their bank accounts, list and open review cases, read the evidence and alerts on a case, add new evidence and case notes, check batch results, create documents, and create or update custom lists and their versions. Because Alloy has a large set of actions, short concrete asks like "show me open cases from today" work better than long paragraphs.

Does connecting Alloy give the AI access to every case and list?

No. Every request to Alloy runs under the access of the person who signed in to Elaichi, so the agent sees only the cases, accounts, and lists that person could already reach. Elaichi can narrow that further, for example to read-only access, but it can never widen it beyond what the person already has.

Can my team share one Alloy connection?

Yes. One person connects Alloy with the 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 every case they open or note they add is logged under their own name.

Can I stop an agent from changing things in Alloy?

Yes. In Elaichi you can restrict the Alloy connection action by action, for example allowing case lookups while blocking updates to accounts or changes to custom lists. A blocked action is never advertised to Claude, ChatGPT, or any other client, so no prompt can reach it.

What happens to an Alloy connection when someone leaves?

When you offboard a person in Elaichi, their access to Alloy through every client ends at once, and the audit log keeps the record of what they did. A shared Alloy connection keeps working for everyone else on the team. If you disconnect Alloy in Elaichi, it disappears from Claude, ChatGPT, Cursor, and every other client in one step.

Put Alloy in front of your team

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