claude-kimi-mcp-normalization
Skill10 starsChanged yesterdayMITView on GitHub
Use when importing or normalizing Claude Code MCP server declarations into Kimi Code without overwriting existing entries, especially after an import appears to succeed but servers are absent from Kimi
- Reads credentials
In this repository44 other files it gives its agents.
- llms-full.txtllms.txt
- llms.txtllms.txt
- ai-prompt-engineering-safety-reviewSkill
- ast-codemapSkill
- ast-grepSkill
- autoharnessSkill
- autonomous-backlog-driverSkill
- cli-self-updaterSkill
- code-frugalitySkill
- codemode-gatewaySkill
- codemode-typesSkill
- consequence-simulationSkill
- context-pruningSkill
- github-update-checkerSkill
- google-agents-cli-evalSkill
- google-agents-cli-scaffoldSkill
- history-searchSkill
- hook-gatingSkill
- hybrid-semantic-searchSkill
- kimi-code-agent-integrationSkill
- kimi-mcp-configurationSkill
- leann-vectorSkill
- log-summarizerSkill
- markdown-vagueSkill
- memory-reconciliationSkill
- mode-classificationSkill
- multiagent-orchestrationSkill
- output-compressionSkill
- prompt-injectionSkill
- python-anti-patternsSkill
- regression-sentinelSkill
- restart-trackingSkill
- rollback-guardSkill
- rust-call-graphSkill
- secrets-managementSkill
- security-best-practicesSkill
- session-compactorSkill
- sqlite-memorySkill
- swarm-barrierSkill
- swarm-dagSkill
- autoharnessSkill
- code-reliability-checksSkill
- skill-threat-rulesSkill
- autoharnessSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use for Claude Code MCP imports, source-to-target scope decisions, field conversion, disabled source servers, and unresolved environment …
- Distinctive: line 16
Keep user declarations user-global and project-local declarations project-local.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude-to-Kimi MCP normalization
When to use
Use for Claude Code MCP imports, source-to-target scope decisions, field conversion, disabled source servers, and unresolved environment placeholders.
Steps
- Resolve
CLAUDE_CONFIG_DIRbefore choosing the Claude home. Read Claude's user configuration only for an MCP import and inspect both user-scopemcpServersand the resolved project-root or current-directory entry underprojects. - Skip source-project names listed in
disabledMcpServers; do not silently re-enable them or convert that project choice into a global disabled entry. - Keep user declarations user-global and project-local declarations project-local. Preserve every existing Kimi entry and keep the existing Kimi entry on a name collision.
- Map stdio, HTTP, and SSE to Kimi's
mcpServersshape. MaptimeouttotoolTimeoutMsandalwaysLoad: truetodeferred: false; omit inferred transport except explicit SSE. - Drop Claude-only policy fields rather than pretending they work in Kimi. Report unsupported transports and entries blocked by unresolved placeholders.
- Convert an
Authorization: Bearer ${VAR}header tobearerTokenEnvVar: "VAR". Drop pass-through environment declarations because Kimi inherits the parent environment; never substitute a secret's current value into the preview or target. - Warn about apparent literal credentials and trusted-workspace requirements for project stdio servers. Direct file changes require a new session before
/mcpcan show them.
Reference: https://www.kimi.com/code/docs/en/kimi-code-cli/customization/mcp.html
How to verify
Compare source and normalized server names, scopes, launch commands or URLs, arguments, environment overlays, and timeouts. Confirm every skipped entry has a reason and every pre-existing Kimi entry is unchanged. Parse the final target JSON, then check /mcp in a new session for actual loading and connection status.
Facts found here
- Context7 accepts
CONTEXT7_API_KEYinstead of the--api-keyargument, so the literal key can be removed from imported arguments and supplied through the inherited environment. Source: https://www.npmjs.com/package/@upstash/context7-mcp
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

