Artie MCP connector
The Artie connector lets Claude, ChatGPT, Cursor and any MCP client check Artie connectors, browse source tables, manage column hashing salts and encryption keys, and start exports, with every action running as the signed-in person and recorded in an audit log.
-
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.
59 tools
How to connect
How to connect Artie to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Artie once
-
Open Connections, choose Add connection, and pick Artie.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Artie API key. One person generates a token in Artie 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.
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.
Artie MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Artie MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Artie MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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 Artie to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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 Artie through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Data engineering
Check a source before building a pipeline
Ping a new Postgres, Oracle or DynamoDB connector in Artie and list its databases, schemas and tables so you know it is reachable before anyone sets up replication.
-
Analytics
Find where a table actually lives
Search the Artie data catalog for the orders or customers table, pull its column detail, and answer the question without opening three separate consoles.
-
Security
Review how sensitive columns are masked
List every column hashing salt and encryption key in Artie, then preview how a salt hashes a field before that data lands in the warehouse.
-
Platform
Stand up a new Snowflake destination
Create the Snowflake warehouse, database and schema through Artie, then confirm the connector can reach it, all from the same conversation.
-
Data engineering
Clean up after a database cutover
List the remaining Postgres publications, drop the stale replication slot, and update the Artie connector settings once the migration is finished.
-
Operations
Start an export when a team asks
Kick off a DynamoDB export in Artie the moment a downstream team needs a fresh copy, and check the connector afterward to confirm it went through.
Try asking
- “Which Artie connectors pull tables from the warehouse database?”
- “Summarize schemas added across Artie connectors this month.”
- “List columns covered by Artie column hashing salts.”
Compare
Elaichi vs Zapier MCP vs Composio for Artie
All three can connect Artie to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Artie tools | Allow or restrict single Artie 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 Artie 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
Artie tools for your AI agents
59 tools are ready to call through Elaichi's MCP endpoint the moment you connect Artie, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Artie gets you
6 screens from the product, each doing one job for your Artie account.
The agent
Ask about Artie connectors in plain language.
Starter prompts return answers from live Artie connectors, schemas and tables.
- connectors
- schemas
- tables
- databases
Ask Elaichi to work across your apps.
Which Artie connectors pull tables from the warehouse database?
Summarize schemas added across Artie connectors this month.
List columns covered by Artie column hashing salts.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Artie together.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
All 59 Artie tools arrive ready to call.
Connectors, schemas, tables and column hashing salts, with no custom code written.
- List all Artie column hashing salts
- Get single Artie column hashing salt by ID
- Create a Artie column hashing salt
- Update a Artie column hashing salt by ID
ElaichiToolsToolboxes
Every team gets its own Artie toolbox.
Curate one toolbox of Artie tools per team and scope it to them.
- Data engineering
- Analytics
- Platform
- Security
ElaichiToolboxesShared connections
Teammates use Artie accounts without credentials.
See who connected each Artie account and which teams and members share it.
- Data engineering
- Analytics EMEA
- Platform
- Security
ElaichiConnectionsAudit log
Every Artie call is written down.
When, who, what happened, type and resource, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 drafts your Artie digest.
Six steps fetch tables, group them, draft a digest, await approval, post back.
Artie digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch connectors
Artie
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Artie
Queued
Collections and dashboards
Artie numbers land before anyone asks.
Four metrics, 14 days of records created, split by team, refreshed on schedule.
Artie health
Refreshed 4 minutes ago · every 15 minutes · from the connectors collection
Connectors
1,284 ↓ 12%
Schemas
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Connectors created
Last 14 days
By team
Share of activity
Data engineering 34%
Analytics EMEA 27%
Platform 21%
Security 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Artie to Claude?
Open Elaichi, choose Artie from the catalog, and paste in your Artie API key when prompted. 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 with your Elaichi account and Artie is ready to use.
Does Artie work with ChatGPT and Cursor as well as Claude?
Yes. Once Artie 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 Artie once and every client picks it up.
What can an AI agent actually do with my Artie data?
An agent can look up an Artie connector, ping it to see whether it is reachable, and list the databases, schemas, tables and column detail behind it. It can search the Artie data catalog, list and preview column hashing salts, list encryption keys, create Snowflake warehouses, databases and schemas, start a DynamoDB export, and manage Postgres publications and replication slots. Because Artie exposes a lot of actions, short concrete asks such as "list the tables in the billing connector" work better than long paragraphs.
Does connecting Artie give the AI access to every connector and key in my workspace?
No. Every call to Artie runs with the access of the person who signed in, so the agent sees the connectors, salts and encryption keys that person's Artie API key can already see, and nothing more. Elaichi can narrow that access further with restrictions, but it never widens it.
Can I stop an agent from deleting or changing things in Artie?
Yes. Restrictions in Elaichi work per action, so you can block deleting an Artie connector, dropping a replication slot or removing a hashing salt while still allowing lookups and catalog searches. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to an Artie connection when someone leaves?
Offboarding a person in Elaichi ends their access to Artie at once, across every client they used. If they shared the Artie connection with a team, it keeps working for everyone else. Disconnecting Artie once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Artie MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Artie 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 Artie?
Yes. Both let Claude, ChatGPT or Cursor use Artie. 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 Artie call.
How is Elaichi different from Composio for Artie?
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 Artie: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Artie in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.