How to integrate Apify MCP with Kimi Code

How to integrate Apify MCP with Kimi Code Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools. In this guide, I will explain the easiest and most secure way to connect your Apify account to Kimi Code via Composio Connect, so it can create a new dataset for scraped results, fetch items from a specific Apify dataset, get details of your latest Apify actor, and more without ever putting your account credentials at risk.

Apify logoApify
Api Key

Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.

112 Tools

How to integrate Apify MCP with Kimi Code

Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools.

In this guide, I will explain the easiest and most secure way to connect your Apify account to Kimi Code via Composio Connect, so it can create a new dataset for scraped results, fetch items from a specific Apify dataset, get details of your latest Apify actor, and more without ever putting your account credentials at risk.

Also integrate Apify with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Managed OAuth. You do not have to worry about authentication and authorization flows for every app.
  • Programmatic tool calling. Allows LLMs to write code in a remote workbench to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Connect Apify to Kimi Code

Kimi Code is a TypeScript agent distributed through npm. It acts as an MCP client and reads server definitions from an mcp.json file, and it can also add and authenticate servers conversationally through /mcp-config. Composio is a remote HTTP server that authenticates with OAuth, so no API key is stored anywhere.

1. Install Kimi Code

The quickest way is the official install script, which requires no pre-installed Node.js and places the kimi executable on your PATH.

bash
# macOS or Linux
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash

# Windows PowerShell
irm https://code.kimi.com/kimi-code/install.ps1 | iex

# Confirm the installation
kimi --version

2. Log in

Start Kimi Code in your project directory, then sign in from the interactive UI:

bash
kimi

Run /login and choose Kimi Code OAuth using the device-code flow, or use a Moonshot API key.

3. Add Composio with /mcp-config

In current versions of Kimi Code, MCP servers are managed inside the app, not with a shell subcommand. From the interactive UI, run:

bash
/mcp-config
Kimi Code MCP config flow for adding the Composio MCP server

Tell it the server name and URL in plain language. For example:

Server name is Composio, and here is the server URL: https://connect.composio.dev/mcp

Kimi Code asks whether to add it globally, at ~/.kimi-code/mcp.json, or project-local for the current checkout, then writes the entry for you:

bash
{
  "mcpServers": {
    "Composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

There is no transport field to set. Kimi Code infers HTTP from the url.

4. Restart the session

The new server is picked up on a fresh session, not the current one. Start a new session:

bash
/new

On the new session, Kimi Code detects that the server needs authorization and prompts you to run:

bash
/mcp-config login Composio

5. Authorize with OAuth

Run the command Kimi suggests:

bash
/mcp-config login composio

Kimi Code opens Composio's authorization page or surfaces a URL. Approve access, then return to the session. You should see confirmation that the Composio MCP server is connected.

Composio authorization page for Kimi Code MCP setup

Check the connection status any time with /mcp. Composio should appear as connected with its tools listed.

Kimi Code showing Composio connected after OAuth authorization

Connect your Apify account

Back in a Kimi Code session, ask the agent to connect to Apify or give it any Apify-related task.

For example, ask it to:

  • "Create a new dataset for scraped results"
  • "Fetch items from a specific Apify dataset"
  • "Get details of your latest Apify actor"

It will prompt you to authenticate and authorize access to Apify.

That is it. Composio tools are now available in Kimi Code, and your Apify account is ready to use.

Conclusion

You have successfully connected Apify to Kimi Code using Composio Connect. Your agent can now manage Apify from the terminal with natural language, without exposing credentials in prompts or local scripts.

Since the same Composio endpoint exposes 1,000+ apps, you can add Slack, Calendar, Linear, and more to the same server and chain them into cross-app workflows.

TOOLS

Supported Tools

Every Apify action and event your agent gets out of the box.

Build Actor

Tool to build an Actor with specified configuration.

Abort Actor Build

Tool to abort an Actor build that is starting or running.

Delete Actor Build

Tool to delete an Actor build permanently.

Get Actor Build

Tool to get detailed information about a specific Actor build.

Get Actor Build Log

Tool to retrieve the log file for a specific Actor build.

Get user builds list

Tool to get a paginated list of all builds for a user.

Abort Actor Run

Tool to abort a running or starting Actor run.

Delete Actor Run

Tool to delete a finished Actor run.

Get Actor Run

Tool to get details about a specific Actor run.

Update Actor Run Status Message

Tool to update the status message of an Actor run.

Delete Actor Task

Tool to delete an Actor task permanently.

Get Actor Task

Tool to get complete details about an Actor task.

Update Actor Task

Tool to update Actor task settings using JSON payload.

Get last actor task run

Tool to get the most recent run of a specific Actor task.

Run Task Sync (GET)

Tool to run a specific task synchronously and return its output.

Run Task Sync & Get Dataset Items

Tool to run an actor task synchronously and retrieve its dataset items.

Run Task Sync with Input Override & Get Dataset Items

Tool to run an actor task synchronously with input overrides and retrieve its dataset items.

Run Task Sync (POST)

Tool to run an Actor task synchronously with input override and return its output.

Update Actor

Tool to update Actor settings using JSON payload.

Get last actor run

Tool to get the most recent run of a specific Actor.

Run Actor Sync without Input (GET)

Tool to run a specific Actor synchronously without input and return its output.

Run Actor Sync & Get Dataset Items

Tool to run Actor synchronously and get dataset items.

Get list of Actors

Tool to get the list of all Actors that the user created or used.

Delete Actor Version

Tool to delete a specific version of an Actor's source code.

Delete Actor Version Environment Variable

Tool to delete an environment variable from a specific Actor version.

Get Actor Version Environment Variable

Tool to get environment variable details for a specific Actor version.

Update Actor Version Environment Variable

Tool to update environment variable for a specific Actor version using JSON payload.

Get list of Actor version environment variables

Tool to get the list of environment variables for a specific Actor version.

Create Actor Version Environment Variable

Tool to create an environment variable for a specific Actor version.

Get Actor version

Tool to get details about a specific version of an Actor.

Update Actor Version

Tool to update an Actor version's configuration and source code.

Get list of Actor versions

Tool to get the list of versions of a specific Actor.

Create Actor Version

Tool to create a new version of an Actor.

Get list of Actor webhooks

Tool to get a list of webhooks for a specific Actor.

Create Actor

Tool to create a new Actor with specified configuration.

Create Dataset

Tool to create a new dataset.

Create Actor Task

Tool to create a new Actor task with specified settings.

Create Task Webhook

Tool to create a webhook for an Actor task.

Delete Dataset

Tool to delete a dataset permanently.

Get Dataset

Tool to retrieve dataset metadata by dataset ID.

Update Dataset

Tool to update a dataset's name via JSON payload.

Get list of datasets

Tool to get list of datasets for a user.

Get Dataset Statistics

Tool to get dataset field statistics by dataset ID.

Delete Actor

Tool to delete an Actor permanently.

Delete Webhook

Tool to delete a webhook by its ID.

Get Actor Details

Tool to get details of a specific Actor.

Get Actor Last Run Dataset Items

Tool to get dataset items from the last run of an Actor.

Get all webhooks

Tool to get a list of all webhooks created by the user.

Get dataset items

Tool to retrieve items from a dataset.

Get Default Build

Tool to get the default build for an Actor.

Get Key-Value Record

Tool to retrieve a record from a key-value store.

Get list of builds

Tool to get a list of builds for a specific Actor.

Get list of runs

Tool to get a list of runs for a specific Actor.

Get list of task runs

Tool to get a list of runs for a specific Actor task.

Get list of tasks

Tool to fetch a paginated list of tasks belonging to the authenticated user.

Get list of task webhooks

Tool to get a list of webhooks for a specific Actor task.

Get log

Tool to retrieve logs for a specific Actor run or build.

Get OpenAPI Definition

Tool to get the OpenAPI definition for a specific Actor build.

Get Run Dataset Items

Tool to get dataset items from a specific Actor run.

Get Task Input

Tool to retrieve the input configuration of a specific task.

Get Task Last Run Dataset Items

Tool to get dataset items from the last run of an Actor task.

Delete Key-Value Store

Tool to delete a key-value store permanently.

Get Key-Value Store

Tool to retrieve key-value store metadata by store ID.

Get Key-Value Store Keys

Tool to retrieve a list of keys from a key-value store.

Delete Key-Value Store Record

Tool to delete a record from a key-value store.

Check Key-Value Store Record Exists

Tool to check if a record exists in a key-value store.

Get list of key-value stores

Tool to get the list of key-value stores owned by the user.

Create Key-Value Store

Tool to create a new key-value store or retrieve an existing one by name.

List User Actor Runs

Tool to get a paginated list of all Actor runs for the authenticated user.

Delete Request Queue

Tool to delete a request queue permanently.

Get Request Queue

Tool to retrieve request queue metadata by queue ID.

Get Request Queue Head

Tool to retrieve first requests from the queue for inspection.

Get Head and Lock Queue Requests

Tool to get and lock head requests from the queue.

Update Request Queue

Tool to update request queue name using JSON payload.

Delete Request from Queue

Tool to delete a specific request from a request queue.

Get Request from Queue

Tool to retrieve a specific request from a request queue by its ID.

Delete Request Lock

Tool to delete a request lock from a request queue.

Prolong Request Lock

Tool to prolong request lock in a request queue.

Update Request in Queue

Tool to update a request in a request queue.

Batch Delete Requests from Queue

Tool to batch-delete up to 25 requests from a queue.

Batch Add Requests to Queue

Tool to batch-add up to 25 requests to a request queue.

List Request Queue Requests

Tool to list requests in a request queue with pagination support.

Add Request to Queue

Tool to add a request to the queue.

Unlock Queue Requests

Tool to unlock requests in a request queue that are currently locked by the client.

Get list of request queues

Tool to get list of request queues for a user.

Create Request Queue

Tool to create a new request queue or retrieve an existing one by name.

Run Actor Asynchronously

Tool to run a specific Actor asynchronously.

Run Actor Sync

Tool to run a specific Actor synchronously with input and return its output record.

Run Actor Sync & Get Dataset Items

Tool to run an Actor synchronously and retrieve its dataset items.

Run Task Asynchronously

Tool to run a specific Actor task asynchronously.

Delete Schedule

Tool to delete a schedule by its ID.

Get Schedule

Tool to get schedule details by ID.

Get Schedule Log

Tool to get schedule log by ID.

Update Schedule

Tool to update an existing schedule with new settings.

Get list of schedules

Tool to get list of schedules created by the user.

Create Schedule

Tool to create a new schedule with specified settings.

Store Data in Dataset

Tool to store data items in a dataset.

Store Data in Key-Value Store

Tool to create or update a record in a key-value store.

Get list of Actors in Store

Tool to get list of public Actors from Apify Store.

Update Key-Value Store

Tool to update a key-value store's properties.

Update Task Input

Tool to update the input configuration of a specific Actor task.

Get Public User Data

Tool to get public user data.

Get Current User Account Data

Tool to get private user account information.

Get Account Limits

Tool to get a complete summary of account limits and usage.

Update Account Limits

Tool to update account limits manageable on the Limits page.

Get Monthly Usage

Tool to get monthly usage summary with daily breakdown.

Get list of webhook dispatches

Tool to get list of webhook dispatches for the user.

Get Webhook Dispatch

Tool to get webhook dispatch object with all details.

Get webhook

Tool to get webhook object with all details.

Update Webhook

Tool to update webhook using JSON payload.

Test Webhook

Tool to test a webhook by creating a test dispatch with a dummy payload.

Get webhook dispatches

Tool to get list of webhook dispatches for a specific webhook.

FAQ

Frequently asked questions

With a standalone Apify MCP server, the agents and LLMs can only access a fixed set of Apify tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Apify and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Kimi Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Apify tools.

Yes, absolutely. You can configure which Apify scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Apify data and credentials are handled as safely as possible.

Start with Apify.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Apify tool your agent needs.Free to start.

Start building