A
licenseNot graded
qualityB
maintenanceAn MCP server that exposes an AI project portfolio as queryable tools, allowing users to ask about projects, search by technology, or get details via natural language.
1
MIT
toad-mcp-server
by vola-trebla
Related Servers
Alternatives to toad-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server providing RAG context and failure capture for Claude Code, enabling semantic search across project knowledge and storing/analyzing failures.1MIT
- FlicenseAqualityCmaintenanceMCP server exposing AI trends, daily digests, toolbox search, and pipeline stats from cantkeepupwithai.com to MCP clients like Claude Desktop.6-
- AlicenseNot gradedqualityDmaintenanceAI-powered MCP server that enables Claude and other LLMs to interact directly with construction documents, drawings, and specifications through advanced RAG and hybrid search capabilities.9MIT
- AlicenseBqualityDmaintenanceEnables AI-driven semantic code search via natural language queries, integrating with MCP clients like Claude Desktop to retrieve relevant code context from any codebase.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server providing weather lookup, semantic search over personal notes (RAG), and image generation tools for any MCP client like Claude Desktop.MIT
TDQS
A4.1/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a distinct capability: semantic search, eval execution, system health, prompt listing, and prompt detail retrieval. The relationship between list_prompts and get_prompt is complementary rather than ambiguous.
Naming Consistency5/5
All tools follow the same `toad_` prefix with a clear verb_noun pattern: search_documents, run_eval, system_status, list_prompts, get_prompt. This makes the toolset highly predictable.
Tool Count5/5
Five tools is well-scoped for a specialized server covering search, evaluation, system health, and prompt registry access. Each tool earns its place without redundant or unnecessary entries.
Completeness3/5
The server supports read/search/run workflows, but lacks prompt registry write operations (create/update/delete) and any way to list available eval suites. Agents may encounter dead ends when trying to discover eval inputs or manage prompt lifecycle.