An API key inherits the issuing user's rights, so an agent cannot reach a space that person could not open — and on top of that, each method can be set to auto-apply, require approval, or be denied outright. Writes propagate as live events, which means a human watching the page sees the agent's edit as it lands rather than after a refresh.
A collaborative documentation and project workspace that exposes its own operations over MCP at /api/mcp-standard. An agent authenticated with an API key gets the same permissions as the user that issued it, and sensitive methods route through an approval gate.
- space_create, space_list, space_update, space_delete — manage spaces
- page_create, page_list, page_update, page_delete, page_move — create and reorganise pages
- comment_create, comment_list, comment_update, comment_delete — work the comment threads on a page
- attachment_upload, attachment_list, attachment_get, attachment_download, attachment_delete — file attachments
- user_list, user_get, user_update — user administration
- group_create, group_list, group_update, group_delete, group_addMember, group_removeMember — groups and membership
- workspace_create, workspace_list, workspace_update, workspace_delete, workspace_addMember, workspace_removeMember — workspace administration
- ui_navigate — move the interface to a specific destination
- An approval gate: a method that needs sign-off returns an APPROVAL_REQUIRED error carrying an approvalToken and its expiry
- Per-method policy configured in workspace settings as auto-apply, require approval, or deny
A running instance of the workspace server. Create an API key with the bundled registration script and send it as a bearer token; the key is tied to a user and workspace and carries exactly that user's permissions. Clients connect over HTTP to the /api/mcp-standard endpoint — no separate bridge process. Changes made through MCP also emit real-time events to connected clients.