Connecting your IDE

The hosted MCP endpoint has two shapes. One repo:

https://api.repowise.dev/mcp/{owner}/{repo}

The {owner}/{repo} segments are required. They are the GitHub owner/name of a repo you've already indexed. Every editor that supports MCP can talk to that URL once you've minted an API key.

One workspace, answering across its member repos:

https://api.repowise.dev/mcp/w/{workspace_id}

Both take the same account-scoped key, so there is nothing extra to mint for the workspace shape. See across a whole workspace below for what changes.

Mint an API key#

1. Sign in at repowise.dev.
2. Open Settings → Editor.
3. Click Generate key and name it after the editor you'll use it from.
4. Pick the repo you're connecting, then copy the snippet for your editor.

Keys are revocable any time.

Snippets#

Replace OWNER/REPO with the repo you're connecting and YOUR_API_KEY with the key you just minted. The same snippets are generated for you, pre-filled, on Settings → Editor.

claude mcp add --transport http repowise https://api.repowise.dev/mcp/OWNER/REPO \
  --header "Authorization: Bearer YOUR_API_KEY"

{
  "mcpServers": {
    "repowise": {
      "url": "https://api.repowise.dev/mcp/OWNER/REPO",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

{
  "servers": {
    "repowise": {
      "type": "http",
      "url": "https://api.repowise.dev/mcp/OWNER/REPO",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "repowise": {
      "serverUrl": "https://api.repowise.dev/mcp/OWNER/REPO",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Any other MCP client that speaks the Streamable HTTP transport works with the same two values: the URL above and an Authorization: Bearer YOUR_API_KEY header.

Across a whole workspace#

A workspace groups several indexed repos. Pointing a client at the workspace URL gives you one connection that answers across all of them:

https://api.repowise.dev/mcp/w/{workspace_id}

Open the workspace and use its Connect tab, which builds the URL, carries the same editor snippets as above, and lists the aliases below. Everything else about the snippets is identical: swap the URL, keep the Authorization header.

What changes on this shape:

• An extra tool, list_repos. Call it first. It returns each member repo with the alias to address it by.
• Every federatable tool takes an optional repo. Pass an alias to scope the call to one member; omit it, or pass "all", and the tool answers across every member you can read. get_symbol always requires one, because a symbol id only means something inside one repo.
• Read-only. Write tools are refused here by design, so a re-index still goes through the per-repo endpoint even with a write-scoped key.
• Pro, Teams, or Admin. The per-repo endpoint above is not gated this way and stays available on every plan.

An alias comes from the alias you gave the repo when you added it to the workspace. If you left it blank it falls back to the owner and name joined by a hyphen, so acme/billing-api answers to acme-billing-api. The workspace's Connect tab prints the exact tokens.

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.