Hosted MCP server

GetSign MCP for monday.com

Automate eSignature, document generation, and status tracking from Claude, Cursor, and ChatGPT without leaving the chat. No API keys to paste. Start for free.

Connect GetSign MCP See setup steps

No API keysAuthorize monday once27 agent tools

Instruction

Send the renewal for the Acme Industries deal

Runtime log

14:31:52read board itemDeals / Acme Industries · #4821

14:31:53pulled fieldscompany · value · date · signer

14:31:55generated draftRenewal_Agreement_Acme_2026.pdf

14:31:57plan readyholding for your approval

Renewal_Agreement_Acme_2026.pdf Awaiting your approval

to [email protected] · term 12 mo · $24,000/yr · order J. Reyes → You

Source: monday.com · Deals board

Set up in minutes. Powered by GetSign.

Set up GetSign MCP in 3 simple steps

GetSign MCP runs on hosted servers. Nothing to download, nothing to run locally.

Server URL

https://mcp.getsign.io/mcp

Install GetSign on monday.com

MCP talks to your monday account through GetSign, so the app must be on the account first. A monday admin does this once.

Add to monday.com

Add the MCP server

One URL works everywhere. Claude Code, Cursor and Codex can install the GetSign plugin instead, which adds signing recipes as skills. Each client has its own short guide.

Set up your client

Authorize monday, then ask

Your client opens a GetSign login page the first time. Approve monday access once and the agent can work on your boards.

Send your first document

Works with every MCP client

GetSign MCP works with Claude, ChatGPT, Cursor and more

The installer above covers all of these. Use this section to configure by hand, or if your client is not listed.

Add the server:
claude mcp add --transport http getsign https://mcp.getsign.io/mcp
Run /mcp in Claude Code, select getsign, and authenticate.
Ask: "Use getsign_list_skills and tell me which tools can change data."

Add --scope user to make GetSign available in every project instead of just this repo.

Open Settings → Connectors → Create (developer mode / custom connectors must be enabled).
Paste the MCP server URL and choose OAuth authentication:
https://mcp.getsign.io/mcp
Save, then connect and approve monday access.
Enable the GetSign connector in the composer before asking about a board.

GetSign MCP speaks Streamable HTTP. There is no SSE-only or stdio setup needed for ChatGPT.

Add GetSign to Cursor

Or add it by hand in Settings → MCP → New MCP server:

{
  "mcpServers": {
    "getsign": {
      "url": "https://mcp.getsign.io/mcp"
    }
  }
}

After it appears in the MCP list, click Needs login / the server name to finish monday authorization.

Add GetSign to VS Code

Or run MCP: Add Server → HTTP from the Command Palette, or drop this into .vscode/mcp.json:

{
  "servers": {
    "getsign": {
      "type": "http",
      "url": "https://mcp.getsign.io/mcp"
    }
  }
}

VS Code prompts for sign-in the first time an agent calls a GetSign tool.

Open Settings → Connectors → Add custom connector.
Paste the server URL and add it:
https://mcp.getsign.io/mcp
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.

Any MCP client that supports remote servers with OAuth works. Point it at:

https://mcp.getsign.io/mcp

{
  "mcpServers": {
    "getsign": {
      "url": "https://mcp.getsign.io/mcp"
    }
  }
}

Transport is Streamable HTTP; auth is OAuth 2.1 with dynamic client registration, so there is no client ID or secret to configure. Windsurf, Zed, Codex, Goose and Warp all use one of the two shapes above.

27 MCP tools

27 tools for documents and eSignatures on monday.com

Your agent calls typed tools with known arguments, and the server tells it what comes next. This is why it can complete multi-step signing tasks correctly.

tools on the default catalog

end-to-end recipes

API keys to manage

confirmation layers on writes

Workflows and settings

Create a signing workflow on a board, read its settings, and change reminders, OTP, sender identity, document generation, signature collection or share-and-track, all by describing what you want.

Documents and fields

Upload or choose a template, merge board values into it, detect signature pads and date fields with AI, assign each field to a signer column, and set the signing order.

Send, track, collect

Send by email or shareable link, ask who is still pending across a board, read the complete audit trail, and download the sealed signed PDF.

See all 27 tools and 14 recipes Read the quickstart

Read tools are always safe. Tools that change data are marked as mutating. Sending, cancelling, resetting and deleting require confirmation on the server regardless of what your client allows. Rarely used tools start hidden to keep the agent context small and are enabled for the session when needed.

Why jump between apps?

Generate, send and track documents from one chat

Everything GetSign does on a monday board, an agent can now do in conversation. It explains each step before it changes anything.

Create documents from board data

Turn monday items into proposals, contracts, invoices, and forms, merged with real column values, generated on demand.

Send for signature and track progress

Map signature fields with AI detection, send by email or signing link, then ask who has opened, signed, or is still pending.

Build workflows for any document process

Reminders, OTP verification, approvals, signing order, signed-file write-back, all configured by describing what you want.

Built for how every team already works

Use cases for sales, HR, legal and procurement

GetSign sits inside monday.com, so the same instruction model works wherever documents stall.

Sales and RevOps

Contracts that close on schedule.

GetSign prepares each contract from the deal record, routes it for approval, sends it for signature, and files the signed copy back to the board.

"Send the MSA to every closed-won deal this week."

Customer Success

Onboarding that starts the day the deal closes.

GetSign pulls customer details from the board, prepares the agreement, and tracks every signature so nothing sits waiting on a status nobody checked.

"Send onboarding agreements to this week’s new accounts."

Legal and Contract Ops

Redlines and renewals, tracked end to end.

GetSign holds the document at the approval gate you set, notifies the reviewer, and only sends once Legal signs off, with a complete record of who approved what.

"Route this NDA to Legal for review before it goes out."

HR and People Ops

Offer letters without the chase.

GetSign prepares both documents, sends them together, and files the signed copies to the employee record so onboarding paperwork stops living in email threads.

"Send the offer letter and handbook to this week’s new hires."

Finance and Procurement

Vendor agreements and POs that do not stall.

GetSign moves the document through the approval chain you define and keeps a dated history of every step, so nothing waits on a Slack message someone missed.

"Route this vendor agreement for approval, then send for signature."

Operations

One governed layer instead of five stitched-together tools.

GetSign replaces the automation that breaks quietly in production with a workflow you can see. Every send approved, every document tracked.

"Whenever status changes to Approved, send the linked document."

Example prompts

Whatever the document, just ask.

Copy one of these into your agent to see the flow end to end.

Get started

Use GetSign to run a preflight check, then show me the workflows on board 123456789.

Create a workflow

Create a GetSign workflow named "Sales Agreement" on board 123456789 and summarize its default settings.

Prepare a document

Attach our NDA template to that workflow, detect the signature fields, and assign the signer from the board’s Email column.

Send

Send the GetSign signature request for item 987654321 with the message "Please review and sign this agreement."

Track

Who still needs to sign on board 123456789? Show pending sessions and unsigned signers across the board.

Close out

Summarize the signing history for this item, give me the audit trail, and link the signed PDF.

FAQ

GetSign MCP FAQ

Everything you need to know about connecting your AI agent to GetSign.

What is GetSign MCP?

GetSign MCP is a hosted MCP server that connects AI agents like Claude, ChatGPT, and Cursor to GetSign on monday.com. Generate documents from board data, send for eSignature, track status, and build document workflows from a chat, with OAuth sign-in and no API keys.

Can I use GetSign with AI tools like Claude or ChatGPT?

Yes. GetSign MCP connects to any MCP-compatible AI client like Claude or ChatGPT. You can generate documents, send for signature, track status, and build workflows by describing your intent in a chat. No API keys needed. The agent authenticates through OAuth and always waits for approval before executing changes.

Do I need the GetSign app on monday.com?

Yes. MCP works against your monday account through GetSign, so the app must be installed on the account and you must approve monday access once. A monday account admin can install it from the install link above. After that, any user with a GetSign seat can connect their own agent.

Do I need an API key?

No. Authentication is OAuth. Your client sends you to a GetSign login page, you approve monday access, and the token stays with your client. There is no key, client ID, or secret to paste anywhere.

Which clients are supported?

Any MCP client that supports remote servers: ChatGPT, Cursor, Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Codex, and others. The installer link picks the right flow per client. The Connect your client section above has manual steps for each.

Can the agent send a document without me approving it?

Anything that changes data (sending a request, resetting a signing process, changing workflow settings) is marked as a mutating tool, and the server returns a confirmation step before the destructive ones run. Your MCP client also asks before each tool call unless you have explicitly allowed it.

Can it add a signer who is not on the board?

Signers come from existing monday columns: an Email, People, or mirrored email column on the board. If nobody has added a suitable column yet, the agent will tell you which one to create. Extra addresses can be copied on the email, but a copy recipient is not a signer.

Is there a self-hosted or local option?

The hosted server is the supported path for everyone. Developers building against their own GetSign backend can run the server locally over studio. See the GetSign MCP server repository on GitHub.

Is signing through an agent legally binding?

Yes. MCP is only a new way to drive the same GetSign signing engine. Signatures keep the same audit trail, tamper-evident sealing, and ESIGN/UETA/eIDAS compliance as signatures started from a monday board.

Continue with GetSign MCP

Connect your AI agent to GetSign.

No API keys. OAuth authentication. 27 tools. Works with Claude, ChatGPT, Cursor, VS Code, and any MCP client.

Connect GetSign MCP Set up manually

GetSign MCP for monday.com

Set up GetSign MCP in 3 simple steps

Install GetSign on monday.com

Add the MCP server

Authorize monday, then ask

GetSign MCP works with Claude, ChatGPT, Cursor and more

27 tools for documents and eSignatures on monday.com

Workflows and settings

Documents and fields

Send, track, collect

Generate, send and track documents from one chat

Create documents from board data

Send for signature and track progress

Build workflows for any document process

Use cases for sales, HR, legal and procurement

Contracts that close on schedule.

Onboarding that starts the day the deal closes.

Redlines and renewals, tracked end to end.

Offer letters without the chase.

Vendor agreements and POs that do not stall.

One governed layer instead of five stitched-together tools.

Whatever the document, just ask.

GetSign MCP FAQ

Start using GetSign MCP

1. Set up your client

2. Send your first document

3. Look up tools and recipes

Connect your AI agent to GetSign.