outline-wiki-mcp

A stateless MCP server that turns your self-hosted Outline wiki into your AI team's knowledge base. No server-side credentials: every client sends its own Outline API token in the Authorization header, so AI permissions are exactly that user's wiki permissions — nobody can make their AI read a collection they can't see themselves. Ships 12 workflow tools covering search, read, write and organize — including get_project_context, which pulls a whole project bundle in one call — plus a draft→publish flow and an idempotent ClickUp → Outline migration CLI.

Features

• Per-user permissions, zero shared tokens — the server keeps no credentials; the Outline API token in the request header is the identity.

• 12 tools: search, doc tree, full-doc read, create/update/publish/archive, collections, move, file attachments.

• get_project_context — hand an agent everything about a project (all docs in the collection) in a single call.

• Draft-first publishing — create_doc writes drafts; publish_doc promotes them. AI edits stay reviewable before they land.

• Document metadata headers — docs carry a visible kaynak / durum / son kontrol (source / status / last-checked) blockquote that write tools parse and keep up to date.

• Turkish-aware name matching — collection lookup is case- and locale-correct (İ/i), single substring hits resolve, ambiguous ones refuse to guess.

• DNS-rebinding protection — Host allowlist on the MCP endpoint, configurable via MCP_ALLOWED_HOSTS.

• Migration CLI — ClickUp v3 Docs → Outline (doc = collection, page = document), idempotent via a mapping file, paced against Outline rate limits.

• Small and boring on purpose — one Dockerfile, non-root user, digest-pinned base image, runs as one service in the compose stack.

Related MCP server: requarks-wiki-mcp

Quickstart

cp docker-compose.example.yml docker-compose.yml
cp .env.example .env        # fill in SECRET_KEY, UTILS_SECRET, POSTGRES_PASSWORD, Google OAuth
docker compose up -d --build

The stack exposes nothing to the internet by itself — put a reverse proxy or tunnel in front (see the comments in docker-compose.example.yml).

Then create a personal API token in Outline (profile → Settings → API Keys — never share tokens) and point your MCP client at the server:

{
  "mcpServers": {
    "wiki": {
      "type": "http",
      "url": "https://mcp.example.com/mcp",
      "headers": { "Authorization": "Bearer <your-outline-api-token>" }
    }
  }
}

Add .mcp.json to your project's .gitignore — the token must never reach git.

Tools

ClickUp migration

Idempotent: keeps a mapping file (migrate_mapping.json by default) and resumes where it stopped. Each ClickUp doc becomes a collection, each page a document.

OUTLINE_API_URL=https://wiki.example.com/api OUTLINE_TOKEN=<outline-token> \
  python -m wiki_mcp.migrate \
    --clickup-token <pk_...> \
    [--workspace <clickup-workspace-id>] \
    [--only <substring-filter>] \
    [--mapping migrate_mapping.json]

Development

python3 -m venv .venv
.venv/bin/pip install -e '.[dev]'
.venv/bin/pytest -q

Tests run against an in-process fake Outline client — no live wiki needed.

License

MIT — see LICENSE.