nizovtsevnv/outline-mcp-rs
If you are the rightful owner of outline-mcp-rs and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
The MCP Server is designed for seamless interaction with the Outline API, prioritizing simplicity, performance, and reliability.
Outline MCP Server
MCP (Model Context Protocol) server for Outline API interaction with focus on simplicity, performance, and reliability.
π Quick Start
1. Get Your Outline API Key
- Outline.com: https://app.outline.com/settings/api-and-apps
- Self-hosted: https://your-instance.com/settings/api-and-apps
2. Download & Install
Choose one of the installation methods:
π Option 1: Download pre-built binary (Recommended)
Download from GitHub Releases
After extracting:
- Linux/macOS: If needed, make executable:
chmod +x outline-mcp
- Windows: Since the release is not code-signed, π‘οΈ Windows Defender may block execution. You'll need to:
- Allow the executable through Windows Defender/antivirus
- Add the folder to Windows Defender exclusions, or
- Right-click the file β Properties β "Unblock" if downloaded from internet
π¦ Option 2: Install from crates.io
cargo install outline-mcp-rs
Requires Rust toolchain. The binary will be installed to ~/.cargo/bin/outline-mcp
π¨ Option 3: Build from source
git clone https://github.com/nizovtsevnv/outline-mcp-rs.git
cd outline-mcp-rs
cargo build --release
# Binary will be in target/release/outline-mcp
βοΈ Option 4: Nix (with reproducible environment)
nix run github:nizovtsevnv/outline-mcp-rs
3. Configure your AI agent
JSON configuration for Cursor IDE, Gemini CLI:
{
"mcpServers": {
"Outline knowledge base": {
"command": "outline-mcp",
"env": {
"OUTLINE_API_KEY": "your-api-key-here",
"OUTLINE_API_URL": "https://app.getoutline.com/api"
}
}
}
}
π‘ Path Notes:
- cargo install: Use
"outline-mcp"
(added to PATH automatically)- Downloaded binary: Use full path like
"/path/to/outline-mcp"
- Built from source: Use
"/path/to/outline-mcp-rs/target/release/outline-mcp"
β οΈ Important Path Requirements:
- Use absolute paths - relative paths may not work correctly
- No spaces in the executable file path (use underscores or hyphens instead)
- ASCII characters only - avoid non-Latin characters in paths
- Windows users: Use double backslashes
\\
in paths (e.g.,"C:\\tools\\outline-mcp.exe"
)
β Good examples:
- Linux/macOS:
"/usr/local/bin/outline-mcp"
or"/home/user/bin/outline-mcp"
- Windows:
"C:\\tools\\outline-mcp.exe"
or"C:\\Users\\YourName\\bin\\outline-mcp.exe"
β Avoid:
"./outline-mcp"
(relative path)"/path with spaces/outline-mcp"
(spaces in path)"/ΠΏΡΡΡ/outline-mcp"
(non-Latin characters)"C:\tools\outline-mcp.exe"
(single backslash on Windows)
π οΈ Supported Tools
Complete coverage of Outline API functionality:
π Document Operations
create_document
- Create new documentget_document
- Retrieve document by IDupdate_document
- Update existing documentdelete_document
- Delete documentlist_documents
- List documents with filteringsearch_documents
- Search documents by queryarchive_document
- Archive documentmove_document
- Move document between collections
π Collection Management
create_collection
- Create new collectionget_collection
- Retrieve collection detailsupdate_collection
- Update collection metadatalist_collections
- List all collections
π¬ Comments & Collaboration
create_comment
- Add comment to documentupdate_comment
- Modify existing commentdelete_comment
- Remove comment
π Advanced Features
create_template_from_document
- Create reusable templateslist_users
- User management
π― Project Principles
β‘ Performance
- Static builds with musl/glibc - single file without dependencies
- < 5MB binary with full functionality
- < 10ms startup time to ready state
- < 10MB memory usage
π‘οΈ Reliability
- Zero dependencies at runtime (static linking)
- Explicit error handling - no panics in production
- Type safety - leveraging Rust's ownership system
- Comprehensive testing - unit and integration tests
π§ Simplicity
- Minimal code - only essential functionality
- Clear architecture - easy to understand and modify
- Single binary - simple deployment
- Environment configuration - no config files
π Development Requirements
- Nix (recommended) - handles all dependencies automatically
- OR manually: Rust 1.75+, OpenSSL development libraries
ποΈ Architecture
βββββββββββββββββββ ββββββββββββββββββββ βββββββββββββββββββ
β MCP Client ββββββ Transport Layer ββββββ Outline API β
β (Claude/etc) β β (STDIO/HTTP) β β (REST/JSON) β
βββββββββββββββββββ ββββββββββββββββββββ βββββββββββββββββββ
Core Components
- Transport Layer: STDIO and HTTP adapters
- MCP Protocol: JSON-RPC 2.0 implementation
- Outline Client: HTTP API wrapper
- Tools Registry: Dynamic tool discovery and execution
Quick Build Commands:
# Linux/Unix systems
nix build # Linux native
nix build .#musl # Linux static (portable)
nix build .#windows # Windows cross-compile
# macOS systems (requires Nix on macOS)
nix build # Auto-detects Intel/ARM
nix build .#macos-x86_64 # Intel target
nix build .#macos-arm64 # ARM target
macOS Development Setup:
# Install Nix on macOS
curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install
# Enable flakes
echo "experimental-features = nix-command flakes" >> ~/.config/nix/nix.conf
# Clone and build
git clone https://github.com/nizovtsevnv/outline-mcp-rs
cd outline-mcp-rs
nix build
π For detailed macOS development instructions, see
π For Windows code signing setup, see
π§ͺ Testing
# Run all tests
nix develop -c cargo test
# Run with coverage
nix develop -c cargo test --coverage
# Integration tests with live API (set OUTLINE_API_KEY)
nix develop -c cargo test --test integration
π§ Configuration
STDIO Mode (Default)
export OUTLINE_API_KEY="your-key-here"
./outline-mcp
HTTP Mode
export OUTLINE_API_KEY="your-key-here"
export HTTP_HOST="0.0.0.0"
export HTTP_PORT="8080"
./outline-mcp --http
π§ Optimized Nix Configuration
Our flake.nix
has been carefully optimized to eliminate duplication and improve maintainability:
ποΈ Architecture Improvements
- π¦ Metadata Sync: Package information references
Cargo.toml
values with comments - π Reusable Shell Builder:
mkDevShell
function eliminates code duplication - π― Consistent Shell Hooks: Unified
mkShellHook
function for all environments - β‘ Base Build Inputs: Shared dependencies across all development shells
- π§ͺ Automated Checks: Built-in formatting, linting, and testing workflows
π Available Commands
# Development environments
nix develop # Native development with tools
nix develop .#musl # musl static build environment
nix develop .#windows # Windows cross-compilation
nix develop .#macos # macOS development (Darwin only)
# Package building
nix build # Native build (Linux/macOS auto-detect)
nix build .#musl # Static musl build (portable Linux)
nix build .#glibc-optimized # Optimized glibc build (static OpenSSL, dynamic glibc)
nix build .#windows # Windows cross-compilation
nix build .#macos-x86_64 # macOS Intel (requires macOS or CI)
nix build .#macos-arm64 # macOS Apple Silicon (requires macOS or CI)
# Alternative: Use dev environment for building
nix develop -c cargo build --release # Native
nix develop .#musl -c cargo build --target x86_64-unknown-linux-musl --release # musl
nix develop .#windows -c cargo build --target x86_64-pc-windows-gnu --release # Windows
# macOS targets (macOS only)
nix develop -c cargo build --target x86_64-apple-darwin --release # Intel Mac
nix develop -c cargo build --target aarch64-apple-darwin --release # Apple Silicon
π€ Contributing
- Fork the repository
- Create feature branch (
git checkout -b feature/amazing-feature
) - Make changes with tests
- Ensure all checks pass:
cargo test && cargo clippy
- Submit pull request
Development Workflow
# Setup development environment
nix develop
# Code formatting
cargo fmt
# Linting
cargo clippy
# Testing
cargo test
# Cross-platform testing
nix develop .#musl --command cargo test --target x86_64-unknown-linux-musl
nix develop .#windows --command cargo check --target x86_64-pc-windows-gnu
π License
MIT License - see file for details.
π Acknowledgments
- Outline team for excellent API documentation
- Anthropic for MCP protocol specification
- Rust community for outstanding tooling and libraries