jam-nodes-docs-mcp
Related Servers
Alternatives to jam-nodes-docs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides tools for AI agents to search, browse, and retrieve the full documentation for the mcp-framework. It enables agents to access documentation sections and page content directly within MCP-compatible environments like Claude Code and Cursor.37 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search and retrieve current technical documentation for frameworks such as LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP, Camel AI, and CrewAI through MCP tools over stdio or SSE.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, read, and traverse documentation bundles in Open Knowledge Format via MCP tools.705 npm75MIT
- AlicenseAqualityDmaintenanceProvides access to Agno framework documentation for AI agents, enabling search and retrieval of SDK references, API endpoints, code examples, and integration guides through MCP-compatible tools.73MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and retrieve information from the official Magnolia CMS documentation through a set of MCP tools.MIT
- FlicenseNot gradedqualityAmaintenanceEnables users to search and retrieve up-to-date technical documentation for popular agent frameworks such as LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP, Camel AI, and CrewAI. It does this by performing site-specific web searches and extracting page text through a standardized MCP interface over stdio or SSE.-
TDQS
Scored across 5 tools
Each tool targets a distinct documentation resource: keyword search, individual node details, node listing, API reference, and guides. There is no meaningful overlap in their primary functions.
All tool names follow a consistent verb_noun pattern (search_docs, get_node_info, list_nodes, get_api_reference, get_guide). The naming is predictable and uniform.
With 5 tools, the server is well-scoped for a documentation-focused MCP. Each tool covers a clear aspect of accessing documentation without unnecessary redundancy or bloat.
The tool set covers all major ways users interact with docs: searching, listing available nodes, retrieving node details, accessing API reference, and reading guides. No obvious dead ends or missing operations for the documented scope.