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.
Your AI client + GetSign
“Send the agreement for this monday.com item.”
- 1Connect your AI client
Add the GetSign MCP server URL.
- 2Authorize once
Approve access to your monday.com account.
- 3Describe your task
Review the plan before anything is sent.
The three steps, whatever your client
Every client below follows the same three steps. Only the middle one differs.
https://mcp.getsign.io/mcpInstall 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.comAdd 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 clientAuthorize 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 taskIn 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.
Choose your client
Claude Code and ChatGPT have step-by-step pages covering the failures we actually see. The rest take one of the two config shapes below.

Claude Code Guide
Install the GetSign plugin, or add the server with one claude mcp add command. Signing recipes ship as skills.

ChatGPT Guide
Add GetSign as a custom connector in Settings, choose OAuth, and enable it in the composer.
Read the guide →
Claude Desktop
Settings → Connectors → Add custom connector, then paste the server URL.
See the steps →Cursor
Install the GetSign plugin from our GitHub repo, or add the server with a one-click deeplink.
See the steps →
Codex
Install the GetSign plugin from our GitHub repo with two commands, or add the server with codex mcp add.
VS Code
One-click install, the MCP: Add Server command, or a .vscode/mcp.json entry.
Windsurf
Remote MCP server with OAuth: uses the standard mcpServers config shape.
Zed
Add GetSign as a context server pointing at the hosted URL.
See the steps →Goose
Add a remote extension with the hosted URL; Goose handles the OAuth round-trip.
See the steps →Warp
Add an MCP server in Warp's settings using the standard JSON shape.
See the steps →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.
- Open Settings → Plugins → Discover, search for GetSign and press Add.
- 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:
- 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.
Cursor
Recommended: install the plugin. The same plugin Claude Code installs. It adds the MCP server and GetSign’s signing recipes as skills, so the agent follows the right tool order from the first message instead of discovering it mid-task.
- Open Dashboard → Plugins → Add Marketplace → Import from Repo and paste the repo below.
- Install GetSign from Customize → Plugins.
- Finish monday authorization from the MCP list: the plugin wires up the server, but it does not connect your monday account.
https://github.com/Getsign-JP/getsign-mcp-pluginOr add it by hand: Settings → MCP → New MCP server:
{
"mcpServers": {
"getsign": {
"url": "https://mcp.getsign.io/mcp"
}
}
}After it appears in the MCP list, click Needs login or the server name to finish monday authorization.
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.
Codex
Recommended: install the plugin. The same plugin Claude Code and Cursor install. It adds the MCP server and GetSign’s signing recipes as skills, so the agent follows the right tool order from the first message instead of discovering it mid-task.
- Add the GetSign marketplace.
- Install the plugin: it installs enabled, no extra step.
- Connect your monday account: the plugin registers the server, but it does not sign you in.
codex plugin marketplace add Getsign-JP/getsign-mcp-plugincodex plugin add getsign@getsigncodex mcp login getsignWant the tools without the skills? Add the server on its own, then run the same codex mcp login getsign:
codex mcp add getsign --url https://mcp.getsign.io/mcp
codex mcp list should show getsign at https://mcp.getsign.io/mcp, enabled.
Windsurf, Zed, Goose, Warp: and any other MCP client
Any MCP client that supports remote servers with OAuth works. Point it at the server URL below.
https://mcp.getsign.io/mcpMost clients take this JSON shape; clients that ask for an explicit transport want http (Streamable HTTP):
{
"mcpServers": {
"getsign": {
"url": "https://mcp.getsign.io/mcp"
}
}
}
{
"servers": {
"getsign": {
"type": "http",
"url": "https://mcp.getsign.io/mcp"
}
}
}If something goes wrong
Three things account for nearly every failed setup.
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.
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.
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.
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.
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 guideChatGPTConnect 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 guideQuickstartWalk 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 referenceUse 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 guideInstall 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.
Explore the MCP documentation when you need details, or open the plugin guide when you want the server and signing skills together.
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.