GetSign MCP is now live. The AI-Native document workflow layer for your team. 🎉
Setup

Add GetSign to your AI client

GetSign MCP runs on GetSign's hosted servers. There is nothing to download and nothing to run locally: you add one URL to your client and approve monday access once. No API keys, no client ID, no secret.

Illustrative workflowMCP

Your AI client + GetSign

Example prompt

“Send the agreement for this monday.com item.”

  1. 1
    Connect your AI client

    Add the GetSign MCP server URL.

  2. 2
    Authorize once

    Approve access to your monday.com account.

  3. 3
    Describe your task

    Review the plan before anything is sent.

One connection. Your document workflow.
Example workflow: not a live session or product screenshot.
Three steps

The three steps, whatever your client

Every client below follows the same three steps. Only the middle one differs.

Server URL
https://mcp.getsign.io/mcp
1

Install GetSign on monday.com

MCP works against your monday account through GetSign, so the app has to be on the account first. A monday account admin does this once, for everyone.

Add to monday.com
2

Add the MCP server

Pick your client below. One installer link covers most of them; Claude Code, Cursor and Codex have a plugin that adds GetSign’s signing recipes as skills on top of the tools.

Choose your client
3

Authorize monday, then ask

The first time your agent calls a GetSign tool, your client opens a GetSign login page. Approve monday access once and it can work on your boards.

See the first task

In a hurry? The universal installer picks the right flow for whichever client you are in: open the installer. Use the per-client steps below if you would rather configure it by hand, or if your client is not listed.

By hand

Configure it yourself

GetSign MCP speaks Streamable HTTP and authenticates with OAuth 2.1 using dynamic client registration: so there is never a key, client ID or secret to configure. Every client below needs the same one URL.

Claude Desktop

Recommended: add the plugin.
GetSign is in Anthropic's plugin directory. The plugin adds the MCP server and GetSign's signing recipes as skills.

  1. Open Settings → Plugins → Discover, search for GetSign and press Add.
  2. Connect GetSign and approve monday access, the plugin adds the server, but it does not sign you in.

Or add the server on its own:

  1. Open Settings → Connectors → Add custom connector.
  2. Paste the server URL and add it:
    https://mcp.getsign.io/mcp
  3. Press Connect and approve monday access.

Older Claude Desktop builds without remote connectors can bridge via mcp-remote, but the hosted connector is the supported path.

Troubleshooting

If something goes wrong

Three things account for nearly every failed setup.

The server connects, but every tool says you are not authorized

You added the server but have not finished the OAuth round-trip. Adding the server and connecting your monday account are two separate steps: trigger the login from your client’s MCP list, or just ask the agent to run a GetSign preflight check and follow the link it returns.

The login page says the GetSign app is not installed

Step 1 has not been done on that monday account. A monday admin needs to install GetSign before any user on the account can authorize an agent.

Your client shows no GetSign tools at all

Check the URL is exactly https://mcp.getsign.io/mcp: any other path, or a missing /mcp, returns an error instead of the tools, and some clients show that as a server with nothing in it. Then restart the client; most only read MCP config at startup.

Connect your AI agent to GetSign.

Bring GetSign into the AI client your team already uses. Connect once with OAuth, then ask your agent to prepare documents, send them for signature, track status, and bring the signed PDF back into your monday.com workflow.