MCP access

AuroraDocs can expose a scoped workspace API to external agents through the AuroraDocs MCP server package.

What MCP Is For

Use MCP access when you want an external AI agent or automation client to work with AuroraDocs content using explicit tools instead of scraping the app UI.

Current tool coverage includes:

• search, list, recent, and read objects
• create and update objects
• append blocks
• task helpers
• property helpers
• workspace members
• task-list and task-status discovery
• wiki-style knowledge lookup tools when the workspace knowledge layer is available

Requirements

MCP access is AuroraCloud-scoped:

• you must be signed in
• the workspace must be AuroraCloud-backed
• the token must have the required scopes
• normal workspace membership and role checks still apply

Browser-only and Local folders workspaces are outside the MCP scope unless they are first promoted to AuroraCloud.

Encrypted Workspaces

For E2EE workspaces, MCP cannot decrypt locked content. Tools should return locked or unavailable states rather than ciphertext. Treat encrypted content as unavailable to external agents unless Aurora explicitly provides a safe unlocked path.

Managing Access

Workspace owners can manage MCP access in Settings → Workspace → MCP Access. Keep tokens narrow, rotate them when a client is retired, and avoid sharing tokens between unrelated tools.

Privacy Notes

External MCP clients are separate software. Only grant tokens to clients you trust, and review what those clients store in their own logs or histories.