Kimi Code
Current Kimi Code configuration
The current Kimi Code reference uses ~/.kimi-code/mcp.json for the user and .kimi-code/mcp.json for a project. Merge:
{"mcpServers":{"morawp":{"url":"https://api.morawp.com/mcp"}}}
In the terminal UI, /mcp-config adds or edits servers. Complete browser authorization with:
/mcp-config login morawp
Use /mcp to inspect status. Start a new session after adding a server to a file; an existing session may not register its tools.
Earlier Kimi CLI releases
The separately published Kimi CLI reference uses kimi mcp commands:
kimi mcp add --transport http --auth oauth morawp https://api.morawp.com/mcp
kimi mcp auth morawp
Check kimi --version and kimi mcp --help before selecting this flow. Do not mix an older release's storage layout with the newer .kimi-code configuration.
Browser interface
Kimi CLI documents kimi web for a local browser UI. Configure and authenticate the server in the corresponding terminal environment first, then check its availability in a new web session. The hosted Kimi chat product is not the same local MCP client.
If it does not work
Check the configuration generation, active project, and authentication status. Keep static headers empty for MoraWP. To revoke access, disconnect the Agent in MoraWP and remove the client entry from the configuration you actually used.
Approve and check access
First connect a WordPress website in MoraWP. When the client opens sign-in, review the Workspace, websites, and Ability access before approving. Read only limits changes; enabled Integrations may still expose private fields. No static Agent key is needed.
In a new session with MoraWP enabled, ask:
Use MoraWP to list the websites this connection can access.
Do not create, edit, delete, or publish anything.
Check: the intended website appears. Then read one page to check WordPress access. A configured server alone is not proof of a working read.
For missing tools, see Missing Abilities. To stop access, disconnect the Agent in MoraWP and remove its local server entry. Local removal alone is not MoraWP revocation.
Official references
Current Kimi Code MCP reference · Kimi CLI command reference · Kimi CLI browser interface
Vendor instructions reviewed October 9, 2026. Client interfaces and account policies may change.