SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Make MCP with Kimi Code

Connect Kimi Code to Make MCP. Get all available make operations, show supported languages for make automations, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Make logoMake
Api Key

Make is an automation platform that connects your favorite apps and services. Build powerful, custom workflows without writing code.

53 Tools

How to integrate Make 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 Make account to Kimi Code via Composio Connect, so it can get all available Make operations, show supported languages for Make automations, list all timezones used in Make, and more without ever putting your account credentials at risk.

Also integrate Make with

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKClaude Agent SDKCodexGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Why use Composio?

Composio provides:

  • Access to 1,500+ 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 Make 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 Make account

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

For example, ask it to:

  • "Get all available Make operations"
  • "Show supported languages for Make automations"
  • "List all timezones used in Make"

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

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

Conclusion

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

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

TOOLS

Supported Tools

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

Activate Scenario

Activate a Make scenario; a regularly scheduled scenario may run immediately, executing its configured automation and external effects.

Create Hook

Create a hook without exposing its bearer-like URL, UDID, or relay data.

Create Organization

Tool to create a new organization in Make.

Create Scenario

Create a Make scenario from JSON-encoded blueprint and scheduling data.

Create Password Reset Demand

Tool to create a password reset demand for a user by their email address.

Deactivate Scenario

Deactivate a Make scenario and stop it if it is currently running.

Delete Scenario

Move a Make scenario to trash, where it can be restored for 30 days.

Get Cashier Prices

Tool to retrieve a specific cashier price by its identifier.

Get Cashier Products

Tool to retrieve available cashier products from Make.

Get Connection

Retrieve one Make connection by ID.

Get Current Authorization

Tool to retrieve current authorization details for the authenticated user.

Get Enums Apps Review Statuses

Tool to retrieve available app review statuses in Make.

Get Enums IMT Regions

Tool to retrieve the list of Make regions and their regionId values.

Get Enums IMT Zones

Tool to retrieve available IMT zones in Make.

Get Enums LLM Models

Tool to retrieve available Large Language Models from Make.

Get Enums Module Types

Tool to retrieve available module types in Make.

Get Enums Organization Features

Tool to retrieve available organization features in Make.

Get Enums User API Token Scopes

Tool to retrieve all available API token scopes in Make.

Get Enums User Email Notifications

Tool to retrieve available email notification types for Make users.

Get Enums User Features

Retrieve the list of all existing user features and their descriptions.

Get Enums Variable Types

Tool to retrieve available variable types in Make.

Get Hook

Retrieve a hook without exposing its bearer-like URL, UDID, or relay data.

Get Hook Incoming Activity

Get hook queue statistics or safe metadata for one incoming event; payload values are not returned.

Get Hook Log

Retrieve safe status and timing diagnostics for one Make webhook execution log.

Get Operations

Retrieve daily operations usage for an organization over the past 30 days.

Get Organization

Retrieve detailed information about one Make organization by ID.

Get Public Template Blueprint

Retrieve the complete blueprint for a public approved Make template.

Get Scenario

Retrieve one Make scenario by ID with optional selected columns.

Get Scenario Blueprint

Retrieve a sanitized current, draft, or historical scenario blueprint; credential-bearing URL, auth, header, query, password, secret, and token fields are omitted.

Get Scenario Execution

Retrieve the status, outputs, pause metadata, or error for one execution.

Get Scenario Interface

Retrieve a Make scenario's declared input and output interface.

Get Scenario Logs

List scenario logs, list one module's operation logs, or retrieve one execution log according to the identifiers supplied.

Get Scenario Trigger

Retrieve safe trigger details without exposing its URL or UDID.

Get Team

Retrieve detailed information about a specific team by its ID.

Get Current User

Tool to retrieve information about the current authenticated user.

List Connections

List the connections belonging to a Make team.

List Enums Countries

Retrieve all supported countries in Make.

List Enums Languages

Tool to retrieve a list of language codes and names.

List Enums LLM Builtin Tiers

Retrieve all predefined LLM tiers (small, medium, large) with their associated models, providers, and pricing coefficients.

List Enums Locales

Retrieve all supported locales in Make.

List Enums Timezones

Retrieve all supported timezones in Make.

List Hook Logs

List safe summary metadata for a Make webhook's retained execution logs.

List Incomplete Executions

List failed or unfinished executions for a Make scenario.

List Organizations

Tool to list organizations the authenticated user belongs to (including organizationId, name, and timezoneId).

List Public Templates

Browse public approved Make templates with filters and offset pagination.

List Scenarios

List scenarios belonging to a Make team with offset pagination.

List Teams

Tool to list all teams within an organization.

Ping API

Tool to ping the Make API to verify connectivity and service availability.

Run Scenario

Run an already active Make scenario, executing its configured automation and external effects.

Set SDK Connection API

Replace the complete API definition for a Make SDK app connection.

Update Scenario

Partially update a Make scenario, leaving omitted properties unchanged; optionally authorize installation of an app newly used by the organization.

Update Scenario Interface

Replace an on-demand scenario's input specification; requires Make Pro+.

Verify Connection

Test whether a Make connection's saved credentials can reach its provider.

FRAMEWORKS

How to build Make MCP Agent with another framework

Claude Code logo

Claude Code

Use Make MCP with Claude Code

Cursor logo

Cursor

Use Make MCP with Cursor

ChatGPT logo

ChatGPT

Use Make MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Make MCP with Claude Cowork

Antigravity logo

Antigravity

Use Make MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Make MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Make MCP with Claude Agent SDK

Codex logo

Codex

Use Make MCP with Codex

Grok Build logo

Grok Build

Use Make MCP with Grok Build

VS Code logo

VS Code

Use Make MCP with VS Code

OpenCode logo

OpenCode

Use Make MCP with OpenCode

OpenClaw logo

OpenClaw

Use Make MCP with OpenClaw

Hermes logo

Hermes

Use Make MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Make MCP with Atomic Agent

CLI logo

CLI

Use Make MCP with CLI

Google ADK logo

Google ADK

Use Make MCP with Google ADK

LangChain logo

LangChain

Use Make MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Make MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Make MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Make MCP with LlamaIndex

CrewAI logo

CrewAI

Use Make MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Make MCP with Pydantic AI

AutoGen logo

AutoGen

Use Make MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Make MCP server, the agents and LLMs can only access a fixed set of Make tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Make 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 Make tools.

Yes, absolutely. You can configure which Make 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 Make data and credentials are handled as safely as possible.

Start with Make.It takes 30 seconds.

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

Start building