Apify MCP server
Apify is a platform for building, running, and managing web scraping and automation programs called Actors, used by developers and data teams to pull structured data from the web at scale. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for Apify.
Inspect Actor inputs and pricing
Use when preparing a run: returns current pricing, run defaults and a bounded input schema summary. Check truncated and schemaUnavailable; omitted details are not validation rules. Null pricing means unknown, not free. Prices depend on plan and platform usage.
Start an Actor
Use when starting an approved Actor after get_actor reveals its inputs and pricing. Each call starts a paid run with a spend cap; poll get_run. Omitted timeout preserves the Actor default.
Get Actor run status
Use when checking whether an Actor run has finished or retrieving its dataset and store IDs. Returns immediately; a failed run is returned as lifecycle status. Cost totals may remain preliminary just after completion.
8 Apify actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
6Look things up, subject to your permissions.
- apify.get_actorInspect Actor inputs and pricing
Use when preparing a run: returns current pricing, run defaults and a bounded input schema summary. Check truncated and schemaUnavailable; omitted details are not validation rules. Null pricing means unknown, not free. Prices depend on plan and platform usage.
- apify.get_runGet Actor run status
Use when checking whether an Actor run has finished or retrieving its dataset and store IDs. Returns immediately; a failed run is returned as lifecycle status. Cost totals may remain preliminary just after completion.
- apify.get_dataset_itemsRead dataset items
Use when fetching JSON results from an Actor dataset. Reads at most 100 rows per page; follow nextOffset until null. Storage and transfer usage may be charged. Oversized JSON is rejected rather than silently truncated.
- apify.list_actorsList account Actors
Use when choosing an Actor previously created or used by the connected account. Set my to list only owned Actors. Follow nextOffset to retrieve subsequent pages.
- apify.search_actorsSearch the Actor Store
Use when discovering public Actors for a scraping task. Searches names, descriptions and documentation, returning IDs and summaries. Use get_actor to inspect input schema and pricing before starting a run.
- apify.get_store_recordRead a JSON store record
Use when reading a JSON store record up to 100k characters. INPUT may contain secrets; retrieve only when authorized. Binary/HTML and redirected records are unsupported (redirects fail closed). Storage/transfer may be charged.
write
1Create and change things. Allow, or ask the user first.
- apify.run_actorStart an Actor
Use when starting an approved Actor after get_actor reveals its inputs and pricing. Each call starts a paid run with a spend cap; poll get_run. Omitted timeout preserves the Actor default.
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- apify.abort_runAbort an Actor run
Use when a running Actor job is no longer needed. Stops the job; already incurred charges remain. Graceful abort allows state persistence. Runs already in a terminal state remain unchanged.
Control access to Apify.
Connect the intended Apify account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- apify.run_actor: require approval
- apify.abort_run: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Apify connects.
Connect Apify using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Apify with your AI client.
Sign in to Arc0 and connect Apify in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Apify with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingApify with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingApify with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingApify with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingApify with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingApify with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
Apify and Arc0, answered.
Does Apify work with Claude Desktop and Claude Code?
Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use Apify with OpenAI Codex, ChatGPT and Cursor?
Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official Apify MCP server?
This is Arc0’s integration page, not a claim of an official Apify server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Apify for its own current MCP offerings.
Which Apify actions are supported?
8 registry-defined actions: 6 read, 1 write and 1 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does Apify need?
Connect Apify using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in Apify?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does Apify through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Plug Apify into your agent.
Apify MCP server: 8 actions including inspect actor inputs and pricing, start an actor, get actor run status. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Apify and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Apify.