context7-mcp
Related Servers
Alternatives to context7-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA Model Context Protocol server that fetches up-to-date, version-specific documentation and code examples from libraries directly into LLM prompts, helping developers get accurate answers without outdated or hallucinated information.2354,384 npm62,380MIT
- AlicenseNot gradedqualityDmaintenanceContext9 is an MCP server that feeds AI agents with up-to-date documentation, reducing hallucinations by real-time knowledge synchronization.31Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceProvides real-time access to code library documentation and examples through Context7 API integration, enabling AI assistants to retrieve up-to-date technical documentation, code snippets, and best practices for various programming libraries.1MIT
- AlicenseAqualityCmaintenanceDevsContext is an MCP server that provides AI coding agents with synthesized engineering context—requirements, decisions, architecture, and standards—from tools like Jira and Slack. It fetches and synthesizes relevant information on demand to help agents work on tasks correctly.41MIT

Mintlify Indexofficial
AlicenseNot gradedqualityCmaintenanceProvides real-time documentation retrieval for coding agents, answering implementation questions with compact, cited context assembled from developer documentation and live web search via a single MCP context tool.49MIT- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol (MCP) server that implements AI-First Development framework principles, allowing LLMs to interact with context-first documentation tools and workflows for preserving knowledge and intent alongside code.336AGPL 3.0
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'resolve-library-id' handles library identification and matching, while 'get-library-docs' retrieves documentation for a specific library. There is no overlap in functionality, and the descriptions explicitly define their separate roles in the workflow.
Both tools follow a consistent verb-object naming pattern with hyphens ('resolve-library-id', 'get-library-docs'), which is clear and readable. The minor deviation is that 'resolve' and 'get' are different verbs, but this reflects their distinct actions appropriately within the domain.
With only 2 tools, the server feels thin for its apparent domain of library documentation retrieval. A more complete surface might include tools for browsing libraries, searching documentation, or managing queries, but the current set is minimal and may limit agent capabilities.
The tool surface is severely incomplete for library documentation workflows. While it covers resolution and fetching, it lacks tools for operations like searching across libraries, listing available libraries, or handling documentation updates, which are common needs in this domain.