Data & contentPublic source

Document MCP Server

The most complete multi-backend document MCP server. 29 tools across 3 backends — Google Docs/Drive, Notion, and Microsoft OneDrive/SharePoint. Full CRUD, search, export, comments, and sharing. Single Rust binary with…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Multi-backend — Google Docs/Drive, Notion, Microsoft OneDrive in one server

Feature-flagged — compile only the backends you need (--features google,notion,microsoft)

Full document lifecycle — create, read, update, delete, search, export, comment, share

No credential exposure — tokens stay in env vars, never reach LLM context

Single binary — no Node.js, no Python, no runtime dependencies

Architecture

How Document MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Document MCP Server

Validates the request and owns 29 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Document MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Document MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

30 named tools

google_list_docs

List Google Docs documents

read only

google_search_docs

Search Google Docs by content

read only

google_get_doc

Get Google Doc metadata and structure

read only

google_get_text

Get Google Doc as plain text

read only

google_create_doc

Create a new Google Doc

internal write

google_insert_text

Insert text into a Google Doc at a position

internal write

google_replace_text

Find and replace text in a Google Doc

internal write

google_export_doc

Export Google Doc as text/plain, text/html, or application/pdf

read only

google_list_comments

List comments on a Google Doc

read only

google_add_comment

Add a comment to a Google Doc

internal write

google_share_doc

Share a Google Doc with a user

external write

google_delete_doc

Delete a Google Doc

external write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

15 read only10 internal write5 external write

The registry manifest declares read only, internal write, external write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Long-running tasks

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-document

MCP client configuration

export GOOGLE_ACCESS_TOKEN="ya29.xxxx"

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Api Reference ↗docs/api-reference.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring