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

GetSign in Claude Code

Install the GetSign plugin, approve monday access once, and get a contract signed without leaving the terminal. Five minutes, three commands, no API keys.

Start the setupExplore the plugin
Server URL
https://mcp.getsign.io/mcp
Illustrative workflowMCP

Claude Code + GetSign

Example prompt

“Prepare an NDA for item 987654321 and show me the signing plan.”

  1. 1
    Install the plugin

    Add the MCP server and signing recipes.

  2. 2
    Connect your account

    Complete the OAuth authorization.

  3. 3
    Ask, review, approve

    Claude prepares the workflow for your review.

Your signing recipes, in Claude Code.
Example workflow: not a live session or product screenshot.
Walkthrough

Install and connect

Two of these four steps happen once per monday account, not once per person.

Install GetSign on monday.com

MCP works against your monday account through GetSign, so the app must be on the account before anyone can connect an agent. A monday account admin does this once, for the whole account.

Add GetSign to monday.com

Already using GetSign on your boards? Then this is done: skip to step 2.

Add the GetSign plugin

This is the recommended path. The plugin adds the MCP server and GetSign’s signing recipes as skills: so Claude follows the right tool order from your first message instead of discovering it mid-task. Run all three commands inside Claude Code:

/plugin marketplace add Getsign-JP/getsign-mcp-plugin
/plugin install getsign@getsign
/plugin enable getsign@getsign

The plugin installs disabled: it connects to an external service, so Claude Code makes you opt in. Until you enable it, neither the server nor the skills load.

Prefer the tools without the skills? Add the server on its own instead:

claude mcp add --transport http getsign https://mcp.getsign.io/mcp

Add --scope user to make GetSign available in every project rather than just this repo. Claude Code deduplicates MCP servers by endpoint, so installing the plugin next to a getsign server you already added leaves you with one server, not two.

Authorize monday.com

Adding the server and connecting your account are separate steps: the plugin does the first, you do the second. Run:

/mcp

Select the GetSign server: plugin:getsign:getsign if you installed the plugin, getsign if you added it by hand: choose Authenticate, and approve monday access in the browser tab that opens. The token stays with Claude Code; nothing is pasted back into the terminal.

Ask for something

Claude loads the matching GetSign skill on its own from what you ask. Try:

Or invoke a recipe directly with its slash command: for example /getsign:send-new-document.

First run

Run a GetSign preflight check, then show me the workflows on board 123456789.

Send

Send the contract on item 987654321 for signature.

Verify

What a working install looks like

Two checks. If both of these are right, you are connected.

/mcp lists GetSign as connected

Manage MCP servers

 plugin:getsign:getsign   ✔ connected · 27 tools

Twenty-seven tools is the default catalog. A handful of rarely-used tools start hidden to keep Claude's context small: it turns them on for the session by itself when it needs one.

/plugin lists the GetSign skills

getsign@getsign (v1.2.0)  enabled

  send-new-document
  sign-from-file-column
  create-or-update-workflow
  board-pending-signatures
  save-signed-document-to-file-column
  install-getsign-on-new-account

Those six skills are why the plugin beats a bare server: each one carries the tool order that GetSign’s API actually requires, so Claude does not have to work it out as it goes. What each skill does

Troubleshooting

The three failures we actually see

In that order of frequency.

1  GetSign appears in /mcp, but every tool call says you are not authorized

The plugin registered the server and you skipped step 3. Run /mcp, select the GetSign server and authenticate. If you would rather do it in conversation, ask Claude to run a GetSign preflight check: it finds the missing connection and hands you a login link.

2  The login page says the GetSign app is not installed on this account

Step 1 has not been done for that monday account, or it was uninstalled. A monday admin needs to install GetSign first. Or ask Claude to install GetSign on the account: it returns one link that shows monday’s install screen only when the app is genuinely missing, then goes straight into the authorization step.

3  You end up with two GetSign servers, or none

Claude Code deduplicates by endpoint, not by name, so a plugin server and a hand-added getsign pointing at the same URL collapse into one. Two usually means the URLs differ: a typo, or a trailing slash. None usually means the plugin is still disabled (run /plugin enable getsign@getsign), or the client was not restarted after the config changed. Check the URL is exactly https://mcp.getsign.io/mcp.

Keep confirmations on. Sending a signature request, cancelling one or resetting a signing process are real actions with real recipients. GetSign asks for confirmation before the destructive ones, and Claude Code asks before each tool call unless you have allowlisted it: we recommend leaving both on for write tools.

Continue with GetSign MCP

Choose the next MCP guide based on what you are trying to finish now. You can connect another AI client, send a first document for signature, review every available MCP tool, or return to the overview before sharing the setup with your team.

MCP guideSetup guides

Connect Claude Code, ChatGPT, Claude Desktop, Cursor, Codex, VS Code, or another MCP-compatible client. The setup path explains where the server URL goes and what to check before the first signing request.

MCP guideChatGPT

Connect Claude Code, ChatGPT, Claude Desktop, Cursor, Codex, VS Code, or another MCP-compatible client. The setup path explains where the server URL goes and what to check before the first signing request.

MCP guideQuickstart

Walk through a first GetSign MCP send from a connected AI agent. It shows the prompt flow, document preparation, approval step, sending, and tracking through to the signed PDF.

MCP guideTool reference

Use the tool and recipe reference when you need the exact actions behind a workflow. It explains what the MCP server exposes and how the tools chain together for common signing jobs.

MCP guidePlugin guide

Install the GetSign MCP plugin when your agent supports skills and you want guided recipes loaded before work begins. It helps the agent follow the right order for signing workflows.

Send a first document with the quickstart, or learn how the signing skills work in the plugin guide.

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.