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

GetSign in ChatGPT

No terminal, no config file. GetSign connects to ChatGPT as a custom connector: paste one URL, approve monday access once, and ask ChatGPT to send your contracts for signature.

Connect ChatGPTSend your first document
Server URL
https://mcp.getsign.io/mcp
Illustrative workflowMCP

ChatGPT + GetSign

Example prompt

“Who still needs to sign on board 123456789?”

  1. 1
    Add the connector

    Connect ChatGPT to GetSign MCP.

  2. 2
    Approve monday access

    Authorize the account you work with.

  3. 3
    Ask about your board

    Track signing progress from the conversation.

Your boards. Your documents. One chat.
Example workflow: not a live session or product screenshot.
Prerequisites

Before you start

Two things have to be true, and both are one-time.

GetSign is installed on your monday account

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

Add GetSign to monday.com

Your ChatGPT plan allows custom connectors

Adding your own MCP server needs custom connectors: available on ChatGPT’s paid plans, and on Business and Enterprise workspaces where an admin has enabled them. If you cannot see Connectors in settings, that is why.

Walkthrough

Add the connector

Four clicks and one paste.

Open Settings → Connectors

In ChatGPT, open your profile menu, then Settings, then Connectors. Choose Create (on some plans this sits behind Advanced → Developer mode).

Paste the GetSign server URL

Name it GetSign, paste the MCP server URL, and choose OAuth as the authentication method.

https://mcp.getsign.io/mcp

There is no API key, client ID or secret to fill in. GetSign MCP registers your client automatically over OAuth 2.1: leave those fields empty if ChatGPT offers them.

Connect, and approve monday access

Save the connector, then press Connect. A GetSign login window opens; sign in and approve monday access. That approval is what lets the agent read your boards and send signature requests on your behalf.

Turn GetSign on for the chat, then ask

Connectors are off by default in a new conversation. Open the composer’s tools menu and enable GetSign before asking about a board: otherwise ChatGPT will answer from general knowledge and never call a tool.

First run

Using GetSign, run a preflight check and then list the signing workflows on board 123456789.

Track

Using GetSign, who still needs to sign on board 123456789?

Troubleshooting

The three failures we actually see

All three look like GetSign is broken, and none of them is.

1  ChatGPT answers about your board without calling GetSign

The connector is connected but not enabled for that conversation. Enable GetSign in the composer’s tools menu, then ask again. Naming GetSign in the prompt: “using GetSign, …”: makes it pick the connector reliably.

2  The connector connects, but tools report you are not authorized

The OAuth round-trip did not finish, or it completed against a different monday account. Disconnect and reconnect the connector, and watch for the GetSign consent screen: approving monday access is a separate step from adding the connector.

3  ChatGPT refuses to send, or asks you to confirm twice

That is by design. Sending a signature request is a real email to a real recipient, so GetSign asks for confirmation before it goes out. Answer the confirmation and it sends. If you never see a confirmation prompt and the send silently stalls, say “confirm” and ChatGPT will retry with the confirmation attached.

One limitation worth knowing. ChatGPT cannot open a file from your computer into GetSign. Documents come from your monday board: a template in the GetSign gallery, or a file already in a board File column. If you need to upload a brand-new PDF from your laptop, do it from the board (or from a client with file access, such as Claude Code) and then drive the signing from ChatGPT.

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 guideClaude Code

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 review every available action in the tool reference.

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.