M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
O

ONLYOFFICE DocSpace MCP Server

Official
Connect AI agents directly to ONLYOFFICE DocSpace to manage rooms, files, and permissions in natural language.
How to install ↓ Compare GitHub source repository ↗
Category
Collaboration #25 of 55
Stars
★ 32 Popular
Transport
stdio (local process) · SSE · Streamable HTTP
Runtime
Docker · Node.js · Hosted (no local runtime)
Credentials
API key / credential required
License
MIT
Last commit
55FMRS · C

An official ONLYOFFICE-maintained DocSpace MCP server that plugs AI clients directly into DocSpace for room, file, permission, and people management. It offers stdio/SSE/Streamable HTTP transports, multiple authentication methods, and a hosted remote instance under the MIT license. Best suited to DocSpace users who want natural-language automation of document collaboration, though credentials must be protected and destructive batch operations handled with care.

Strongest · Documentation 14/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
9/20
Maintenance
11/20
Documentation
14/20
Setup experience
13/20
Why each score
Reliability 8/20
The README shows three transports (stdio/SSE/Streamable HTTP), four auth methods, and links to tool docs, indicating a well-structured declared capability surface. However, all judgments come only from the README and the supplied metadata; there is no cached server manifest, no source tree, no CI workflows, and no committed tests, so MCP init + tool-list handshake, whether declared tools match real behavior, and error/dependency control cannot be verified. Static calibration caps reliability at 12 without verifiable execution evidence (real CI plus tests covering key paths); with no test or error-handling evidence at all, a conservative 8 is given.
Security and permissions 9/20
The README's local example injects DOCSPACE_API_KEY via environment variables and uses placeholders rather than real secrets; support for OAuth 2.0 and request-level auth headers suggests credential isolation awareness. No malware, covert exfiltration, or unconfirmed dangerous-by-default operations are evident, so no red line is triggered. Still, permission scoping, confirmation requirements for delete/archive operations, token storage, and log redaction are not documented, so evidence is incomplete and the score is reduced to 9.
Maintenance 11/20
The MIT license is explicit, the repo is not archived, and it reports 0 open issues, indicating an active project with clear ownership by the official ONLYOFFICE organization; the README references multiple distribution channels (Docker Hub, Docker MCP, npm, MCP bundle). But version numbers, commit cadence, issue response times, dependency update policy, and a security-response channel are absent, so sustained maintenance cannot be confirmed; a conservative 11 is assigned.
Documentation 14/20
Documentation is layered: the README gives an overview, features, use cases, remote and local connection guidance, environment variable descriptions, and links to docs for tools, global configuration, request-level configuration, per-client setup, and distribution, plus tool and installation examples. The gap is that linked docs are not part of the supplied material, so tool parameters, limits, and troubleshooting cannot be verified, and error handling and platform differences are thinly disclosed; the score is reduced to 14.
Setup experience 13/20
The install path is clear: a mainstream-client JSON config template (Docker-based, with mcpServers structure and env placeholders is provided), and the hosted remote instance allows instant connection without local deployment, with Docker/npm/MCP bundle options available. However, full setup requires Docker or a Node runtime and self-generated API keys, and copy-paste examples for multiple clients plus verification steps are lacking. Per static calibration the setup cap is 15 without execution evidence, so a conservative 13 is given.

Static review · not runListed 2026-09-10

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesUses the networkChanges third-party account data

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.

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).

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.

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.

Setup

Before you start

Runtime：Docker · Node.js · Hosted (no local runtime)

DOCSPACE_BASE_URL required The URL of your ONLYOFFICE DocSpace instance (e.g. https://portal.onlyoffice.com).
DOCSPACE_API_KEY requiredsecret Your personal API key generated in DocSpace settings -> Developer Tools -> API keys.
  1. Locate your client's JSON configuration file.
  2. Add an onlyoffice-docspace entry under mcpServers: command is docker, args are run --interactive --rm --env DOCSPACE_BASE_URL --env DOCSPACE_API_KEY onlyoffice/docspace-mcp (Docker must be installed).
  3. Set environment values: DOCSPACE_BASE_URL to your DocSpace instance URL, and DOCSPACE_API_KEY to your personal API key generated in DocSpace settings -> Developer Tools -> API keys.
  4. Restart the client; the server usually starts automatically, and you can issue natural language commands such as "Create a new project room and invite Anna with editor rights."

Alternatively, connect to the ONLYOFFICE-hosted remote server: use https://mcp.onlyoffice.com/mcp for clients supporting Streamable HTTP, or https://mcp.onlyoffice.com/sse for clients that only support legacy SSE.

claude_desktop_config.json 
{
  "mcpServers": {
    "onlyoffice-docspace": {
      "command": "docker",
      "args": [
        "run",
        "--interactive",
        "--rm",
        "--env",
        "DOCSPACE_BASE_URL",
        "--env",
        "DOCSPACE_API_KEY",
        "onlyoffice/docspace-mcp"
      ],
      "env": {
        "DOCSPACE_BASE_URL": "https://your-instance.onlyoffice.com",
        "DOCSPACE_API_KEY": "your-api-key"
      }
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "onlyoffice-docspace": {
      "command": "docker",
      "args": [
        "run",
        "--interactive",
        "--rm",
        "--env",
        "DOCSPACE_BASE_URL",
        "--env",
        "DOCSPACE_API_KEY",
        "onlyoffice/docspace-mcp"
      ],
      "env": {
        "DOCSPACE_BASE_URL": "https://your-instance.onlyoffice.com",
        "DOCSPACE_API_KEY": "your-api-key"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add onlyoffice-docspace -e DOCSPACE_BASE_URL=https://your-instance.onlyoffice.com -e DOCSPACE_API_KEY=your-api-key -- docker run --interactive --rm --env DOCSPACE_BASE_URL --env DOCSPACE_API_KEY onlyoffice/docspace-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the config and restarting the client, DocSpace tools should appear in the client's tool list; ask the AI to "list all rooms" — a response with data from your instance confirms the connection.

Troubleshooting

  1. Verify DOCSPACE_BASE_URL points to the correct DocSpace instance (e.g. https://portal.onlyoffice.com).
  2. Verify DOCSPACE_API_KEY was generated in DocSpace settings -> Developer Tools -> API keys and is still valid.
  3. For the local server, confirm Docker is installed and running and that the onlyoffice/docspace-mcp image pulls correctly.
  4. When using the remote server, check whether your client supports Streamable HTTP; if it only supports SSE, use the /sse endpoint.
  5. Restart the client after changing configuration and confirm the server starts automatically.
  6. If tools are unavailable, check whether they were disabled by toolset or meta tool settings.

Things to try

Once connected, you can ask your AI assistant things like:

  • Create a new project room and invite Anna with editor rights.
  • Upload this file to "My documents".
  • List all rooms and their access levels.
  • List all people in the portal.

Use cases

Room management: create, update, and archive rooms; configure room types; manage membership and access levels.
Folder and file operations: create folders, upload documents, copy or move items in batches, rename or delete content, and check file or folder details.
Collaboration and permissions: invite or remove users, adjust security settings, and review current access rights for rooms and shared spaces.
Content access: retrieve "My documents" or "Rooms" folders, get folder contents, download files as text, and monitor ongoing file operations.
People directory: list all people in the portal to streamline invitations and access management.

Supported clients

Claude Desktop
Cursor
Windsurf

Listed from the project's documentation, not tested by this site.

Overview

The ONLYOFFICE DocSpace MCP Server is ONLYOFFICE's official Model Context Protocol server that connects AI tools directly to ONLYOFFICE DocSpace. It gives AI agents, assistants, and chatbots the ability to manage rooms, collaborate on files, handle permissions, and automate document workflows through natural language interactions. The server supports stdio, SSE, and Streamable HTTP transports, accepts API keys, Personal Access Tokens, Basic authentication, and OAuth 2.0 with dynamic client registration, and allows request-level configuration of authentication and tool selection via custom HTTP headers at session initialization. Tools are organized into logical toolsets with fine-grained enable/disable capabilities and meta tools, and the server is distributed as a Docker image, Docker MCP Server, MCP bundle, and Node.js application. ONLYOFFICE also hosts remote instances (https://mcp.onlyoffice.com/mcp and https://mcp.onlyoffice.com/sse) for instant connection without deployment.

Similar servers

Compare with other MCP servers

Source revision 181a1d329cc5 Data synced 2026-10-19 Read the FMRS scoring method