MCP server

Let approved clients read the project context your team already trusts.

Connect RepoWiki as a read-only MCP server. Approved clients can search indexed docs, read the right file, request source packets, check claims and freshness, and keep source details and activity close.

Start Team Read setup guide

Details

Bring repo docs to the tools you use.

MCP lets your tools retrieve the docs your team already trusts, without creating a second source of truth, running RepoWiki model calls, or giving clients open-ended access.

what it is

Your project context, ready to read

You can let supported clients ask the docs your team already keeps in Git, with the source trail still attached through tools, resources, and workflow prompts.

scope

Useful context, bounded access

Your clients can search and read indexed docs inside the projects or repositories you choose. They cannot write docs, sync sources, invite members, or change billing.

trust

Answers keep their source

Every result carries project, repository, branch, path, sync timing, and source links when available, so you can check the answer.

control

Access stays visible

You get scoped tokens, revocation, returned-doc activity, monthly usage visibility, and fair-use limits.

how it works

Ask once. Keep the source.

Ask in the client you use

Your approved MCP client calls a read-only tool and searches the docs in its scope.

See the closest sources

Each result keeps its project, repository, path, branch, and last sync time.

Receive a bounded source packet

The client receives structured source context, coverage, warnings, freshness details, and the same JSON as a text fallback.

Keep the workspace in view

Scoped tokens, returned-doc activity, revocation, usage limits, and read-only access stay visible.

example request

A question finds its source.

You keep one source of truth. RepoWiki searches the docs in your workspace and returns the file with structured content and verification details attached.

your question

"What retry window do our webhooks use?"

search_docs({
  query: "webhook retry",
  limit: 3
})

matching docs

docs/payments/webhooks.md

payments-api

updated 18 min ago

runbooks/retry-policy.mdx

platform

updated yesterday

adr/014-event-delivery.md

core-services

updated Mar 4

source receipt

When an answer matters, you can check the project, repo, branch, path, sync time, and token activity behind it.

Project

Payments

Repository

payments-api

Branch

main

Path

docs/payments/webhooks.md

Freshness

Synced 18 min ago

available tools

Only the tools context needs.

Use MCP for retrieval: find docs, read files, list scopes, request bounded source packets, check claims, inspect freshness, use resources and workflow prompts, and stay inside the credential boundary. RepoWiki does not run model calls through MCP.

Read-only

Your clients can search and read docs, not write, sync, invite, or change billing.

Scoped

Tokens can cover the workspace, selected projects, or selected repositories.

Structured

Responses include structured content and the same JSON as text fallback.

Bounded packets

Context packets include excerpts, coverage, warnings, and next-tool guidance.

Claim checks

Claim verification returns source status, warnings, and safer wording.

Freshness checks

Recent changes show what moved since a meeting or workflow checkpoint.

Audited

Searches, reads, listings, packets, claim checks, freshness checks, resources, and prompts record activity without storing raw packet queries, claims, or freshness queries.

Metered

Named client tokens stay visible, revocable, and within monthly fair-use limits.

search_docs

Find the doc your client needs, with project, repository, and path filters.

read_doc

Read a source file with path, repository, branch, and freshness intact.

list_projects

Show the projects this token can access.

list_repositories

Stay within the repositories this token can access.

list_docs

Page through visible documents before narrowing a search.

search

Use simple read-only search for compatibility clients.

fetch

Read one document id returned by compatibility search.

get_context_packet

Return a bounded source packet with coverage and warnings.

verify_claim_against_docs

Check one proposed claim before a client uses it.

get_recent_context_changes

Return recent source changes for freshness checks.

resources and prompts

More than one-off tool calls.

Clients that support MCP resources and prompts can discover scoped project maps, retrieve bounded document payloads, and guide common account, claim, follow-up, and support workflows while RepoWiki stays read-only.

Project resource

Expose the token-scoped project list as reusable JSON.

Project map

Return a bounded document map for one project.

Document resource

Read one bounded document payload by stable id.

Workflow prompts

Guide account brief, claim check, follow-up, and support workflows.