Install the Apify plugin in your AI agent
The Apify plugin is the shortest way to connect a coding agent to Apify. One install configures the Apify MCP server and Agent Skills together.
Apify maintains a separate plugin for each agent, because each agent has its own plugin format and install flow. Check what your agent gets, then follow its install steps.
Why use the plugin
Without a plugin, you set up the MCP server and Agent Skills separately. The MCP server needs a configuration in your agent, and standalone skills need the skills CLI and an Apify CLI login. The plugin replaces the MCP configuration and the skills CLI with one install. It doesn't replace the Apify CLI. The Actor development, actorization, and scraping skills call it, so install it with npm install -g apify-cli and run apify login before you use them. Depending on the agent, you install the plugin for all your projects or for a single project.
What's included
Most plugins bundle three parts:
- The Apify MCP server at
https://mcp.apify.com, preconfigured inside the plugin, for the live connection to the Apify platform. - Five Agent Skills covering scraping with existing Actors, Actor development, actorization, output schemas, and application integration.
- An
apifyrouting agent that picks the right tool or skill from a plain-language request.
The OpenClaw, Hermes Agent, and Kilo Code plugins work differently. Instead of connecting to the MCP server, they register native Apify tools that start Actor runs and collect the results asynchronously, so the agent can keep working while an Actor runs.
Coverage by agent
| Agent | MCP server | Agent Skills | Routing agent | Plugin source |
|---|---|---|---|---|
| Claude Code | Yes | Yes | Yes | apify/apify-claude-code-plugin |
| Codex (app and CLI) | Yes | Yes | No | apify/apify-codex-plugin |
| Cursor | Yes | Yes | Yes | apify/apify-cursor-plugin |
| GitHub Copilot and VS Code | Yes | Yes | Yes | apify/apify-github-copilot-plugin |
| OpenCode | Yes | Yes | Yes | opencode-apify |
| Grok Build | Yes | Yes | Yes | apify/apify-grok-build-plugin |
| Kimi Code | Yes | Yes | No | apify/apify-kimi-code-plugin |
| Qoder and Qwen Code | Yes | Yes | Yes | apify/apify-qoder-plugin |
| DeepSeek Harness | Yes | Yes | No | dsh-apify-plugin |
| OpenClaw | Native tool | No | No | @apify/apify-openclaw-plugin |
| Hermes Agent | Native tools | Routing skill | No | apify-hermes-agent-plugin |
| Kilo Code | Native tool | No | No | @apify/kilocode-plugin |
If your agent isn't listed, connect the MCP server directly and install Agent Skills separately. The MCP configurator generates a configuration for most MCP clients.
Install
Pick your agent. Each tab shows the install commands, where to run them, and how to sign in. The full guide for each agent covers manual setup and troubleshooting.
- Claude Code
- Codex
- Cursor
- GitHub Copilot
- VS Code
- OpenCode
- Grok Build
- Kimi Code
- Qoder
- DeepSeek Harness
- OpenClaw
- Hermes Agent
- Kilo Code
-
In Claude Code, add the Apify marketplace, install the plugin, and reload:
/plugin marketplace add apify/apify-claude-code-plugin/plugin install apify@apify/reload-plugins -
Run
/mcp, openplugin:apify:apify, select Enable, then select Authenticate and complete the Apify sign-in in your browser.
You can also add the marketplace from the /plugins manager. Read the full Claude Code guide.
In the Codex app:
-
Open Plugins in the left sidebar, select the dropdown next to +, and choose Add marketplace.
-
Enter the Apify plugin repository in the Source field and select Add marketplace:
apify/apify-codex-plugin -
Open the Personal tab and select Add next to Apify.
-
Select Add to Codex, then Install Apify. Codex opens the Apify sign-in in your browser.
In the Codex CLI:
-
Run
/pluginsand open the Add Marketplace tab. -
Enter the Apify plugin repository:
apify/apify-codex-plugin -
Open the Apify Plugin tab, select Apify, and select Install plugin.
The CLI opens the Apify sign-in the first time it calls a tool that needs authentication, such as running an Actor. Read the full Codex app guide or Codex CLI guide.
-
In the Cursor agent chat, run:
/add-plugin apifyYou can also search for
Apifyunder Plugins in Cursor Settings, or install it from the Cursor Marketplace. -
In Cursor Settings, open Tools & MCPs, select Connect on the Apify MCP server, and complete the Apify sign-in in your browser.
Read the full Cursor guide.
In the GitHub Copilot CLI, install the plugin from the Awesome Copilot marketplace, which the CLI registers by default:
/plugin install apify@awesome-copilot
Copilot opens a browser tab for the Apify sign-in. In the desktop app, open Settings > Plugins, search for Apify, and select Install, then sign in from Settings > MCP servers.
Read the full GitHub Copilot CLI guide or desktop app guide.
- Open the Extensions view and enter
@agentPlugins apifyin the search field. - Select Install on the
apifyentry from the Awesome Copilot marketplace, then confirm the trust prompt. - When VS Code asks to authenticate the MCP server, select Allow and complete the Apify sign-in in your browser.
VS Code installs the same plugin as GitHub Copilot. Read the full VS Code guide.
-
In your project, install the plugin from npm:
opencode plugin opencode-apify -
Start the Apify sign-in:
opencode mcp auth apify
Read the full OpenCode guide.
In Grok Build, install the plugin from its repository:
/install-plugin https://github.com/apify/apify-grok-build-plugin
Grok Build opens the Apify sign-in on the first Actor run. There's no Apify guide for Grok Build yet, so check the plugin README for details.
-
In Kimi Code, install the plugin from its repository, then reload the session:
/plugins install https://github.com/apify/apify-kimi-code-plugin/reloadYou can also run
/plugins, switch to the Curated tab, and select Apify. -
Kimi Code doesn't start the sign-in on its own, so run it once:
/mcp-config login apify
Read the full Kimi Code CLI guide.
-
In the Qoder CLI, run
/plugins, open the Marketplaces tab, and add the Apify plugin repository:https://github.com/apify/apify-qoder-plugin -
Install the
apifyplugin from the Discover tab, run/plugins reload, and restart the CLI.
The Qoder IDE installs from the Qoder Marketplace page in one step, and the Desktop app and QoderWork import the plugin package from the same page. Qwen Code installs the Qoder plugin as an extension. Read the full Qoder guide or Qwen Code guide.
-
Install the plugin into the profile you launch, for example the
webprofile behind the web GUI:dsh plugin --profile web add dsh-apify-pluginTo use the terminal too, repeat the command with
--profile headless. -
DeepSeek Harness has no OAuth flow, so add your Apify API token to a
.envfile in the directory you launchdshfrom, then restart the profile:APIFY_TOKEN=<YOUR_API_TOKEN>
Read the full DeepSeek Harness guide.
-
Install the plugin from npm:
openclaw plugins install @apify/apify-openclaw-plugin -
Run the setup wizard, which asks for your Apify API token, then restart the gateway:
openclaw apify setupopenclaw gateway restart
Read the full OpenClaw guide.
-
Install the plugin from PyPI and enable it:
pip install apify-hermes-agent-pluginhermes plugins enable apify -
Save your Apify API token and enable the
apifytoolset:hermes apify-setup
Read the full Hermes Agent guide.
-
Install the plugin from npm:
kilo plugin @apify/kilocode-plugin -
Store your Apify API token through Kilo's auth flow, then restart Kilo Code so the plugin picks it up:
kilo auth login --provider apify
There's no Apify guide for Kilo Code yet, so check the plugin README for details.
Plugins that use the MCP server sign in through OAuth and keep the connection for future sessions. You can revoke access in Apify Console > Settings > Integrations. The DeepSeek Harness, OpenClaw, Hermes Agent, and Kilo Code plugins use an Apify API token instead.
Related resources
- Agent Skills - The bundled skills and how to install them on their own
- Apify MCP server - Tool reference, authentication, and production practices
- For AI agents - Overview of the plugin, the MCP server, and Agent Skills