OnlyOffice DocSpace MCP Server

OnlyOffice DocSpace MCP Server

What is OnlyOffice DocSpace MCP Server about? Provides a Model Context Protocol server that lets large language models manage and query DocSpace entities (files, folders, rooms, people) through standardized toolsets.

How to use OnlyOffice DocSpace MCP Server?

1. Install via npx:

{
  "mcpServers": {
    "onlyoffice-docspace": {
      "env": {
        "DOCSPACE_BASE_URL": "https://your-instance.onlyoffice.com",
        "DOCSPACE_API_KEY": "your-api-key"
      },
      "command": "npx",
      "args": ["--yes", "@onlyoffice/docspace-mcp"]
    }
  }
}

2. Or build from source with Node 24+ and pnpm.
3. Configure via environment variables (DOCSPACE_BASE_URL, DOCSPACE_API_KEY, etc.) and launch.

Key features

• Supports stdio (default) and optional HTTP transport.
• Four toolsets: files, folders, people, rooms, each exposing multiple CRUD operations.
• Dynamic meta‑tools (call_tool, list_tools, get_tool_input_schema, list_toolsets) for on‑demand tool loading.
• Fine‑grained enable/disable of toolsets and individual tools via DOCSPACE_TOOLSETS, DOCSPACE_ENABLED_TOOLS, DOCSPACE_DISABLED_TOOLS.
• Ability to run in internal mode for company‑only integrations.

Use cases

• Enable AI assistants to create, move, or delete files in DocSpace.
• Automate room provisioning and security settings through LLM‑driven workflows.
• Allow conversational bots to list users, retrieve folder contents, or manage permissions.
• Integrate DocSpace operations into custom enterprise AI pipelines.

FAQ

• Is the server production‑ready? Currently in preview; expect breaking changes.
• Which transport should I use? stdio is default; http is available in internal mode.
• How to authenticate? Provide an API key, PAT, or basic auth via env vars.
• Can I limit exposed tools? Yes, using the toolset and tool enable/disable env vars.
• How to run behind a firewall? Use the HTTP mode with custom host/port configuration.

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.

[!WARNING]

This ONLYOFFICE DocSpace MCP server is currently in preview state. While functional, it may undergo breaking changes, have incomplete features, or contain bugs. Use with caution in production environments and expect potential updates that could affect compatibility.

Installation

Most clients that implement the MCP protocol have a common configuration file in JSON format, inside which you can add ONLYOFFICE DocSpace MCP server as follows:

{
	"mcpServers": {
		"onlyoffice-docspace": {
			"env": {
				"DOCSPACE_BASE_URL": "https://your-instance.onlyoffice.com",
				"DOCSPACE_API_KEY": "your-api-key"
			},
			"command": "npx",
			"args": ["--yes", "@onlyoffice/docspace-mcp"]
		}
	}
}

For a more detailed example of the MCP server installation process, see how it can be done using Claude Desktop.

Build from source

ONLYOFFICE DocSpace MCP server can be built from source. To do this, you need to have the following tools installed on your system:

• Node.js version 24 or higher;
• pnpm version 10 or higher.

This project uses mise, a polyglot tool version manager, which you can use to install these tools. If you already have experience with tools like asdf, nvm, nodenv, or similar ones, you will find it very familiar.

Once you have everything installed, clone the Git repository from the company's Git server:

git clone git@git.onlyoffice.com:ONLYOFFICE/docspace-mcp.git

... or from the GitHub mirror:

git clone git@github.com:ONLYOFFICE/docspace-mcp.git

... install dependencies:

pnpm install

... build ONLYOFFICE DocSpace MCP server:

pnpm build

Now, you can use local build of ONLYOFFICE DocSpace MCP server in your MCP client:

{
	"mcpServers": {
		"onlyoffice-docspace": {
			"env": {
				"DOCSPACE_BASE_URL": "https://your-instance.onlyoffice.com",
				"DOCSPACE_API_KEY": "your-api-key"
			},
			"command": "<repo-dir>/bin/onlyoffice-docspace-mcp"
		}
	}
}

Configuration

The only way to configure ONLYOFFICE DocSpace MCP server is through environment variables. Below is an example of the .env file with possible configuration options:

#
# Internal configuration options
# These options are intended exclusively for use by company employees when
# integrating the DocSpace MCP server into other company products.
#

# Whether to run the DocSpace MCP server in internal mode.
# @type boolean
# @presence optional
# @default false
DOCSPACE_INTERNAL=

#
# General configuration options
# These options are available for all transport protocols.
#

# The transport protocol to use for communication with the DocSpace MCP server.
# The HTTP transport only available in the internal mode for now.
# @type enumeration
# @enum stdio, http
# @presence optional
# @default stdio
DOCSPACE_TRANSPORT=

# The user agent to include in the User-Agent header for DocSpace API requests
# @type string
# @presence optional
# @default @onlyoffice/docspace-mcp v2.0.0
DOCSPACE_USER_AGENT=

# Whether to enable dynamic tools. See the README.md file for more details about
# how dynamic tools work.
# @type boolean
# @presence optional
# @default false
DOCSPACE_DYNAMIC=

# The list of toolsets to use or 'all' to use all available toolsets. See the
# README.md file for more details about how toolsets work.
# @type enumeration (comma-separated)
# @enum See the README.md file for available toolsets
# @presence optional
# @default all
DOCSPACE_TOOLSETS=

# The list of tools to enable. See the README.md file for more details about how
# enabled tools work.
# @type enumeration (comma-separated)
# @enum See the README.md file for available tools
# @presence optional
# @default none
DOCSPACE_ENABLED_TOOLS=

# The list of tools to disable. See the README.md file for more details about
# how disabled tools work.
# @type enumeration (comma-separated)
# @enum See the README.md file for available tools
# @presence optional
# @default none
DOCSPACE_DISABLED_TOOLS=

#
# stdio configuration options
# These options are available only for the stdio transport protocol.
#

# The base URL of the DocSpace instance for API requests.
# @type url
# @presence required
# @example https://your-instance.onlyoffice.com
DOCSPACE_BASE_URL=

# The origin URL to include in the Origin header for DocSpace API requests.
# @type url
# @presence optional
# @example https://your-instance.onlyoffice.com
DOCSPACE_ORIGIN=

# The API key for accessing the DocSpace API.
# @type
#   string
# @presence
#   Required if nether DOCSPACE_AUTH_TOKEN nor DOCSPACE_USERNAME and
#   DOCSPACE_PASSWORD are provided.
# @example
#   sk-a499e...
DOCSPACE_API_KEY=

# The Personal Access Token (PAT) for accessing the DocSpace API.
# @type
#   string
# @presence
#   Required if neither DOCSPACE_API_KEY nor DOCSPACE_USERNAME and
#   DOCSPACE_PASSWORD are provided.
# @example
#   Fe4Hrgl6...
DOCSPACE_AUTH_TOKEN=

# The username for accessing the DocSpace API using basic authentication.
# @type
#   string
# @presence
#   Required if neither DOCSPACE_API_KEY nor DOCSPACE_AUTH_TOKEN are provided.
#   This configuration is used in conjunction with DOCSPACE_PASSWORD.
# @example
#   henry.milton@onlyoffice.com
DOCSPACE_USERNAME=

# The password for accessing the DocSpace API using basic authentication.
# @type
#   string
# @presence
#   Required if neither DOCSPACE_API_KEY nor DOCSPACE_AUTH_TOKEN are provided.
#   This configuration is used in conjunction with DOCSPACE_USERNAME.
# @example
#   ditgor-p...
DOCSPACE_PASSWORD=

#
# HTTP configuration options
# These options are available only for the http transport protocol.
#

# The host to listen on for incoming HTTP requests.
# @type string
# @presence optional
# @default 127.0.0.1
DOCSPACE_HOST=

# The port to listen on for incoming HTTP requests.
# @type number
# @presence optional
# @default 8080
DOCSPACE_PORT=

# The time-to-live (TTL) for HTTP sessions in milliseconds.
# @type number
# @presence optional
# @default 28800000 (8 hours)
DOCSPACE_SESSION_TTL=

# The interval for checking HTTP sessions for expiration in milliseconds.
# @type number
# @presence optional
# @default 240000 (4 minutes)
DOCSPACE_SESSION_INTERVAL=

Usage

Model Context Protocol describes several different concepts, however ONLYOFFICE DocSpace MCP server implements Tools only.

Tools

[!NOTE]

In addition to the existing concept of Tools, ONLYOFFICE DocSpace MCP server introduces a new one, Toolsets. A Toolset is a set of related tools.

In ONLYOFFICE DocSpace MCP server, all toolsets and their tools are available by default. However, you can manage this using the following configuration options: DOCSPACE_TOOLSETS, DOCSPACE_ENABLED_TOOLS, and DOCSPACE_DISABLED_TOOLS. See the Examples section for more details on how to configure these options.

Below is a table of available toolsets:

#	Toolset Name	Toolset Description
1	files	Operations for working with files.
2	folders	Operations for working with folders.
3	people	Operations for working with users.
4	rooms	Operations for working with rooms.

Below are tables of available tools:

#	Tool Name	Tool Description
1	copy_batch_items	Copy to a folder.
2	delete_file	Delete a file.
3	download_file_as_text	Download a file as text.
4	get_file_info	Get file information.
5	move_batch_items	Move to a folder.
6	update_file	Update a file.
7	upload_file	Upload a file.

#	Tool Name	Tool Description
8	create_folder	Create a folder.
9	delete_folder	Delete a folder.
10	get_folder_content	Get content of a folder.
11	get_folder_info	Get folder information.
12	get_my_folder	Get the 'My Documents' folder.
13	rename_folder	Rename a folder.

#	Tool Name	Tool Description
14	get_all_people	Get all people.

#	Tool Name	Tool Description
15	archive_room	Archive a room.
16	create_room	Create a room.
17	get_room_access_levels	Get a list of available room invitation access levels.
18	get_room_info	Get room information.
19	get_room_security_info	Get a list of users with their access levels to a room.
20	get_room_types	Get a list of available room types.
21	get_rooms_folder	Get the 'Rooms' folder.
22	set_room_security	Invite or remove users from a room.
23	update_room	Update a room.

Meta Tools

In some cases, directly connecting all available tools can be problematic. Using the DOCSPACE_DYNAMIC configuration option, you can wrap all available tools into meta-tools. Meta-tools are tools that allow an AI model to interact with other tools dynamically without loading them all simultaneously. Below is a table of available meta-tools:

#	Meta Tool Name	Meta Tool Description
1	call_tool	This is a meta-tool for calling a tool. The list of available tools can be obtained using the list_tools meta-tool. The input schema can be obtained using the get_tool_input_schema meta-tool.
2	get_tool_input_schema	This is a meta-tool for getting an input schema for a specific tool. The list of available tools can be obtained using the list_tools meta-tool.
3	list_tools	This is a meta-tool for listing available tools of a specific toolset. The list of available toolsets can be obtained using the list_toolsets meta-tool.
4	list_toolsets	This is a meta-tool for listing available toolsets. Toolset is a set of available tools.

The DOCSPACE_DYNAMIC configuration option is complementary to DOCSPACE_TOOLSETS, DOCSPACE_ENABLED_TOOLS, and DOCSPACE_DISABLED_TOOLS configuration options.

Examples

In this section you can find examples of how to configure ONLYOFFICE DocSpace MCP server. For simplicity, let us come up with a small list of available toolsets and tools. The real server provides more of them, but for these examples, just a few are enough:

Toolset	Tools
files	create_file, get_file, delete_file
folders	create_folder, get_folder, delete_folder

Enable a tool from not specified toolset

Configuration:

DOCSPACE_TOOLSETS=files
DOCSPACE_ENABLED_TOOLS=create_folder

Result:

Toolset	Tools
files	create_file, get_file, delete_file
folders	create_folder

Disable a tool from specified toolset

Configuration:

DOCSPACE_TOOLSETS=files
DOCSPACE_ENABLED_TOOLS=create_folder
DOCSPACE_DISABLED_TOOLS=get_file

Result:

Toolset	Tools
files	create_file, delete_file
folders	create_folder

Manually specify tools to be available

Configuration:

DOCSPACE_TOOLSETS= # Keep this empty to disable all tools
DOCSPACE_ENABLED_TOOLS=create_file,get_file,create_folder
DOCSPACE_DISABLED_TOOLS=get_file,delete_folder

Result:

Toolset	Tools
files	create_file
folders	create_folder

License

ONLYOFFICE DocSpace MCP server is distributed under the Apache-2.0 license found in the LICENSE file.