Documentation MCP

The Signeasy API docs have their own Model Context Protocol (MCP) server at https://docs.signeasy.com/mcp. Connect it to an AI tool such as Cursor, VS Code, Windsurf, or Claude, and your assistant can look up endpoints and send requests to the API while it writes your integration.

This is a different server from the Signeasy MCP, which connects Claude to a Signeasy account for everyday document work.

What it can do

The server has four tools.

Tool	What it does
`list-endpoints`	Lists every API path and method, with a summary of each.
`search-endpoints`	Searches paths, operations, and parameters by keyword.
`get-endpoint`	Returns the full definition of one endpoint, including its parameters, request body, and responses.
`execute-request`	Sends a request to the Signeasy API.

It covers the API reference. It doesn't search the guides.

🚧
Use a sandbox token
execute-request sends real requests with whatever access token you give your assistant. Use a sandbox token while you build, and never paste a live token into an AI tool.

Set it up

Add the server to your tool's MCP configuration.

Add to mcp.json:

{
  "servers": {
    "signeasy": {
      "url": "https://docs.signeasy.com/mcp",
      "type": "http"
    }
  },
  "inputs": []
}

Try it

Once it's connected, ask your assistant questions like these.

"Which endpoint sends a document for signature with fields placed by coordinates?"
"Show me the request body for fetching an embedded signing URL."
"Write a Node.js function that uploads a PDF and sends it to one signer."