Outline MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTLINE_API_KEY | Yes | Your Outline API key, created in Outline under Settings → API & Apps → Create API key (format: ol_api_...). | |
| OUTLINE_API_URL | No | The API URL for Outline. Set this for self-hosted Outline instances; defaults to https://app.getoutline.com/api. | https://app.getoutline.com/api |
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_callA | Call any Outline RPC method directly (POST https://app.getoutline.com/api/:method). Use for endpoints without a dedicated tool. Common methods: documents.info, documents.list, documents.search, documents.create, documents.update, documents.delete, documents.move, documents.archive, documents.unpublish, documents.export, collections.list, collections.info, collections.create, collections.update, collections.delete, collections.add_document, comments.list, comments.create, users.list, users.info, users.invite, attachments.create, shares.list, stars.list, pins.list, templates.list, revisions.list, events.list, auth.info. Args: method (string, e.g. "documents.info"), params (object, method-specific payload). Returns: the method's data payload (with pagination when present). |
| outline_searchC | Full-text search across documents. Args: query (string), collectionId (optional), limit, offset. Returns: matching documents. |
| outline_get_documentA | Fetch a document by id, including its Markdown text. Args: id (string). |
| outline_list_documentsC | List documents, optionally within a collection or under a parent. Args: collectionId, parentDocumentId, limit, offset. |
| outline_list_collectionsB | List all collections in the workspace. Args: limit, offset. |
| outline_list_collection_documentsB | List the document tree of a collection. Args: id (collection id), limit, offset. |
| outline_list_usersC | List workspace users, optionally filtered. Args: query (optional), limit, offset. |
| outline_list_commentsC | List comments on a document. Args: documentId (string), limit, offset. |
| outline_create_documentB | Create a document. Args: title (required), text (Markdown, optional), collectionId, parentDocumentId, publish (default false — drafts are only visible to you). Returns: the created document. |
| outline_update_documentB | Update a document's title and/or body. Args: id (required), title (optional), text (optional, replaces the body). Returns: the updated document. |
| outline_delete_documentA | Delete a document. Args: id (required), permanent (default false — moves to trash when false). |
| outline_move_documentC | Move a document to another collection and/or parent. Args: id (required), collectionId, parentDocumentId. |
| outline_create_collectionB | Create a collection. Args: name (required), description (optional Markdown), private (default false), color (optional hex like "#4E5D78"). Returns: the created collection. |
| outline_create_commentC | Add a comment to a document. Args: documentId (required), text (Markdown), parentCommentId (optional, to reply). |
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 14 tools
Most tools target a clear resource+action, but outline_call is a catch-all RPC escape hatch that overlaps with every dedicated tool, and outline_list_documents vs outline_list_collection_documents have subtly different scopes that could cause misselection. Descriptions clarify intent reasonably well.
Nearly all tools follow a consistent outline_verb_noun pattern (create/update/delete/list/get/move). outline_call breaks the verb_noun shape and outline_list_collection_documents is noun-heavy, but the scheme remains readable and predictable.
14 tools sit comfortably in the well-scoped 3-15 range for a document/workspace platform, with each dedicated tool covering a distinct common operation.
Documents get full lifecycle coverage (create/get/update/delete/move/list/search) plus collections, comments, and users. Minor gaps exist (no collection update/delete or comment update/delete as dedicated tools, no archive/unpublish), but outline_call provides a fallback for these.