outline-rbac-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTLINE_URL | Yes | The URL of the Outline instance (e.g., https://outline.example.com). | |
| OUTLINE_API_KEY | Yes | Your personal Outline API key. |
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 |
|---|---|
| whoamiA | [requires: account.view_self] Show the authenticated user, their role, and effective capabilities resolved from the role graph. |
| access_graphA | [requires: account.view_self] Render the role inheritance graph and where the current user sits in it. |
| update_my_accountA | [requires: account.update_self] Update your own profile (name and/or avatar URL). |
| list_usersC | [requires: users.list] List workspace users. |
| invite_userA | [requires: users.invite] Invite a user to the workspace with a given role. |
| remove_userA | [requires: users.remove] Permanently remove a user from the workspace. |
| suspend_userA | [requires: users.suspend] Suspend a user (blocks sign-in, keeps their data). |
| activate_userA | [requires: users.activate] Re-activate a previously suspended user. |
| change_user_roleB | [requires: users.change_role] Change another user's workspace role. |
| search_docsA | [requires: docs.search] Full-text search across documents you can access. |
| read_docA | [requires: docs.read] Read a document by ID. |
| create_docC | [requires: docs.create] Create a document in a collection. |
| update_docA | [requires: docs.update] Update a document's title and/or text. |
| delete_docA | [requires: docs.delete] Delete a document. |
| audit_logA | [requires: audit.read] Read the workflow audit trail: every tool call, who made it, and at which stage it succeeded or was denied. |
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 15 tools
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.
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.
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.
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.