The AI -Native document workflow layer on monday.com

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

  • No API keys
  • Authorize monday once
  • 50+ agent tools
Set up in minutes. Powered by GetSign.

Set-up GetSign MCP in 3 simple steps

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

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

Install GetSign on monday.com

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

Add to monday.com
2

Add the MCP server

One link works for every client — it picks the right flow for Claude, Cursor, ChatGPT, VS Code, and the rest. Or follow the per-client steps below.

Open the installer
3

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.

See what to ask
Works with every MCP client

Connect your client

The installer above covers all of these. Use this section if you’d rather configure it by hand, or your client isn’t listed.

  1. Open Settings → Connectors → Create (developer mode / custom connectors must be enabled).
  2. Paste the MCP server URL and choose OAuth authentication:
    https://mcp.getsign.io/mcp
  3. Save, then connect and approve monday access.
  4. 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.

Built for how every team already works

One instruction. Any team.

GetSign Flow sits inside monday.com, so the same instruction model works wherever documents stall — sales, legal, HR, finance, or ops.

Sales & RevOps

Contracts that close on schedule.

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

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 — no copy-pasting between the CRM and a separate signing tool.

Customer Success & Onboarding

Onboarding that starts the day the deal closes.

“Send onboarding agreements to this week’s new accounts.”

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

Legal & Contract Ops

Redlines and renewals, tracked end to end.

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

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.

HR & People Ops

Offer letters and policy sign-off without the chase.

“Send the offer letter and handbook acknowledgment to this week’s new hires.”

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

Finance & Procurement

Vendor agreements and POs that don’t stall.

“Route this vendor agreement for approval, then send for signature.”

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.

Operations & Internal Builders

One governed layer instead of five stitched-together tools.

“Whenever a board status changes to Approved, send the linked document.”

GetSign replaces the Zap that breaks quietly in production with a workflow you can see — every send approved, every document tracked, filed where the record already lives.

Why jump between apps? Do it all in one chat.

Everything GetSign does on a monday board, an agent can now do in conversation — and 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, sign-anywhere, signed-file write-back — configured by describing what you want.

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

Questions

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; 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 has manual steps.
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’ve allowed it.
Can it add a signer who isn’t 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 stdio — see the GetSign MCP repository.
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.