MCP server

Let AI tools read the project context your team already trusts.

Connect RepoWiki as a read-only MCP server. Your approved clients can search indexed docs, read the right file, and keep source details close.

Start Team Read setup guide

Details

Bring repo docs to the tools you use.

MCP lets your tools use the docs your team already trusts, without creating a second source of truth or giving clients write 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.

scope

Useful context, bounded access

Your clients can search and read indexed docs. 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 named tokens, revocation, recent 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 sends the question to RepoWiki and searches the workspace docs.

See the closest sources

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

Read the file that answers it

The model gets context from the doc your team already maintains in Git.

Keep the workspace in view

Tokens, activity, revocation, usage limits, and read-only scope 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 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, and sync time 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 projects, and stay within the repositories you connected.

Read-only

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

Source-backed

Each result includes repo, branch, path, sync time, and source link.

Metered

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

search_docs

Find the doc your client needs.

read_doc

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

list_projects

Show the projects available in the workspace.

list_repositories

Stay within the repositories your team connected.