cody-mcp
Related Servers
Alternatives to cody-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and read offline documentation from synced libraries via MCP tools, providing hybrid keyword and semantic search without network calls.2 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables hybrid search over product PDFs with version-aware, figure-returning answers for any MCP client, locally or via secure remote access.MIT
- AlicenseNot gradedqualityDmaintenanceProvides LLM-free search tools across Confluence, JIRA, code, and project knowledge for any MCP client.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to search a unified organizational knowledge warehouse, create and iterate on documents, manage folders and reviews, and curate shareable knowledge packs through any compatible MCP client.-
- FlicenseAqualityCmaintenanceEnables MCP clients to retrieve authoritative AI Square documentation, API references, SDK examples, guides, and troubleshooting information through citation-safe hybrid search and static resources.11-
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to a team's product knowledge base, enabling search, capture, and navigation of glossary terms, business rules, decisions, and relations via MCP.25,173 npmMIT
TDQS
Scored across 3 tools
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.
All tools use snake_case with a verb_noun pattern (search_team_knowledge, list_integrations, ask_cody). The style is consistent and predictable.
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.
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.