Repowise (Hosted)
Attach Claude or Cursor to repowise.dev–indexed repos over HTTP so agents get codebase intelligence without running repowise init on every machine.
Overview
Repowise (Hosted) is a MCP server for the Build phase that delivers repowise.dev–indexed codebase intelligence to agents over streamable-http with an API key.
What is this MCP server?
- Remote streamable-http MCP at https://api.repowise.dev/mcp/{owner}/{repo} (registry version 0.17.1).
- Bearer Authorization with rw_live_… API keys; read scope is sufficient per registry headers.
- No local repowise init on the client—repository must already be indexed on repowise.dev.
- Owner and repo path variables map directly to GitHub org/user and repository name.
- Same intelligence themes as local Repowise: graph, history, docs, decisions, code health—delivered hosted.
- Registry version 0.17.1 for Repowise (Hosted)
- Remote URL template: api.repowise.dev/mcp/{owner}/{repo}
- Authorization header: Bearer rw_live_… API key (read scope sufficient)
What problem does it solve?
Re-indexing every laptop and CI sandbox wastes time when the team already centralized repo understanding on repowise.dev.
Who is it for?
Builders with repos indexed on repowise.dev who want quick MCP setup on new machines or shared agent configs.
Skip if: Air-gapped workflows, repos never uploaded to repowise.dev, or teams that cannot store API bearer tokens in MCP config.
What do I get? / Deliverables
After adding the remote MCP URL and Bearer key, agents query hosted graph, history, docs, and health for owner/repo without local init.
- HTTP MCP session to hosted codebase intelligence for one indexed repo
- Agent queries without per-machine repowise init
- Repeatable owner/repo URL pattern for team configs
Recommended MCP Servers
Journey fit
Build is the primary shelf because you connect external repo intelligence into the agent workflow while implementing across environments. integrations matches streamable-http remotes, owner/repo URL variables, and Bearer API keys from the repowise.dev dashboard.
How it compares
Hosted streamable-http MCP—not the local PyPI stdio server that requires repowise init on disk.
Common Questions / FAQ
Who is dev.repowise/repowise-hosted for?
Solo builders and small teams whose repos are indexed on repowise.dev and who want HTTP MCP access from Claude Code, Cursor, or similar clients.
When should I use dev.repowise/repowise-hosted?
Use it when local indexing is undesirable but the target GitHub owner/repo is already on repowise.dev and you need agent context during build or review.
How do I add dev.repowise/repowise-hosted to my agent?
Create a read-scoped API key on repowise.dev, then register remote MCP https://api.repowise.dev/mcp/{owner}/{repo} with Authorization: Bearer rw_live_….