revibe-mcp
Related Servers
Alternatives to revibe-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables natural-language analysis of GitHub repositories by exposing repository metadata, source code retrieval, search, and file reading as MCP tools, with answers grounded in the actual repository content.-
- AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with structured intelligence about any GitHub repository including overview, PRs, contributors, hot files, CI status, and dependencies via a hosted MCP endpoint.86 npmMIT
- FlicenseNot gradedqualityAmaintenanceAnalyzes repositories, explains architecture, calculates change impact, and enforces guardrails for AI Agents like Claude Code, Cursor, and Codex via MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered GitHub interactions including repository analysis, code search, PR reviews, and more through the MCP protocol.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to analyze any public GitHub repository through typed, focused tools that surface metadata, README content, file structure, detected tech stack, and Mermaid architecture diagrams. It lets users explore repo purpose, structure, and dependencies via natural language without manual browsing.MIT
- FlicenseNot gradedqualityCmaintenanceEnables large language models to explore, inspect, and analyze GitHub repositories through natural-language queries, using MCP tools to retrieve repository data, file structures, file contents, and code search results from the GitHub REST API.-
TDQS
Scored across 6 tools
Each tool has a distinct role: login for authentication, analyze_repo for submission, check_status for job monitoring, and three retrieval tools with clear separation of scope. get_summary, get_section, and get_agent_context serve different granularities of output, preventing confusion.
Most tools follow a clear verb_noun pattern (analyze_repo, check_status, get_summary, get_section, get_agent_context). The exception is revibe_login, which places a brand prefix before a verb and does not match the conventional verb-first structure, creating a minor inconsistency.
With 6 tools, the server is well-scoped for its purpose: authentication, analysis submission, status polling, and result retrieval. This is an appropriate size that covers the workflow without redundancy or unnecessary bloat.
The tool set covers the complete lifecycle of a Revibe analysis: login, submit repository, check progress, and retrieve results in multiple formats (summary, sections, and full agent context). No critical steps are missing for the intended use case, and the output options are sufficient for both human and agent consumption.