io.github.ONLYOFFICE/docspace MCP Server
io.github.ONLYOFFICE/docspace
AI-powered room-based collaboration for ONLYOFFICE DocSpace with natural language document and permission management.
What is the io.github.ONLYOFFICE/docspace MCP server?
The ONLYOFFICE DocSpace MCP Server is an MCP server that connects AI agents and chatbots directly to ONLYOFFICE DocSpace, enabling management of rooms, files, permissions, and collaborative workflows through natural language. It supports multiple authentication methods (API keys, PAT, Basic auth, OAuth 2.0) and transport protocols (stdio, SSE, Streamable HTTP).
This MCP server bridges AI tools with ONLYOFFICE DocSpace, a room-based collaborative platform. It allows AI agents to create and manage rooms, handle file operations, control permissions, invite users, and automate document workflows—all through conversational commands. Available as Docker, npm package, or remote hosted service.
How to install io.github.ONLYOFFICE/docspace
Copy-paste configuration for popular MCP clients.
DOCSPACE_BASE_URLThe base URL of the DocSpace instance for API requests.
DOCSPACE_API_KEYsecretThe API key for accessing the API.
DOCSPACE_TRANSPORTThe transport protocol to use for communication with the MCP server.
DOCSPACE_DYNAMICThe flag that indicates whether the MCP server should use meta tools.
DOCSPACE_TOOLSETSThe list of toolsets to enable for the MCP server.
DOCSPACE_ENABLED_TOOLSThe list of tools to enable for the MCP server.
DOCSPACE_DISABLED_TOOLSThe list of tools to disable for the MCP server.
DOCSPACE_USER_AGENTThe user agent to include in the User-Agent header for API requests.
DOCSPACE_AUTHORIZATIONsecretThe raw value to include in the Authorization header for API requests.
DOCSPACE_AUTH_TOKENsecretThe Personal Access Token (PAT) for accessing the API.
DOCSPACE_USERNAMEThe username for accessing the API using basic authentication.
DOCSPACE_PASSWORDsecretThe password for accessing the API using basic authentication.
DOCSPACE_SESSION_TTLThe time-to-live (TTL) for HTTP sessions in milliseconds.
DOCSPACE_SESSION_INTERVALThe interval for checking HTTP sessions for expiration in milliseconds.
DOCSPACE_OAUTH_BASE_URLThe base URL of the DocSpace OAuth service for OAuth requests.
DOCSPACE_OAUTH_CLIENT_IDThe client ID of the OAuth application.
DOCSPACE_OAUTH_CLIENT_SECRETsecretThe client secret of the OAuth application.
DOCSPACE_OAUTH_AUTH_TOKEN_ALGORITHMThe algorithm to use for signing OAuth access tokens.
DOCSPACE_OAUTH_AUTH_TOKEN_TTLThe time-to-live (TTL) for OAuth access tokens in milliseconds.
DOCSPACE_OAUTH_AUTH_TOKEN_SECRET_KEYsecretThe secret key to use for signing OAuth access tokens.
DOCSPACE_OAUTH_STATE_TOKEN_ALGORITHMThe algorithm to use for signing OAuth state tokens.
DOCSPACE_OAUTH_STATE_TOKEN_TTLThe time-to-live (TTL) for OAuth state tokens in milliseconds.
DOCSPACE_OAUTH_STATE_TOKEN_SECRET_KEYsecretThe secret key to use for signing OAuth state tokens.
DOCSPACE_SERVER_BASE_URLThe base URL of the server.
DOCSPACE_HOSTThe host to bind the server to.
DOCSPACE_PORTThe port to bind the server to.
DOCSPACE_SERVER_PROXY_HOPSThe number of proxy servers between the server and the client.
DOCSPACE_SERVER_CORS_MCP_ORIGINThe list of allowed origins to include in the Access-Control-Allow-Origin header for CORS requests to MCP endpoints.
DOCSPACE_SERVER_CORS_MCP_MAX_AGEThe maximum age in milliseconds to include in the Access-Control-Max-Age header for CORS requests to MCP endpoints.
DOCSPACE_SERVER_CORS_OAUTH_ORIGINThe list of allowed origins to include in the Access-Control-Allow-Origin header for CORS requests to OAuth endpoints.
DOCSPACE_SERVER_CORS_OAUTH_MAX_AGEThe maximum age in milliseconds to include in the Access-Control-Max-Age header for CORS requests to OAuth endpoints.
DOCSPACE_SERVER_RATE_LIMITS_MCP_CAPACITYThe maximum number of requests allowed per window for the MCP endpoints.
DOCSPACE_SERVER_RATE_LIMITS_MCP_WINDOWThe time window in milliseconds for the rate limit for the MCP endpoints.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_SERVER_METADATA_CAPACITYThe maximum number of requests allowed per window for the OAuth server metadata endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_SERVER_METADATA_WINDOWThe time window in milliseconds for the rate limit for the OAuth server metadata endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_RESOURCE_METADATA_CAPACITYThe maximum number of requests allowed per window for the OAuth resource metadata endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_RESOURCE_METADATA_WINDOWThe time window in milliseconds for the rate limit for the OAuth resource metadata endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_AUTHORIZE_CAPACITYThe maximum number of requests allowed per window for the OAuth authorization endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_AUTHORIZE_WINDOWThe time window in milliseconds for the rate limit for the OAuth authorization endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_CALLBACK_CAPACITYThe maximum number of requests allowed per window for the OAuth callback endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_CALLBACK_WINDOWThe time window in milliseconds for the rate limit for the OAuth callback endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_INTROSPECT_CAPACITYThe maximum number of requests allowed per window for the OAuth introspection endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_INTROSPECT_WINDOWThe time window in milliseconds for the rate limit for the OAuth introspection endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_REGISTER_CAPACITYThe maximum number of requests allowed per window for the OAuth client registration endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_REGISTER_WINDOWThe time window in milliseconds for the rate limit for the OAuth client registration endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_REVOKE_CAPACITYThe maximum number of requests allowed per window for the OAuth token revocation endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_REVOKE_WINDOWThe time window in milliseconds for the rate limit for the OAuth token revocation endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_TOKEN_CAPACITYThe maximum number of requests allowed per window for the OAuth token endpoint.
DOCSPACE_SERVER_RATE_LIMITS_OAUTH_TOKEN_WINDOWThe time window in milliseconds for the rate limit for the OAuth token endpoint.
DOCSPACE_REQUEST_QUERYThe flag that indicates whether the server should accept configuration via query parameters in incoming requests.
DOCSPACE_REQUEST_AUTHORIZATION_HEADERThe flag that indicates whether the server should check for the Authorization header in incoming requests.
DOCSPACE_REQUEST_HEADER_PREFIXThe prefix to use with custom configuration headers.
X-Mcp-DynamicThe flag that indicates whether the MCP server should use meta tools.
X-Mcp-ToolsetsThe list of toolsets to enable for the MCP server.
X-Mcp-Enabled-ToolsThe list of tools to enable for the MCP server.
X-Mcp-Disabled-ToolsThe list of tools to disable for the MCP server.
X-Mcp-Base-UrlThe base URL of the DocSpace instance for API requests.
X-Mcp-Api-KeysecretThe API key for accessing the API.
X-Mcp-Auth-TokensecretThe Personal Access Token (PAT) for accessing the API.
X-Mcp-UsernameThe username for accessing the API using basic authentication.
X-Mcp-PasswordsecretThe password for accessing the API using basic authentication.
Tools & capabilities
Tools this server exposes to the agent.
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.
Use cases
- Create and configure project rooms with specific access levels and invite team members via natural language
- Upload and organize documents in DocSpace folders, then move or copy them in bulk across rooms
- Manage user permissions and access rights across multiple rooms and shared spaces
- Retrieve and download files from DocSpace as text for processing or analysis by AI agents
- Automate document workflows by combining room creation, file uploads, and permission assignments in a single command
io.github.ONLYOFFICE/docspace MCP server FAQ
It's an MCP server that connects AI agents and chatbots to ONLYOFFICE DocSpace, enabling them to manage rooms, collaborate on files, handle permissions, and automate document workflows through natural language commands.
The server itself is open-source (MIT license). ONLYOFFICE offers a free remote instance at mcp.onlyoffice.com, or you can self-host locally using Docker or npm.
Add a configuration block to your client's JSON config file pointing to either the remote server (https://mcp.onlyoffice.com/mcp) or a local Docker instance. Restart your client and it will connect automatically.
The server supports API keys, Personal Access Tokens, Basic authentication, and OAuth 2.0 with dynamic client registration.
Yes, you need access to an ONLYOFFICE DocSpace instance (self-hosted or cloud). You'll provide its URL and API key during configuration.
It supports stdio, SSE (Server-Sent Events), and Streamable HTTP transports, with Streamable HTTP being preferred for modern clients.
README (reference)
Source of truth, from the repository.
ONLYOFFICE DocSpace MCP Server
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.
Features
- Tools with granular control - Access to tools organized into logical toolsets with fine-grained enable/disable capabilities and meta tools.
- Multiple transport protocols - Support for stdio, SSE, and Streamable HTTP transports.
- Different authentication methods - Supports API keys, Personal Access Tokens, Basic authentication, and OAuth 2.0 with dynamic client registration. See examples.
- Request-level configuration - Configure authentication and tool selection during session initialization using custom HTTP headers.
- Various distribution formats - Available as Docker image, Docker MCP Server, MCP bundle, and Node.js application.
Use Cases
- 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.
Connecting Clients to DocSpace MCP Server
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 here you can read about it.
Remote DocSpace MCP Server
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 here.
Local DocSpace MCP Server
If your MCP host does not support remote MCP servers, you can run the local version of the DocSpace MCP Server instead.
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.
Step 1. Locate your config file
Find your client .json configuration file.
Step 2. Add the DocSpace MCP Server entry
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"
}
}
}
}
Step 3. Set environment values
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 here.
Step 4. Restart the client
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".
Tools
The DocSpace MCP server implements the Tools concept described in the MCP specification.
All DocSpace MCP server tools are described here.
Documentation
The documentation is available in the docs directory.
Samples
The following examples show how to use ONLYOFFICE DocSpace MCP server.
Privacy Policy
The policies are available at Legal Terms and Privacy Policy.
License
The DocSpace MCP server is distributed under the MIT license found in the LICENSE file.
<!-- Footnotes -->Related MCP servers
MCP server que conecta agentes de IA aos dados abertos do ONS (Operador Nacional do Sistema)
Provenance-first DePIN telemetry: 331 live networks + 129 Bittensor subnets, 10,508 series.
View repository →
Obelinf
MCP server for Obelinf, the network documentation platform. Sites, racks, devices, IPs, VLANs.

io.github.Obi49/colber-mcp
Trust + coordination infrastructure for the agent economy. 27 tools across 6 Colber modules.
My first MCP server for testing
