Apify MCP connector
The Apify connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent find and run actors, read datasets and run logs, and manage tasks and schedules in Apify, with each person signed in as themselves and every call logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which actor runs failed last night and what did the logs say?
Working in Apify with Elaichi
-
Search actors
-
Search Apify docs
-
Get actor run
How to connect Apify to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Apify 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.
Apify MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Apify 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. The plugin directory lives at chatgpt.com/plugins.
Apify 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.
Apify MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Apify 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.
What teams do with Apify through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Apify is logged.
-
Marketing
Pull competitor prices before the Monday meeting
Start the pricing actor you already use, wait for the run to finish, and read the dataset items back as a plain table. No one has to open Apify or export a file.
-
Sales
Build a prospect list from a scraped directory
Ask for the latest items from the directory scraper's dataset and have them summarized by region or industry. The list is ready to hand over before the first call of the day.
-
Data
Check what came back from last night's crawl
Look at the dataset schema, sample the first hundred items, and spot a broken field before anyone builds a report on it.
-
Research
Find the right actor for a new source
Search the Apify Store for an actor that covers a new website, read its details and the relevant docs, and try a small run to see what the output looks like.
-
Engineering
Set up a task and put it on a schedule
Create an actor task with the inputs your team settled on, publish it, and add a weekly schedule so the crawl runs without anyone remembering to start it.
-
Operations
Catch a runaway run before it burns credits
Ask which runs have been going longer than usual, read the log of the one that looks stuck, and abort it from the same conversation.
Try asking
- “Which actor runs failed last night and what did the logs say?”
- “Show me the first 50 items from the Google Maps scraper dataset.”
- “Create a weekly schedule for the competitor pricing task.”
What connecting Apify gets you
6 screens from Elaichi, each doing one job for your Apify account.
Ask Elaichi to work across your apps.
Which actor runs failed last night and what did the logs say?
Show me the first 50 items from the Google Maps scraper dataset.
Create a weekly schedule for the competitor pricing task.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any actor run in plain language.
Check which scrapes finished overnight and pull the dataset items without opening Apify.
Copy the endpoint
AI apps
One endpoint brings Apify to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot all reach Apify through one governed endpoint, no shared API key.
Tool catalog
27 Apify tools, ready without writing code.
Actors, runs, datasets, key-value stores, tasks and schedules, covered with no custom code.
Toolboxes
Each team gets its own Apify toolbox.
Marketing runs scrapers, Data reads datasets, Engineering manages tasks, each from a scoped toolbox.
Shared connections
Share one Apify connection, never the token.
Teammates start runs and read datasets through your connection without ever seeing a credential.
Audit log
Every Apify call lands in the log.
See who started a run, aborted it, or published a task, and exactly when.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Apify digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch actors
Apify
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 Jake Morgan
Approve Deny -
Post the digest
Apify
Queued
Workflows
A schedule starts the scrape and the digest.
Dataset items are fetched, grouped, drafted into a digest, approved, then the follow-up run starts.
Apify health
Refreshed 4 minutes ago · every 15 minutes · from the actors collection
Actors
1,284 ↓ 12%
Runs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Actors created
Last 14 days
By team
Share of activity
Marketing 34%
Sales 27%
Data team 21%
Research 18%
Collections and dashboards
Apify health, computed on a schedule, no prompt.
Runs, failures, dataset items and compute per team, refreshed hourly with no model involved.
Why connect Apify's MCP server through Elaichi
Apify builds and runs this MCP server. Elaichi sits in front of it, so Apify's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Apify's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Apify's tools at the same Elaichi address as every other connected app. Nobody adds Apify's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Apify sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Apify's server. By default, a tool Apify does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Apify
Apify builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Apify team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Apify
All three can connect Apify 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 Apify tools | Allow or restrict single Apify 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 Apify 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 | Free for one person; $15 per user per month on Gold. | 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.
Apify tools for your AI agents
27 tools are ready to call through Elaichi's MCP endpoint the moment you connect Apify, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Apify builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect Apify to Claude?
Connect Apify in Elaichi first: you sign in with your Apify account over OAuth and approve access, 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. Claude asks you to sign in to Elaichi, and from then on Apify is available in your conversations.
Does Apify work with ChatGPT and Cursor as well as Claude?
Yes. Once Apify is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Apify once and every client picks it up.
What can an AI agent actually do with my Apify data?
With Apify connected, an agent can search the Apify Store for actors, read their details and docs, start an actor run and follow its log, and read the results from datasets and key-value stores. It can also create, update, publish or unpublish actor tasks, add schedules, and abort a run that has gone wrong. Short, concrete asks such as "show me the last five runs of the pricing scraper" work better than long instructions.
Does connecting Apify give the AI access to my whole Apify account?
An agent working through Apify only sees the actors, runs, datasets and stores that the person who signed in can already see in Apify. Elaichi can narrow that further by restricting actions for a role, but it never widens what Apify itself allows.
Can I stop an agent from changing things in Apify?
Yes. Restrictions in Elaichi apply per action, so you can let an agent read Apify datasets and run logs while restricting it from starting runs, aborting them, or editing and publishing tasks. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to an Apify connection when someone leaves?
Offboarding a person in Elaichi ends their access to Apify through every client at once. If they shared an Apify connection, it keeps working for everyone else on the team. Disconnecting Apify once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other connected client.
Does the Apify MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Apify 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, Microsoft Copilot, 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 Apify?
Yes. Both let Claude, ChatGPT or Cursor use Apify. 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 Apify call.
How is Elaichi different from Composio for Apify?
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 Apify: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Apify in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot