| FMRS | 55 / 100 · C | 66 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 9 / 20 | 15 / 20 |
|---|
| Maintenance | 11 / 20 | 15 / 20 |
|---|
| Documentation | 14 / 20 | 15 / 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.
| - Developers, content creators, and project teams using Atlassian Cloud
- Teams that want Atlassian access inside ChatGPT, Claude, Cursor, or VS Code
- Users who need natural-language search, write, and cross-product workflows
|
|---|
| 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 without an Atlassian Cloud site or relevant product permissions
- Deployments requiring a self-hosted MCP server
- Users unwilling to grant an AI client access to Atlassian data or actions
- Jira Service Management or Bitbucket Cloud workflows requiring OAuth authentication
|
|---|
| 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.
| - Jira and Confluence provide read, write, and search permission groups
- Jira Service Management provides read and write access through API tokens only
- Bitbucket Cloud provides read and write access through scoped API tokens only
- Compass is available through OAuth 2.1 only
- The first OAuth installer for a site must have access to the Atlassian apps requested by the MCP scopes
- Organization administrators can manage domain controls, API-token authentication, app access, and audit logs
|
|---|
| 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.
| - AI clients can perform Jira, Confluence, Jira Service Management, Bitbucket, and Compass actions on the user’s behalf
- Prompt injection, indirect prompt injection, and tool-poisoning attacks may cause data exfiltration or unintended changes
- Use least privilege, scoped tokens, and minimal project or workspace access
- Require human confirmation for high-impact or destructive actions and monitor audit logs
|
|---|
| Supported clients | Claude Desktop, Cursor, Windsurf | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 0 | 0 |
|---|