--- title: Install the Apify plugin in your AI agent url: https://docs.apify.com/agents/plugins.md parents: - [Apify documentation](https://docs.apify.com/llms.txt) - [Connect your AI agent to Apify](https://docs.apify.com/agents.md) previous: [Overview](https://docs.apify.com/agents.md) next: [MCP server](https://docs.apify.com/mcp.md) --- > ## Documentation index > Fetch the complete documentation index at: https://docs.apify.com/llms.txt > Use this file to discover all available pages before exploring further. # 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](https://docs.apify.com/mcp.md) and [Agent Skills](https://docs.apify.com/agents/skills.md) 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](https://docs.apify.com/mcp.md) and [Agent Skills](https://docs.apify.com/agents/skills.md) 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](https://docs.apify.com/mcp.md) at `https://mcp.apify.com`, preconfigured inside the plugin, for the live connection to the Apify platform. * Five [Agent Skills](https://docs.apify.com/agents/skills.md) covering scraping with existing Actors, Actor development, actorization, output schemas, and application integration. * An `apify` routing 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](https://github.com/apify/apify-claude-code-plugin) | | Codex (app and CLI) | Yes | Yes | No | [apify/apify-codex-plugin](https://github.com/apify/apify-codex-plugin) | | Cursor | Yes | Yes | Yes | [apify/apify-cursor-plugin](https://github.com/apify/apify-cursor-plugin) | | GitHub Copilot and VS Code | Yes | Yes | Yes | [apify/apify-github-copilot-plugin](https://github.com/apify/apify-github-copilot-plugin) | | OpenCode | Yes | Yes | Yes | [opencode-apify](https://github.com/apify/apify-opencode-plugin) | | Grok Build | Yes | Yes | Yes | [apify/apify-grok-build-plugin](https://github.com/apify/apify-grok-build-plugin) | | Kimi Code | Yes | Yes | No | [apify/apify-kimi-code-plugin](https://github.com/apify/apify-kimi-code-plugin) | | Qoder and Qwen Code | Yes | Yes | Yes | [apify/apify-qoder-plugin](https://github.com/apify/apify-qoder-plugin) | | DeepSeek Harness | Yes | Yes | No | [dsh-apify-plugin](https://github.com/apify/apify-deepseek-harness-plugin) | | OpenClaw | Native tool | No | No | [@apify/apify-openclaw-plugin](https://github.com/apify/apify-openclaw-plugin) | | Hermes Agent | Native tools | Routing skill | No | [apify-hermes-agent-plugin](https://github.com/apify/apify-hermes-agent-plugin) | | Kilo Code | Native tool | No | No | [@apify/kilocode-plugin](https://github.com/apify/kilocode-plugin) | If your agent isn't listed, connect the [MCP server](https://docs.apify.com/mcp.md) directly and install [Agent Skills](https://docs.apify.com/agents/skills.md#install) separately. The [MCP configurator](https://mcp.apify.com) 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** 1. In Claude Code, add the Apify marketplace, install the plugin, and reload: ```text /plugin marketplace add apify/apify-claude-code-plugin /plugin install apify@apify /reload-plugins ``` 2. Run `/mcp`, open `plugin: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](https://docs.apify.com/integrations/claude-code-cli.md). **Codex** In the Codex app: 1. Open **Plugins** in the left sidebar, select the dropdown next to **+**, and choose **Add marketplace**. 2. Enter the Apify plugin repository in the **Source** field and select **Add marketplace**: ```text apify/apify-codex-plugin ``` 3. Open the **Personal** tab and select **Add** next to **Apify**. 4. Select **Add to Codex**, then **Install Apify**. Codex opens the Apify sign-in in your browser. In the Codex CLI: 1. Run `/plugins` and open the **Add Marketplace** tab. 2. Enter the Apify plugin repository: ```text apify/apify-codex-plugin ``` 3. 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](https://docs.apify.com/integrations/codex-app.md) or [Codex CLI guide](https://docs.apify.com/integrations/codex-cli.md). **Cursor** 1. In the Cursor agent chat, run: ```text /add-plugin apify ``` You can also search for `Apify` under **Plugins** in Cursor Settings, or install it from the [Cursor Marketplace](https://cursor.com/marketplace/apify). 2. 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](https://docs.apify.com/integrations/cursor.md). **GitHub Copilot** In the GitHub Copilot CLI, install the plugin from the [Awesome Copilot](https://awesome-copilot.github.com/plugins) marketplace, which the CLI registers by default: ```text /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](https://docs.apify.com/integrations/github-copilot-cli.md) or [desktop app guide](https://docs.apify.com/integrations/github-copilot-desktop.md). **VS Code** 1. Open the Extensions view and enter `@agentPlugins apify` in the search field. 2. Select **Install** on the `apify` entry from the Awesome Copilot marketplace, then confirm the trust prompt. 3. 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](https://docs.apify.com/integrations/vscode.md). **OpenCode** 1. In your project, install the plugin from npm: ```bash opencode plugin opencode-apify ``` 2. Start the Apify sign-in: ```bash opencode mcp auth apify ``` Read the full [OpenCode guide](https://docs.apify.com/integrations/opencode.md). **Grok Build** In Grok Build, install the plugin from its repository: ```text /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](https://github.com/apify/apify-grok-build-plugin) for details. **Kimi Code** 1. In Kimi Code, install the plugin from its repository, then reload the session: ```text /plugins install https://github.com/apify/apify-kimi-code-plugin /reload ``` You can also run `/plugins`, switch to the **Curated** tab, and select **Apify**. 2. Kimi Code doesn't start the sign-in on its own, so run it once: ```text /mcp-config login apify ``` Read the full [Kimi Code CLI guide](https://docs.apify.com/integrations/kimi-code-cli.md). **Qoder** 1. In the Qoder CLI, run `/plugins`, open the **Marketplaces** tab, and add the Apify plugin repository: ```text https://github.com/apify/apify-qoder-plugin ``` 2. Install the `apify` plugin from the **Discover** tab, run `/plugins reload`, and restart the CLI. The Qoder IDE installs from the [Qoder Marketplace](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521) 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](https://docs.apify.com/integrations/qoder.md) or [Qwen Code guide](https://docs.apify.com/integrations/qwen.md). **DeepSeek Harness** 1. Install the plugin into the profile you launch, for example the `web` profile behind the web GUI: ```bash dsh plugin --profile web add dsh-apify-plugin ``` To use the terminal too, repeat the command with `--profile headless`. 2. DeepSeek Harness has no OAuth flow, so add your [Apify API token](https://console.apify.com/settings/integrations) to a `.env` file in the directory you launch `dsh` from, then restart the profile: ```bash APIFY_TOKEN= ``` Read the full [DeepSeek Harness guide](https://docs.apify.com/integrations/deepseek-harness.md). **OpenClaw** 1. Install the plugin from npm: ```bash openclaw plugins install @apify/apify-openclaw-plugin ``` 2. Run the setup wizard, which asks for your [Apify API token](https://console.apify.com/settings/integrations), then restart the gateway: ```bash openclaw apify setup openclaw gateway restart ``` Read the full [OpenClaw guide](https://docs.apify.com/integrations/openclaw.md). **Hermes Agent** 1. Install the plugin from PyPI and enable it: ```bash pip install apify-hermes-agent-plugin hermes plugins enable apify ``` 2. Save your [Apify API token](https://console.apify.com/settings/integrations) and enable the `apify` toolset: ```bash hermes apify-setup ``` Read the full [Hermes Agent guide](https://docs.apify.com/integrations/hermes-agent.md). **Kilo Code** 1. Install the plugin from npm: ```bash kilo plugin @apify/kilocode-plugin ``` 2. Store your [Apify API token](https://console.apify.com/settings/integrations) through Kilo's auth flow, then restart Kilo Code so the plugin picks it up: ```bash kilo auth login --provider apify ``` There's no Apify guide for Kilo Code yet, so check the [plugin README](https://github.com/apify/kilocode-plugin) 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](https://console.apify.com/settings/integrations). The DeepSeek Harness, OpenClaw, Hermes Agent, and Kilo Code plugins use an Apify API token instead. ## Related resources * [Agent Skills](https://docs.apify.com/agents/skills.md) - The bundled skills and how to install them on their own * [Apify MCP server](https://docs.apify.com/mcp.md) - Tool reference, authentication, and production practices * [For AI agents](https://docs.apify.com/agents.md) - Overview of the plugin, the MCP server, and Agent Skills