Outline MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTLINE_API_KEY | Yes | Your Outline API token generated from Settings -> API Tokens | |
| OUTLINE_BASE_URL | Yes | The URL of your Outline instance (e.g., https://app.getoutline.com) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| outline_get_documentB | Get a specific document from Outline by ID |
| outline_search_documentsC | Search for documents in Outline |
| outline_list_documentsB | List documents from Outline, optionally filtered by collection |
| outline_create_documentC | Create a new document in Outline |
| outline_update_documentC | Update an existing document in Outline |
| outline_delete_documentC | Delete a document from Outline |
| outline_list_collectionsB | List all collections in Outline |
| outline_get_collectionC | Get information about a specific collection |
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 8 tools
Every tool has a clearly distinct purpose with no ambiguity: create, delete, get, list, search, and update operations target specific resources (documents or collections). The descriptions clearly differentiate each tool's function, making misselection unlikely.
All tool names follow a consistent 'outline_verb_noun' pattern with snake_case throughout. The verbs (create, delete, get, list, search, update) are consistently applied to nouns (document, collection), providing a predictable and readable naming convention.
With 8 tools, the server is well-scoped for managing documents and collections in Outline. Each tool earns its place by covering essential CRUD operations, listing, and search functionalities, avoiding both bloat and thin coverage.
The tool set provides complete CRUD/lifecycle coverage for the domain: create, get, update, and delete for documents, plus get and list for collections, along with search and filtered listing. There are no obvious gaps that would cause agent failures in document management workflows.