How to connect Apify to Cursor

  • Cursor gets 19 Apify tools through one Metorial MCP URL.
  • Setup is 3 steps; teammates then sign in with SSO.
  • You need Cursor with MCP support.

What Cursor can do with Apify

Ask your agent in plain language. Each of these maps to a real tool on the server.

  • Ask Cursor to use the push dataset items tool in Apify
  • Ask Cursor to use the build actor tool in Apify
  • Ask Cursor to use the list actors tool in Apify
  • Ask Cursor to use the manage request queue tool in Apify
  • Ask Cursor to use the search store actors tool in Apify

Add the Apify MCP server to Cursor

Run these once. Afterwards, everyone you give access to signs in the same way.

  1. 1. Enable Apify in Metorial

    In your Metorial portal, enable the Apify MCP server and sign in with the account that owns the data. Access stays governed by your team policies.

  2. 2. Add Metorial to your MCP config

    Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.

    {
    "mcpServers": {
    "metorial": {
    "url": "<your-magic-mcp-url>"
    }
    }
    }
  3. 3. Sign in

    Open Customize in the sidebar, find Metorial and sign in to load Apify tools.

Give your team Apify in Cursor

Once Apify is enabled in Metorial, teammates sign in with SSO and get the same connection in Cursor, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Apify tools available in Cursor

Full descriptions and inputs are on the Apify MCP server page.

  • Run Actor: Start an Apify Actor run.
  • Manage Task: Create, get, update, delete, list, or run Apify Actor Tasks.
  • Manage Actor: Get, create, update, or delete an Apify Actor owned by the authenticated account.
  • List Runs: List Apify Actor runs either account-wide or for a specific Actor.
  • Abort Run: Abort a running Apify Actor execution.
  • Manage Webhook: Create, get, update, test, delete, or list Apify webhooks for Actor run and build events.
  • Get Dataset Items: Retrieve or export items from an Apify dataset.
  • Manage Schedule: Create, get, update, delete, or list Apify schedules that run Actors or Actor Tasks on a cron expression.
  • Manage Key-Value Store: Manage Apify key-value stores and records.
  • Get Run: Retrieve an Apify Actor run by ID, optionally including JSON dataset items or the run log as a Slate attachment.
  • Push Dataset Items: Append JSON objects to an Apify dataset.
  • Build Actor: Start an Apify Actor build, retrieve build details, or list builds for an Actor.
  • List Actors: List Actors owned by the authenticated Apify account.
  • Manage Request Queue: Manage Apify request queues and queued crawler requests.
  • Search Store Actors: Search public Apify Store Actors.
  • And 4 more on the Apify MCP server page.

Using Apify tools in Cursor

What to expect once Apify is connected.

  • Cursor picks MCP tools automatically when they are relevant, including in Plan Mode. Name a Apify tool to steer it.
  • Cursor asks for approval before it uses an MCP tool by default. Click the arrow next to the tool name to check the arguments first.
  • Switch the Metorial server off from Customize in the sidebar without removing it.
  • Cursor shows each Apify tool response in chat, with expandable views of the arguments and the result.

Troubleshooting Cursor

Metorial connects but tools are missing or failing
Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.
Your company blocks the server
Enterprise admins approve remote servers in Team Settings, then MCP Configuration. Ask them to add a URL entry for your Metorial URL.
Cursor asks before every tool call
That is the default. Allowlist the Metorial tools you trust in your Run Mode settings to run them without a prompt.

Based on the Cursor MCP documentation.

Frequently asked questions

Common questions about connecting Apify to AI agents with Metorial.

  1. Does Cursor support the Apify MCP server?
    Yes. Cursor connects to the Apify MCP server through its MCP config file, pointed at your Metorial URL. You need Cursor with MCP support.
  2. No. You sign in to Apify once through Metorial, and Cursor uses that connection. No API keys go into Cursor's settings.
  3. All 19 Apify tools your team allows, such as Run Actor, Manage Task, Manage Actor. Admins can narrow that list per team.
  4. Yes. Role-based access control decides who can use Apify and which of its tools appear in Cursor, and every call is logged with the person's identity.
  5. Open the Output panel (Cmd+Shift+U), choose MCP Logs, and look for authentication or connection errors.