Revdoku MCP

Revdoku connects assistants to document storage and mailbox workflows through a hosted MCP endpoint with account-specific OAuth access.

Remote serverstreamable-http

What is the Revdoku MCP Server?

Revdoku connects assistants to document storage and mailbox workflows through a hosted MCP endpoint with account-specific OAuth access.

Work with documents and mailboxes

Revdoku's hosted MCP connection gives an agent access to the accounts and mailboxes authorized by the user. The broader product supports stored-file workflows, document versions and submission replies. The CLI, API and MCP interface are different ways into that service; installing a repository skill is not the same as authorizing the MCP connection.

Authorize each agent

The official connection guide uses Streamable HTTP and browser OAuth at the hosted endpoint. Each agent needs its own authorized connection. Select the account and access scope during sign-in, then verify the available mailboxes before asking the agent to work with documents.

Start with a known item

List the intended accounts and mailboxes, retrieve a test document and compare its content with the stored version. Creating or submitting a document is a separate action from reading it. Confirm the destination and resulting version when a workflow writes data, and use the product's version history when reviewing an unintended change.

Project documentation

Repository and setup guide

How to install the Revdoku MCP Server

{
  "mcpServers": {
    "revdoku": {
      "url": "https://mcp.revdoku.com"
    }
  }
}

Configuration

A Revdoku account and an HTTP MCP client that supports the documented OAuth flow.

Example prompts to try

  • “Use Revdoku to OpenClaw.”

Frequently asked questions

No. The connection guide says each agent needs its own authorized connection.