outline-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH_TOKEN | No | Shared secret for gateway auth mode | |
| OUTLINE_API_URL | No | The API URL of your Outline instance (e.g., https://your-outline.example.com/api) | |
| MCP_ALLOWED_HOSTS | No | Public host(s) for hosted deployment (e.g., outline-mcp.example.com) | |
| OUTLINE_API_TOKEN | No | Your Outline API token (looks like 'ol_api_...') | |
| OUTLINE_MCP_READONLY | No | Set to 'true' to disable all write tools (default not set) | |
| MCP_ALLOW_UNAUTHENTICATED | No | Set to 'true' to allow open (unauthenticated) access | |
| MCP_ALLOW_OUTLINE_TOKEN_AUTH | No | Set to 'true' to enable passthrough auth (clients send their own Outline tokens) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentsC | Full-text search documents by keyword. Returns ranked snippets with their documents. |
| get_documentB | Fetch a single document (including its markdown text) by UUID, urlId, or share id. |
| list_documentsC | List documents, optionally scoped to a collection, parent, or author. |
| list_collectionsC | List collections, optionally filtered by name or status. |
| list_commentsB | List comments, optionally scoped to a document or collection. |
| whoamiA | Return the authenticated user and team for the current token. |
| create_documentC | Create a document. Publishing requires a collection or parent document to live in. |
| update_documentC | Update a document. |
| create_commentB | Add a comment to a document. Provide markdown |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool clearly targets a distinct resource and action: document CRUD, comments, collections, search, and user info. No overlap in purpose.
All tools follow a consistent verb_noun pattern (e.g., create_document, list_comments), with 'whoami' as a minor but acceptable exception.
9 tools cover the core operations for a knowledge base server (documents, comments, collections, search, auth) without being excessive or insufficient.
Missing key lifecycle operations: no delete for documents or comments, no collection creation/update/deletion. Notable gaps that could cause agent failures.