A
licenseA
qualityD
maintenanceAn MCP server that enables reading, writing, and searching documents in Outline via its API. It supports document management, full-text search, and collection organization using Markdown formatting.
8
11 npm
17
MIT
outline-rbac-mcp
Related Servers
Alternatives to outline-rbac-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that turns a self-hosted Outline wiki into an AI team's knowledge base, providing tools for search, read, write, and organization with per-user permissions via client-supplied API tokens.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Outline that gives Claude the ability to search and read documents from your Outline instance.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Outline knowledge base implemented on Rust as one statically linked executable file for Linux/MacOS/Windows.7MIT
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude Desktop, Claude Code, and Cursor to search, read, create, update, organize, and archive documents in an Outline wiki, including collections and document trees. It runs locally over stdio with API-token authentication and can optionally allow reversible deletions.90MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that provides secure access to a serverless Markdown wiki on AWS, enabling AI assistants to read, search, and edit pages with space-level permission checks and Bedrock-powered semantic search.MIT
TDQS
A3.7/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct action and resource: user administration (change role, list, invite, remove, suspend, activate), document operations (search, read, create, update, delete), account self-service (whoami, update_my_account), RBAC visualization (access_graph), and auditing (audit_log). No two tools appear to overlap in purpose.
Naming Consistency4/5
The majority of tools follow a clear verb_noun pattern (e.g., list_users, create_doc, suspend_user). However, 'whoami' and 'access_graph' are noun-only exceptions, and 'search_docs' uses a plural noun while document tools like 'read_doc' and 'update_doc' use singular, introducing minor inconsistency.
Tool Count5/5
With 15 tools, the server is at the upper edge of the well-scoped range but each tool covers a distinct and necessary operation within the domains of document management, user administration, RBAC awareness, and auditing. No redundant or excessive tools are present, and the count feels proportionate to the server's stated purpose.
Completeness5/5
The tool surface provides comprehensive coverage: full CRUD for documents, full lifecycle for users (invite, suspend, activate, remove, change role), self-service account operations, RBAC introspection, and an audit trail. There are no obvious missing operations that would prevent an agent from accomplishing common tasks in this domain.
Maintenance
ActivitySlowing
ResponsivenessNo issues