| name | outline-mcp-connector |
| description | MCP connector for Outline knowledge base – enables AI-assisted documentation, team collaboration, and knowledge management through Claude |
| license | BSL |
| tags | ["dev","documentation","mcp","outline","wiki"] |
| difficulty | intermediate |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Outline MCP Connector
Overview
This skill enables Claude to interact with Outline through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Outline's REST API, allowing natural language control of Outline operations, intelligent automation, and AI-powered assistance for Outline workflows.
When to Use This Skill
- Document creation and organization in collections
- Template management and content generation
- Search and knowledge retrieval
- Team and permission management
- API integration and webhook configuration
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Outline │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Outline operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/api/documents.create, /api/documents.search, /api/collections.list, /api/teams.info, /api/events.list
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "outline-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Outline resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/api/documents.create`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"outline-mcp-connector": {
"command": "node",
"args": ["path/to/outline-mcp-connector/index.js"],
"env": {
"OUTLINE_API_KEY": "your-api-key",
"OUTLINE_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Outline API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Outline API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a collection for Engineering RFCs with a template including Problem, Proposal, and Alternatives sections"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.