F
licenseA
qualityD
maintenanceAn MCP server that provides access to up-to-date Stimulus JS documentation directly within Claude conversations and VS Code.
16
6
-
Turbo Docs MCP Server
by pinzonjulian
Related Servers
Alternatives to Turbo Docs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that makes project documentation instantly accessible in Claude Code through @ mentions, allowing Claude to understand your codebase's conventions and architecture.5MIT
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that provides up-to-date documentation for enterprise and development tools directly to AI coding assistants like Claude Code and Cursor.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables Claude to generate, search, and manage documentation for codebases using vector embeddings and semantic search, providing tools for creating user guides, technical documentation, code explanations, and architectural diagrams.6-
- AlicenseAqualityDmaintenanceAn MCP server that lets Claude Code recall the context of past conversations from any project on demand.5305 npm2MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that integrates with Claude to provide smart documentation search capabilities across multiple AI/ML libraries, allowing users to retrieve and process technical information through natural language queries.-
TDQS
A3.5/5.0
Scored across 13 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with no overlap. The 'handbook-' tools cover conceptual topics and tutorials, while the 'reference-' tools provide API documentation, making it impossible to confuse them. Each tool name directly indicates its specific scope within the Turbo framework.
Naming Consistency5/5
The naming follows a perfect and predictable pattern throughout. All tools use a consistent 'prefix-topic' format with kebab-case, where 'handbook-' indicates conceptual guides and 'reference-' indicates API documentation. This consistency makes the tool set highly readable and predictable.
Tool Count5/5
With 13 tools, the count is well-scoped and appropriate for the server's purpose of documenting Turbo. It covers all major aspects (Drive, Frames, Streams, Native, installation, attributes, events) without being overwhelming, and each tool earns its place by addressing a distinct area of the framework.
Completeness5/5
The tool set provides complete coverage of the Turbo documentation domain. It includes all core concepts (introduction, building, installing, Drive, Frames, Streams, Native, page refreshes) and comprehensive API references (attributes, Drive, events, Frames, Streams), leaving no gaps for agents to navigate the framework effectively.
Maintenance
ActivityInactive
ResponsivenessNo issues