Revibe MCP Server
MCP (Model Context Protocol) server for Revibe codebase analysis. Works with Claude Desktop, Cursor, Windsurf, and any MCP-compatible client.
Setup
1. Install
pip install revibe-mcp
2. Log in
revibe-mcp-auth login
This opens your browser — sign up or log in, click "Authorize", and you're done. The API key is saved automatically to ~/.config/revibe/credentials.json.
3. Configure your MCP client
Add the server to your MCP client config. No API key needed in the config — it's loaded from saved credentials automatically.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"revibe": {
"command": "revibe-mcp"
}
}
}
Claude Code
Add to your project's .mcp.json:
{
"mcpServers": {
"revibe": {
"command": "revibe-mcp"
}
}
}
Cursor
Go to Settings > MCP Servers > Add, then set command to revibe-mcp.
Windsurf
Add to your Windsurf MCP config:
{
"mcpServers": {
"revibe": {
"command": "revibe-mcp"
}
}
}
Alternatively, you can pass the API key directly via environment variable:
{
"mcpServers": {
"revibe": {
"command": "revibe-mcp",
"env": {
"REVIBE_API_KEY": "rk_live_your_key_here"
}
}
}
}
Tools
| Tool | Description |
|---|---|
revibe_login |
Log in via browser (also works as an MCP tool from inside your AI assistant). |
analyze_repo |
Submit a GitHub repo for analysis. Auto-detects from git remote if no URL given. |
check_status |
Check progress of an analysis job. |
get_summary |
Get a condensed summary — architecture, modules, patterns. |
get_section |
Drill into a specific section (architecture, file_roles, system_design_qa, etc.). |
get_agent_context |
Get the full structured agent context JSON — optimized for AI consumption. |
CLI Commands
revibe-mcp-auth login # Log in via browser
revibe-mcp-auth status # Show current auth status
revibe-mcp-auth logout # Remove saved credentials
Usage
Once configured, just ask your AI assistant:
- "Analyze this repo with Revibe"
- "What's the architecture of github.com/user/repo?"
- "Get the agent context for this codebase"
The tools handle auto-detection, polling, and structured output automatically.
Metadata
Release files for revibe-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| revibe_mcp-0.1.0.tar.gz | 7.8 kB | Without provenance | Details for revibe_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| revibe_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for revibe_mcp-0.1.0-py3-none-any.whl |
Total release size: 15.7 kB
Release files / revibe_mcp-0.1.0.tar.gz
| Download URL | revibe_mcp-0.1.0.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02107b5d631e55e843f6653c9b7e416371e9741ba2aa1c2d0bd347ae6f6eb582
|
|
BLAKE2b-256 checksum How to use checksums |
d044791ee5df65bf71c5e0dfe899d9aa3634a86eafb83945bab09ba8be98dec5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.0
|
Release files / revibe_mcp-0.1.0-py3-none-any.whl
| Download URL | revibe_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
48bcf9f6e546607bc67436fc603f69ccadbbf821f5ec38eb7c11b7bc38bac2fb
|
|
BLAKE2b-256 checksum How to use checksums |
2d76cd3bcd5d4c9a7c25500e27236b31b1af198fd32cedd292103ca5a2024aa0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.0
|
Security for revibe-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.