Skip to main content
Glama
mcp-outline

mcp-outline

by ytrafimovich

mcp-outline

An MCP server that connects Claude Code to your Outline knowledge base, giving Claude tools to search and retrieve documents.

Tools

  • outline_search — full-text search across your Outline workspace

  • outline_get_document — fetch a document's full content by ID

Related MCP server: Outline Wiki MCP Server

Prerequisites

  • Node.js 18+

  • An Outline API key — go to Preferences → API & Access → New API key

    Use the scope documents:read to restrict the key to read-only document access:

    New API key dialog showing documents:read scope

Setup

1. Clone and install

git clone https://github.com/YOUR_USERNAME/mcp-outline.git ~/.claude/mcp-outline
cd ~/.claude/mcp-outline
npm install

You can clone it anywhere; ~/.claude/mcp-outline is just a tidy location that keeps it with your Claude config.

2. Register the MCP server globally

Run this once from your terminal to add the server to your user-level Claude Code config (available in every project):

claude mcp add -s user outline \
  npx tsx /Users/YOUR_USERNAME/.claude/mcp-outline/src/server.ts \
  --env OUTLINE_API_KEY=YOUR_OUTLINE_API_KEY \
  --env OUTLINE_BASE_URL=https://app.getoutline.com

Replace:

  • /Users/YOUR_USERNAME/.claude/mcp-outline with the actual absolute path where you cloned the repo

  • YOUR_OUTLINE_API_KEY with your Outline API key

  • Omit --env OUTLINE_BASE_URL=... if you use the default https://app.getoutline.com

The -s user flag registers the server at the user scope, so it is available globally in every Claude Code session without needing per-project configuration.

3. Verify

claude mcp list

outline should appear in the list of active MCP servers.

Usage

Once configured, Claude Code can use the Outline tools automatically when you ask questions about your docs:

"Search our Outline for the onboarding guide"

"Get the Outline document with ID abc-123"

License

ISC

Available Tools

2 tools
outline_get_documentC

Get an Outline document by ID

Inputs: id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves a document by ID, and the other performs a search. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow the pattern 'outline_<verb>[_<noun>]' with consistent snake_case and a common prefix, making them predictable.

    Tool Count3/5

    With only 2 tools, the surface is thin for a documentation server. While it covers basic retrieval and search, it lacks other expected operations, making it borderline.

    Completeness3/5

    The server provides get and search capabilities but is missing create, update, delete, and list operations. This represents notable gaps for typical document management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers