| FMRS | 55 / 100 · C | 64 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 9 / 20 | 17 / 20 |
|---|
| Maintenance | 11 / 20 | 10 / 20 |
|---|
| Documentation | 14 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 13 / 20 |
|---|
| Best for | - Users of MCP clients such as Claude Desktop, Cursor, and Windsurf who want to operate ONLYOFFICE DocSpace in natural language.
- Teams that need to automate room, document, and permission management inside AI workflows.
- Users who prefer the ONLYOFFICE-hosted remote MCP server with no deployment required.
- Integrations that need flexible request-level authentication and tool selection.
| - Teams and individuals who already manage docs/wikis in Notion and want AI clients (Claude Desktop, Cursor, etc.) to operate on that content directly
- Developers who want to self-host a local MCP server rather than use a remote hosted option
- Automation/agent workflows that need to query or update Notion database records programmatically
|
|---|
| Not for | - Users who do not use ONLYOFFICE DocSpace or do not plan to connect their portal.
- Environments that must run fully offline without any external service.
- Users who only want to manage non-DocSpace document systems (other cloud drives or local file systems).
| - Users who want the standard-OAuth, zero-JSON-config install with active official support — Notion recommends its newer remote Notion MCP server for that
- Users uncomfortable handing a Notion integration token to a locally-run LLM client
- Use cases needing capabilities the integration deliberately excludes, such as deleting databases
- Long-term production deployments that need guaranteed maintenance, given this repo may be sunset
|
|---|
| Required permissions | - The DocSpace instance URL (DOCSPACE_BASE_URL) is required.
- DocSpace credentials are required: API key, Personal Access Token, Basic authentication, or OAuth 2.0.
- Credentials are supplied via environment variables or client configuration.
- Authentication and tool selection can be configured per request using custom HTTP headers at session initialization.
| - A Notion internal integration token (NOTION_TOKEN or the Authorization value in OPENAPI_MCP_HEADERS), scoped by that integration's Capabilities (can be limited to read-only)
- Access limited to the specific pages/databases explicitly connected to the integration, not the whole workspace
- A separate bearer auth token when using the Streamable HTTP transport (--auth-token / AUTH_TOKEN)
- Network access to the Notion API
|
|---|
| Risks and side effects | - A leaked API key or token lets its holder act as you on DocSpace content.
- An AI agent may mistakenly delete or alter files or permissions, especially during batch operations (copy, move, delete, archive rooms).
- The remote MCP server is hosted by ONLYOFFICE; review its Legal Terms and Privacy Policy before use.
- Credentials are stored in plain environment variables inside client config files and may be readable locally.
| - If the integration is granted broad read/write capabilities and connected to many pages, that content is effectively exposed to the LLM, risking data leakage or unintended edits
- Running with --unsafe-disable-auth removes bearer authentication on the HTTP transport, potentially making it reachable via DNS rebinding from pages a user visits — the README says to only use it on an isolated network
- Multi-tenant token passthrough requires careful TLS/gateway configuration; misconfiguration risks leaking or misrouting Notion tokens between tenants
- The README states this local server may be sunset in favor of the remote Notion MCP, and that issues/PRs here are not actively monitored, so long-term maintenance and security fixes are not guaranteed
- Storing NOTION_TOKEN or OPENAPI_MCP_HEADERS directly in shared client config files risks leaking the secret
|
|---|
| Supported clients | Claude Desktop, Cursor, Windsurf | Claude Desktop, Cursor, Zed, GitHub Copilot CLI |
|---|
| Tools | 0 | 9 |
|---|