Skip to content

kimi mcp Subcommand ​

kimi mcp is used to manage MCP (Model Context Protocol) server configurations. For concepts and usage of MCP, see Model Context Protocol.

sh
kimi mcp COMMAND [ARGS]

add ​

Add an MCP server configuration.

sh
kimi mcp add [OPTIONS] NAME [TARGET_OR_COMMAND...]

Arguments

ArgumentDescription
NAMEServer name, used for identification and reference
TARGET_OR_COMMAND...URL for http mode; command for stdio mode (must start with --)

Options

OptionShortDescription
--transport TYPE-tTransport type: stdio (default) or http
--env KEY=VALUE-eEnvironment variable (stdio only), can be specified multiple times
--header KEY:VALUE-HHTTP header (http only), can be specified multiple times
--auth TYPE-aAuthentication type (e.g., oauth, http only)

list ​

List all configured MCP servers.

sh
kimi mcp list

Output includes:

  • Configuration file path
  • Name, transport type, and target for each server
  • Authorization status for OAuth servers

remove ​

Remove an MCP server configuration.

sh
kimi mcp remove NAME

Arguments

ArgumentDescription
NAMEName of server to remove

auth ​

Authorize an MCP server that uses OAuth.

sh
kimi mcp auth NAME

This will open a browser for the OAuth authorization flow. After successful authorization, the token is cached in ~/.kimi/mcp-oauth/ for future use.

Arguments

ArgumentDescription
NAMEName of server to authorize

TIP

Only servers added with --auth oauth require this command.

reset-auth ​

Clear the cached OAuth token for an MCP server.

sh
kimi mcp reset-auth NAME

Arguments

ArgumentDescription
NAMEName of server to reset authorization

After clearing, you need to run kimi mcp auth again to re-authorize.

After upgrading from older versions that used FastMCP 2.x, existing OAuth MCP tokens are not migrated automatically; if kimi mcp list shows that authorization is required, run kimi mcp auth NAME again.

test ​

Test connection to an MCP server and list available tools.

sh
kimi mcp test NAME

Arguments

ArgumentDescription
NAMEName of server to test

Output includes:

  • Connection status
  • Number of available tools
  • Tool names and descriptions