Skip to main content
Glama
userFRM

kimi-code-mcp

by userFRM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to kimi-code-mcp

No user-submitted related servers found.

    Related Servers

    • kimi-api-mcp

      bene-bosco
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides file operations and Moonshot API-powered tools (reasoning, code review, testing, research, web search, agent) for Kimi K2.5, requiring only a Moonshot API key.
      478 npm
      1
      MIT

    • firepass-mcp

      jameshgrn
      A
      license
      A
      quality
      C
      maintenance
      MCP server that turns Kimi K2.6 Turbo into an agentic coding assistant with tools for file operations, shell commands, and code search.
      4
      2
      MIT

    • emcp

      slezica
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing filesystem operations, shell execution, and web search capabilities.
      -

    • pi-mcp

      zhaob1n
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing pi coding-agent tools for file and shell operations, including read, write, edit, bash, grep, find, and ls.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: file operations (write/read/edit), search (glob/grep), web (search/fetch), and media analysis are unambiguous. Some potential overlap exists between agent, think, review, and research, but their descriptions differentiate them sufficiently for agent selection.

    Naming Consistency4/5

    All tools share the consistent 'kimi_' prefix, which provides strong brand consistency. However, the suffix style varies: some are verb_noun (write_file, read_media), while others are single verbs or nouns (glob, shell, think, review). This is a minor deviation from a strict verb_noun pattern but remains predictable.

    Tool Count5/5

    With 14 tools, the server is well within the ideal 3-15 range. Each tool covers a distinct capability area for a coding assistant, and none feel redundant or superfluous. The count feels appropriately scoped for the server's purpose.

    Completeness4/5

    The tool surface covers core coding needs: file manipulation, search, shell execution, web access, and specialized tasks like review, test, and research. Minor gaps exist (e.g., no explicit delete or rename file tool), but these can be handled by the agent or shell tools, so agents can work around them.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources