vibe-code-mcp
Related Servers
Alternatives to vibe-code-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search, score, review, and submit tools from the SkillsIndex directory of 11,000+ AI agent tools.971 npmMIT
- AlicenseAqualityDmaintenanceIndexes installed SKILL.md files and provides deterministic search and recommendation tools to help AI agents select relevant skills without executing them.428 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI editors such as Claude, Cursor, Windsurf, and VS Code to search a library of 909 developer brand logos, list categories, fetch logo metadata, SVGs, and typed React components, and assemble logo clouds through natural-language tool calls.73MIT

KitScout MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to search a large index of MCP servers, Agent Skills and Claude Code plugins by keyword, filter by official, live or free-to-try status, and fetch full details and connect lines for any tool. Results include GitHub stars, categories and a ready-to-paste install command.MIT- AlicenseBqualityBmaintenanceConnects AI coding agents to a library of procedural AI skills, verified code snippets, and executable shell commands. It enables searching, retrieving, saving, and injecting these resources into agent context.776 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to perform high-performance code search and analysis across multiple languages using symbol indexing, regex text search, and structural AST pattern matching. It also provides tools for technology stack detection and dependency analysis with persistent caching for optimized performance.12MIT
TDQS
Scored across 9 tools
Most tools are distinct, but recommend_stack and route_project both provide recommendations based on a description, causing potential overlap. Descriptions help differentiate, but an agent may still be uncertain which to use for a given query.
Most tools follow a verb_noun pattern (get_, list_, recommend_, refresh_, route_, search_), but catalog_status is a noun_noun phrase, breaking the convention. Overall, naming is largely consistent and intuitive.
With 9 tools covering browsing, search, recommendation, status, and refresh, the count is well-scoped for a catalog server. Each tool has a clear role, and the number feels appropriate without being overwhelming or insufficient.
The server provides comprehensive browsing (by domain, section, tool), searching, recommendation, and status. Missing a direct 'list all tools' endpoint, but the combination of search and section browsing covers most discovery needs. Minor gap for read-only catalog.