home / mcp / docdocdoc mcp server

DocDocDoc MCP Server

Provides a centralized MCP server to manage document requests, including creation, status tracking, and document submissions for DocDocDoc.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "kanta-inc-docdocdoc-mcp-server": {
      "url": "http://localhost:3000",
      "headers": {
        "API_KEY": "your-api-key-here",
        "BASE_URL": "https://staging.docdocdoc.fr"
      }
    }
  }
}

You deploy and use the DocDocDoc MCP Server to manage document requests via a scalable API. It lets you create, read, update, delete, and cancel requests, track status, and handle common document types through a clear MCP interface.

How to use

You interact with the DocDocDoc MCP Server using an MCP client. Create a request to start a document exchange, fetch details to review or confirm information, update the request when requirements change, cancel if needed, or permanently delete a request. Each operation updates the request’s lifecycle status so you can monitor progress at a glance.

Common actions you can perform include creating a new document request, retrieving details by ID, updating the requested document type or message, cancelling a request to mark it as no longer active, and deleting a request to remove it from the system. The server supports multiple document types such as ID cards, passports, driver licenses, and more, and it reports statuses like pending, viewed, completed, cancelled, and expired so you always know where a request stands.

How to install

Prerequisites: ensure you have Python available on your system. You will also use the UDP-based runtime tool to start and interact with the server.

Prerequisites continued: ensure you have the required runtime available for the MCP server commands used in this setup.

Step 1: Start the server in development mode using the runtime command shown below.

uv run main.py

Configuration and usage examples

Configure the MCP client to connect to the DocDocDoc MCP Server using HTTP transport. The server will run on port 3000 by default and can be pointed at your local instance or a staging URL.

{
  "mcpServers": {
    "docdocdoc-mcp-server": {
      "url": "http://localhost:3000",
      "env": {
        "API_KEY": "your-api-key-here",
        "BASE_URL": "https://staging.docdocdoc.fr"
      }
    }
  }
}

Additional sections

Configuration details cover how to enable HTTP transport and the recommended environment variables. The HTTP transport is the preferred method, with a legacy STDIO transport available for backward compatibility. When using STDIO, ensure you provide the complete command and arguments as shown in the setup examples.

Security and notes

Security features include API key authentication via the X-API-Key header, input validation for emails and required fields, and robust error handling. Use your API key to authorize requests to the DocDocDoc MCP Server and protect sensitive document data.

Architecture

The server features a modular design with a dedicated API client for DocDocDoc, environment-based configuration management, and comprehensive error reporting to help you diagnose issues quickly.

Available tools

create_request

Create a new document request with details about the requested document type, recipient, and message.

get_request

Retrieve details for a specific request by its unique identifier.

update_request

Modify an existing request, such as changing the document type or message.

delete_request

Permanently remove a request from the system.

cancel_request

Cancel a request, marking it as cancelled without deleting its data.