Skip to main content
Glama

cody-mcp

A Model Context Protocol server for Cody — AI teammates that work inside the tools you already use.

cody-mcp exposes Cody's integration catalog, team-knowledge search and product answers as MCP tools, so any MCP-capable client (Claude Desktop, Claude Code, Cursor, VS Code, custom agents) can call them directly.

Docs and product: https://agentcody.ai

Tools

Tool

Input

What it does

search_team_knowledge

query (string), limit (1–10, optional)

Ranked search over Cody's knowledge base (setup, support automation, MCP, integrations). Returns titles, summaries and canonical URLs.

list_integrations

category (optional), search (optional)

Lists the tools Cody connects to — Zendesk, Jira, Slack, HubSpot, Airtable, Mixpanel and more — with categories and docs links.

ask_cody

question (string)

Answers product questions (pricing, setup, integrations, MCP support, data handling) with the source URLs it drew from.

Every tool returns both human-readable text and a machine-readable structuredContent payload. All three are deterministic and fully offline — no API keys, no network calls, no stubs that throw.

Related MCP server: kb-mcp

Install

npm install -g cody-mcp

Or run it without installing:

npx -y cody-mcp --version

Requires Node.js 18 or newer.

Configure your MCP client

Add the server to your client's MCP configuration.

Claude Desktop (claude_desktop_config.json) / Claude Code (.mcp.json) / Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "cody": {
      "command": "npx",
      "args": ["-y", "cody-mcp"]
    }
  }
}

Restart the client and the three cody-mcp tools become available to the model.

Example

Ask your client:

Use cody-mcp to find out how Cody handles Zendesk ticket triage, then list the support integrations.

The model calls search_team_knowledge with {"query": "zendesk ticket triage"} and list_integrations with {"category": "Support"}, and answers from the structured results.

Development

git clone https://github.com/daolmedo/cody-mcp.git
cd cody-mcp
npm install
npm run build
npm run smoke     # spawns the server over stdio and calls all three tools

The smoke test starts the compiled server as a real MCP stdio process, performs the MCP handshake, lists the tools and invokes each one, asserting structured results come back.

Registry manifest

server.json describes the package in the format MCP registries consume.

License

MIT


Cody — https://agentcody.ai

Available Tools

3 tools
ask_codyA

Ask Cody a question about the product - pricing, setup, integrations, MCP support or data handling. Returns an answer plus the source URLs it was drawn from.

Inputs: question (required).

list_integrationsA

List the tools Cody connects to, optionally filtered by category or name. Returns integration ids, categories and documentation links on agentcody.ai.

Inputs: search, category.

search_team_knowledgeB

Search Cody's team knowledge base for articles about setup, integrations, support automation and MCP. Returns ranked articles with titles, summaries and canonical URLs on agentcody.ai.

Inputs: query (required), limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation3/5

    ask_cody and search_team_knowledge both retrieve information about Cody, so an agent could confuse them for question-answering tasks. list_integrations is clearly distinct, but the overlap between the other two creates some ambiguity.

    Naming Consistency5/5

    All tools use snake_case with a verb_noun pattern (search_team_knowledge, list_integrations, ask_cody). The style is consistent and predictable.

    Tool Count5/5

    Three tools is well within the ideal range and each targets a distinct retrieval need: knowledge search, integration listing, and Q&A. No unnecessary tools.

    Completeness4/5

    The surface covers the core informational needs (search, list, ask), but lacks a dedicated tool to fetch full article or integration details. Agents can work around by following canonical URLs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search and read offline documentation from synced libraries via MCP tools, providing hybrid keyword and semantic search without network calls.
      12 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides LLM-free search tools across Confluence, JIRA, code, and project knowledge for any MCP client.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables hybrid search over product PDFs with version-aware, figure-returning answers for any MCP client, locally or via secure remote access.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP clients such as Claude, ChatGPT, Cursor and VS Code to a product's published help pages, product map, release timeline and past support conversations, letting users search, read, ask questions with cited answers, and run code-backed investigations. It also offers a sign-in-free server per public help center for visitor-style help search and team contact.
      MIT