Claude Code

Plugin

The MCP server, plus the order the tools go in

The GetSign plugin installs the GetSign MCP server and six skills in one step. Each skill is a signing recipe your agent loads on its own when you ask for that task, so it follows the tool order GetSign’s API requires from the first message instead of working it out as it goes.

Install the plugin Set up Claude Code

Illustrative workflowMCP

The GetSign plugin

Example prompt

“Use the GetSign recipe to prepare and send an NDA.”

1
One installation
Connect the MCP server to your agent.
2
Six signing skills
Load the right recipe before the first tool call.
3
A guided workflow
Follow the tool order the API expects.

The server + signing skills, together.

Example workflow: not a live session or product screenshot.

Which one

Plugin or server on its own?

Same tools either way. The difference is whether your agent knows the order to call them in before it starts.

Server only

Your agent gets the GetSign tools and a short set of rules. For a multi-step task it reads the order from getsign_help mid-conversation, or learns it from the hints GetSign returns after each call. Works in every MCP client, including ChatGPT and Claude Desktop.

Plugin

The same server, plus six skills. When you say “send this for signature”, the agent loads the matching recipe first: which tool starts it, what it needs from you, and every step to the signed PDF. Available in Claude Code, Cursor and Codex.

Both at once is fine

If you already added the server by hand, installing the plugin does not give you a second copy: Claude Code merges MCP servers that point at the same URL. Keep the address exactly https://mcp.getsign.io/mcp.

6 skills

What each skill does

You don’t need to name a skill. Ask in your own words and the agent picks the one whose trigger phrases match. In Claude Code you can also run one directly, for example /getsign:send-new-document.

Skill	What it does	Say something like	Starts with
`send-new-document`	Sends a document that has no GetSign template yet: uploads it, attaches it to a signing workflow, maps the signature fields, points them at a signer column, sends, then tracks it to the signed copy. Steps	“Send this for signature” “Get this signed” “Send this NDA to the client to sign”	`getsign_create_template` Needs the file
`sign-from-file-column`	Sends a document that is already in a board File column, with no template: switches the workflow to Use stored document, points it at that column, then maps the fields on the item’s own file and sends. Steps	“Sign the file that's already on the item” “Use the document from the files column” “There's no template, the PDF is on the board”	`getsign_list_workflows_for_board` Needs a board
`create-or-update-workflow`	Creates a signing workflow on a board, or changes an existing one: sender identity and email, reminders, OTP, document generation, signature collection, share and track, or sourcing the document from a File column. Steps	“Create a GetSign workflow” “Change the workflow settings” “Update the sender email on this workflow”	`getsign_list_workflows_for_board` Needs a board
`board-pending-signatures`	Finds who still has not signed across a board, then drills into one item’s signing history and audit trail to see where it stalled and who to chase. Steps	“Who hasn't signed yet?” “Chase outstanding signatures” “Is the contract signed yet?”	`getsign_status` Needs a board, or a workflow and item
`save-signed-document-to-file-column`	Puts the signed PDF back on the board. First checks whether the workflow’s Signature collection or Generate document settings already do it automatically; if not, downloads the signed PDF and hands it to a connected monday.com tool to attach. Steps	“Save the signed document in the files column” “Attach the signed PDF to this item” “Put the signed contract back on the board”	`getsign_download_signed_documents` Needs a workflow and item
`install-getsign-on-new-account`	Sets GetSign up on a monday.com account for the first time: checks whether the app is installed, gives the account admin one link that covers both the install screen and authorization, confirms the connection, and adds a GetSign board view. Steps	“Set up GetSign” “Connect my monday account to GetSign” “GetSign isn't installed”	`getsign_account` Needs nothing: safe to run first

The server ships 14 recipes and the plugin turns 6 of them into skills: the ones people ask for most by name. The other 8 still work with the plugin installed: your agent reads them through getsign_help, and the tool reference lists them all.

Install

Add it to your client

The plugin wires up the server; it does not sign you in. On every client there is one more step to connect your monday.com account. A monday admin also needs to have installed GetSign on the account once.

Add the marketplace, install, and enable: all three inside Claude Code:

/plugin marketplace add Getsign-JP/getsign-mcp-plugin

/plugin install getsign@getsign

/plugin enable getsign@getsign

Then run /mcp, select plugin:getsign:getsign, choose Authenticate and approve monday access in the browser.

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. Full Claude Code walkthrough

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.

https://github.com/Getsign-JP/getsign-mcp-plugin

Cursor setup, including the server-only option

Add the marketplace and install: the plugin installs enabled.
Then connect your monday account with the third command.

codex plugin marketplace add Getsign-JP/getsign-mcp-plugin

codex plugin add getsign@getsign

codex mcp login getsign

Codex setup, including the server-only option

Contents

What's inside, and keeping it current

What the plugin contains

The MCP server address, the six skills, and a short reference of GetSign gotchas the skills point to. Nothing runs on your machine: no scripts, hooks or background agents. Every action still goes through the same server, with the same confirmation steps.

Updating in Claude Code

Refresh the marketplace with claude plugin marketplace update getsign, update with claude plugin update getsign@getsign, then restart Claude Code.

Updating in Codex

Refresh the marketplace snapshot with codex plugin marketplace upgrade getsign, then start a new session. Tool changes need no update on any client: the tools come from the server, so you get them the next time your client connects. Only skill changes ship in a plugin release.

Plugin FAQ

Questions

I use claude.ai, Claude Desktop or ChatGPT. Can I get the skills?

On claude.ai and the Claude apps, yes, GetSign is in Anthropic's plugin directory: open Settings → Plugins → Discover, search for "GetSign" and press Add. ChatGPT connects to the server only. You lose nothing in capability there: the same recipes are on the server, and your agent can read any of them with getsign_help(flow="send_new_document"). Asking it to "check the GetSign recipe first" before a multi-step task gets you most of the way there.

Do the skills cost context on every message?

Only a short description of each skill is loaded up front, so the agent can recognise when one applies. The full recipe loads only when a skill is used.

Is the plugin the same on all three clients?

Yes. It is one repository with a manifest for each client, and all three read the same six skills and connect to the same server.

Can I see exactly what a skill tells my agent?

Yes: each one is a plain Markdown file in the plugin repository, under skills/<name>/SKILL.md.

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

MCP guideChatGPT

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.

Install GetSign in Claude Code, or connect it as a custom connector in ChatGPT.

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.

Connect GetSign MCP Setup guide