MCP Server
What is the MCP server?
The Model Context Protocol (MCP) server exposes Vipr's analysis data to AI assistants like Claude, Codex, Copilot, and Cursor. Instead of pasting metrics manually, your AI tools can query code quality data directly.
Enabling the MCP server
- Open Vipr Desktop settings.
- Navigate to MCP Server.
- Toggle the server on and start it.
- Keep authentication enabled. Vipr creates a random bearer token for new configurations.
- Copy the Claude, Codex, or Cursor config from the same panel and store it in that host's private user configuration.
The server binds only to 127.0.0.1. It fails clearly if the selected port is occupied rather than
silently choosing a port that does not match the generated client config. Copy a fresh config after
changing the port or regenerating the token.
Available tools
The Desktop process exposes up to 21 tools. Workspace and clarification tools appear only when the corresponding Desktop provider is available. Every tool is declared read-only and returns both text and structured JSON content.
| Area | Tools |
|---|---|
| Current analysis | get_file_analysis, search_issues, get_recommendations |
| Health | get_health_summary, get_complexity_trends |
| History | get_file_history, get_metrics_at_commit, compare_commits, find_regression, get_high_churn_files |
| Branches | compare_branches |
| Snapshots | list_snapshots, get_snapshot, compare_snapshots |
| Live workspace | get_workspace_context, investigate_branch_regression, get_evidence_details |
| Analysis reference | vipr_list_analyses, vipr_get_analysis_docs |
| Clarification | clarify_vipr_context |
| Server | ping |
Connecting AI assistants
Use the config generated by Vipr Desktop. The public Vipr agent plugin is deliberately credential-free: it supplies reusable workflows, while the private host configuration supplies the active local endpoint and bearer token. Never commit the generated config or paste its token into a chat, issue, or support ticket.