mcp-server-outline
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTLINE_BASE_URL | Yes | The base URL of the Outline instance (e.g., https://your-outline.com) | |
| OUTLINE_API_TOKEN | Yes | Your Outline API token | |
| OUTLINE_ENABLE_WRITES | No | Set to 'true' to enable write operations (optional, default false) |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| outline_search_capabilitiesA | Search the Outline/Playbook MCP capabilities. Use first when deciding which tool to call. |
| outline_whoamiA | Show the user + workspace this Playbook token belongs to. |
| outline_searchA | Ranked full-text search with context snippets. Optional filters: collectionId, statusFilter (draft/published/archived), dateFilter (day/week/month/year), userId. |
| outline_list_documentsA | List documents: recent (default), drafts, archived, or deleted (Trash). Optionally scope to a collection. |
| outline_get_documentA | Fetch one document by id or slug. asMarkdown=true returns the full Markdown body. |
| outline_list_collectionsC | List the collections in the workspace. |
| outline_get_collectionA | Fetch one collection; includeStructure=true adds its document tree. |
| outline_list_commentsC | List comments on a document. |
| outline_list_revisionsC | A document’s version history, or one revision with revisionId. |
| outline_create_documentA | Create a document (Markdown body) in a collection. publish=true makes it visible; parentDocumentId nests it. Requires write access. |
| outline_update_documentA | Update a document title/body. append=true adds text to the end; otherwise text REPLACES the whole body. Requires write access. |
| outline_move_documentA | Move a document to another collection and/or under another parent document. Requires write access. |
| outline_archive_documentA | Archive a document (reversible) or restore an archived/trashed one. Requires write access. |
| outline_delete_documentA | Move a document to Trash (recoverable via restore). Permanent deletion is not available here. Requires write access. |
| outline_create_commentA | Add a comment to a document; parentCommentId replies to a thread. Requires write access. |
| outline_manage_collectionA | Create a new collection or update one (name/description/permission). Deleting collections is not available (cascades permanently). Requires write access. |
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 16 tools
Most tools have clearly distinct purposes (create, update, delete, move, archive documents; manage collections; list comments/revisions; search). However, 'outline_search_capabilities' searches MCP capabilities rather than documents, which could cause confusion with 'outline_search'. Also, 'outline_archive_document' combines archive and restore actions into one tool, slightly blurring the operation.
All tools follow a consistent 'outline_<verb>_<noun>' pattern (e.g., outline_create_document, outline_list_comments). Verbs are descriptive and nouns match the resource. The pattern is uniform across the entire set, making it predictable for an agent.
16 tools is an appropriate number for a document management server. It covers essential operations on documents, collections, comments, revisions, and search without being overwhelming or sparse.
The tool set covers full CRUD for documents (create, read, update, delete/trash, move, archive) and collections (create, update, list, get). It also includes comments, revisions, search, and user info. Minor gaps: no permanent deletion (only trash), no document publishing workflow beyond publish flag, and no user/group management.