mcpbeat Sign in

Docusign MCP Server

answering

Docusign is answering right now. Last checked 13 min ago.

Uptime history 48 days of history
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
408 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Docusign every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.docusign.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.docusign.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.docusign.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.docusign.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.docusign.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://mcp.docusign.com/mcp streamable-http needs auth 442 ms 13 min ago

Alternatives to Docusign

same job, measured the same way
Design Feeds
by pipeworx-io

Design Feeds MCP.

34 tools answering
Signnow
by signnow
answering
I
MCP Docs
by fusionauth

FusionAuth Documentation MCP server

2 tools answering
V
Doordash
by doordash
answering
Dovetail
by dovetail
answering

Docusign — questions

Answers built from our own checks of this server.

Why is there no tool list for Docusign?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Docusign working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 408 ms. The bar chart above shows every period we have measured.
How do I connect Docusign?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Docusign need an API key?
Yes. Every time we knock, Docusign answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Docusign?
It answers our handshake in 408 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.