Model Context Protocol (MCP) is a standardized protocol for managing context between large language models (LLMs) and external systems. This repository provides an MCP server for ONLYOFFICE DocSpace.
The DocSpace MCP Server connects AI tools directly to ONLYOFFICE DocSpace. This gives AI agents, assistants, and chatbots the ability to manage rooms, collaborate on files, handle permissions, and automate document workflows - all through natural language interactions.
- Tools with granular control - Access to
- Multiple transport protocols - Support for stdio, SSE, and Streamable HTTP
- Different authentication methods - Supports API keys, Personal Access
Tokens, Basic authentication, and OAuth 2.0 with dynamic client registration. See
- Request-level configuration - Configure authentication and tool selection
during session initialization using
- Various distribution formats - Available as
- Room Management: Create, update, and archive rooms. Configure room types, manage membership, and control access levels.
- Folder & File Operations: Create folders, upload documents, copy or move items in batches, rename or delete content, and check file or folder details.
- Collaboration & 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.
You can connect to the DocSpace MCP server using any MCP clients. We have covered some popular clients, such as Claude Desktop, Cursor, Windsurf, etc., and
The remote DocSpace MCP Server is hosted by ONLYOFFICE and provides the fastest way to start using DocSpace tools inside your AI agent. You can connect to it instantly without deploying or configuring anything on your machine.
The public instance is available at https://mcp.onlyoffice.com/mcp for clients that support modern Streamable HTTP transport and at https://mcp.onlyoffice.com/sse for clients that support only the legacy SSE transport. It is preferable to use the Streamable HTTP transport whenever possible.
See all options for connecting clients to the Remote DocSpace MCP Server
If your MCP host does not support remote MCP servers, you can run the
Most clients that implement the MCP protocol have a common configuration file in the JSON format, inside which you can add the ONLYOFFICE DocSpace MCP Local Server.
Note: The common example below is applicable for Docker image, so Docker must be installed on your system.
Find your client .json configuration file.
Insert the following block into the mcpServers section of your .json configuration file:
{
"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"
}
}
}
}DOCSPACE_BASE_URL- the URL of your DocSpace instance (e.g. https://portal.onlyoffice.com).DOCSPACE_API_KEY- your personal API key generated in DocSpace settings -> Developer Tools -> API keys.
All available parameters are listed
Close and reopen your client. In most cases, the DocSpace MCP Server will start automatically, and you'll be able to issue natural language commands like:
- Create a new project room and invite Anna with editor rights.
- Upload this file to "My documents".
The DocSpace MCP server implements the Tools concept described in the MCP specification.
All DocSpace MCP server tools are described
The documentation is available in the docs directory.
The following examples show how to use ONLYOFFICE DocSpace MCP server.
The policies are available at Legal Terms and Privacy Policy.
The DocSpace MCP server is distributed under the MIT license found in the LICENSE file.