Connecting your IDE

The hosted MCP endpoint is a single HTTP URL. Every editor that supports MCP can talk to it once you've minted an API key.

Mint an API key

1. Sign in at repowise.dev.
2. Open Settings → Editor.
3. Click Generate key — name it after the editor you'll use it from.
4. Copy the snippet for your editor below.

Keys are scoped per repo or per workspace and revocable any time.

Snippets

{
  "mcpServers": {
    "repowise": {
      "transport": "http",
      "url": "https://mcp.repowise.dev",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Targeting a specific repo or workspace

The hosted server is workspace-aware. Pass repo="<alias>" to any tool to target a specific repo, or repo="all" to federate across your whole workspace. See Workspace MCP mode.

Verify it works

Ask your agent something the model can't possibly know without calling repowise:

What are the current hotspot files in this repo?

The agent should call get_overview (or get_risk) and answer with specific file names, churn percentiles, and owners. If it falls back to greps and reads, the MCP connection isn't established.

Rotate or revoke

Settings → Editor shows every active key. Click Revoke to invalidate. Generate a new one, paste it in, restart your editor.