Docs / MCP

Connect RepoWiki through MCP.

RepoWiki can expose a Team workspace as a read-only MCP server, so supported clients can search and read indexed repo docs with source details attached.

Start Team Back to docs

Details

Connect the client you already use.

MCP is for connecting external clients to RepoWiki context. RepoWiki does not run model calls for this beta, and every credential keeps its own access boundary.

01 / enable

Enable connector access

Open the MCP server page in a Team workspace and enable the server. Technical clients can use named tokens; hosted connector clients can use OAuth when they cannot send static headers.

02 / connect

Paste the endpoint into the client

Use the workspace endpoint with a bearer token in a technical MCP client, or let a hosted client complete OAuth against the advertised metadata.

03 / tools

Use source-backed tools and prompts

Clients can call RepoWiki-specific tools, document discovery, bounded source packets, claim checks, freshness checks, resources, prompts, or simple search/fetch compatibility tools. Responses include structured content and a matching JSON text fallback.

04 / limits

Watch usage from RepoWiki

The MCP page shows monthly usage, returned-doc activity, token status, token scope, and the monthly reset date.

client configuration

Use the workspace endpoint with the right credential.

Create a named token for technical clients that support bearer headers, or use OAuth for hosted connectors that need an authorization flow. Use search_docs and read_doc for RepoWiki-specific filters and metadata, list_docs for document discovery, get_context_packet for bounded source packets, verify_claim_against_docs for source checks, get_recent_context_changes for freshness checks, or search and fetch for simple compatibility clients. Clients that support MCP resources and prompts can also read scoped project maps or use workflow prompts for account briefs, claim checks, follow-ups, and support response context.

{
  "mcpServers": {
    "repowiki": {
      "type": "http",
      "url": "https://repowiki.dev/api/mcp/w/<workspace-id>",
      "headers": {
        "Authorization": "Bearer <your token>"
      }
    }
  }
}

search_docs

Filtered RepoWiki search with source metadata.

read_doc

Read one indexed document by id or source path.

list_projects

List project scopes visible to the token.

list_repositories

List repository scopes visible to the token.

list_docs

Paginated document discovery inside token scope.

Simple read-only compatibility search.

fetch

Simple read-only compatibility document read.

get_context_packet

Bounded source packet with coverage and warnings.

verify_claim_against_docs

Check one proposed claim against indexed docs.

get_recent_context_changes

Changed source receipts since a timestamp.

Structured responses

Every tool returns structuredContent.

Text fallback

The same JSON is included as text for older clients.

Resources

Project maps and document payloads stay scoped and bounded.

Prompts

Host-model guidance only; RepoWiki stays read-only.

Read-only

Tools can search, read, and list, not write or sync.

Scoped access

Bearer tokens can narrow scope; OAuth checks workspace membership.

Project resource

Scoped project list as JSON.

Project map

Bounded document map for one project.

Document resource

One bounded document payload by id.

Workflow prompts

Account brief, claim check, follow-up, support context.

Requests

5,000 / month

Search calls

500 / month

Document reads

2,000 / month

Data returned

250 MB / month