Reference

Every GetSign action, as a typed tool

GetSign MCP exposes every GetSign action as a typed tool, so your agent knows a tool’s arguments before it calls it. Read tools are always safe; tools marked writes change data, and the riskiest of them take a confirmation step before they run.

Explore the tools See the quickstart

Server URL

https://mcp.getsign.io/mcp

Your agent can read this reference in conversation instead of loading the page: ask it to call getsign_help for a guide, or getsign_help(flow="send_new_document") for one of the recipes below.

Illustrative workflowMCP

GetSign tool reference

Example prompt

“Show me the recipe for sending a new document.”

1
Discover
Read the available tools and workflow recipes.
2
Prepare
Configure the document and its signing fields.
3
Act with approval
Send, track and collect the signed document.

27 tools. Connected by clear recipes.

Example workflow: not a live session or product screenshot.

27 tools

The catalog

27 of the 31 tools the server defines are on tools/list by default, grouped below by what they act on. There is no free-text API to get wrong.

Resource	Tool	Description
Discovery	`getsign_help`	Read a GetSign agent guide or named flow recipe (index, search, or markdown)
	`getsign_account`	Check GetSign auth and monday-app install state (preflight, status, or install_state)
	`getsign_manage_tools`	Turn rarely-used GetSign tools on or off for this session
	`getsign_report_issue`	File a bug or support report from a failing tool result and get back a reference for the user
Setup & connection	`getsign_connect`	Open a secure GetSign login, or install the monday app then log in
	`getsign_monday_item`	Fetch a monday item or the first item on a board, including signer / status / file column lists for assign and generate settings
	`getsign_ensure_board_view`writes	Ensure a GetSign board view tab exists on a monday board and return its link
Workflows	`getsign_create_workflow`writes	Create a signing workflow on a monday board
	`getsign_update_workflow_settings`writes	Configure document generation, signature collection, reminders, OTP, sign-anywhere, email delivery, and email logo attach/remove
	`getsign_set_workflow_email_logo`writesoff by default	Request a presigned PUT URL to upload a workflow email logo; attach the key with update
	`getsign_get_workflow`	Fetch GetSign workflow settings, including a short-lived logo_preview_url when a logo is set
	`getsign_list_workflows_for_board`	List GetSign workflows configured on a monday board
Documents & fields	`getsign_generate_documents`writes	Generate documents for a GetSign workflow and monday item (waits until done by default)
	`getsign_list_envelope_documents`	List the documents attached to a workflow item: the ones that would be sent for signing
	`getsign_delete_envelope_document`writes	Remove a document or pinned template file from a workflow/envelope
	`getsign_validate_document_placeholders`writes	Check a document’s `{columnId}` merge tokens against the board’s columns, and rewrite unmatched ones in a DOCX once you confirm
	`getsign_detect_placeholders_ai`writes	Run AI placeholder detection on a PDF file to auto-find signature fields, initials, sign dates, text boxes, and checkboxes
	`getsign_save_document_configuration`writes	Save AI-detected fields or sequential signing order onto an item document or gallery template
	`getsign_get_document_url`	Get an item-document or gallery-template link with required `action="edit"` or `action="preview"`
Templates	`getsign_list_template_gallery`	Search the reusable template library
	`getsign_select_template_for_workflow`writes	Attach an existing template gallery template to a GetSign workflow
	`getsign_duplicate_template_for_workflow`writesoff by default	Duplicate a template into a GetSign workflow so the copy can be customized
	`getsign_create_template`writes	Register a PDF/DOC/DOCX as a template gallery entry: two calls: request a presigned upload URL, PUT the file, then register the stored key
Sending & signing	`getsign_send_signature_request`writes	Send a signature request email for a GetSign workflow on a monday item
	`getsign_cancel_signature_request`writes	Cancel an active GetSign signature request for a workflow item
	`getsign_get_signer_data`	Resolve signers who must sign and copy_recipients who only get a copy
	`getsign_generate_signing_link`writes	Generate a shareable signing link for a workflow item
	`getsign_reset_signing_process`writesoff by default	Reset signing status for a workflow item so it can be prepared again
	`getsign_start_sign_by_me`writesoff by default	Start a sign-by-me flow for the current user on a workflow item
Tracking & audit	`getsign_status`	Check signing progress: item history, board sessions, activity log, or who still needs to sign
Tracking & audit	`getsign_download_signed_documents`	Get short-lived download links for the final signed PDFs

Tools marked off by default are hidden from the initial tool list to keep your agent’s context small: it turns them on for the session with getsign_manage_tools when it needs one. We recommend keeping your client’s human confirmation on for write tools, and exercising caution when combining GetSign MCP with untrusted servers to avoid prompt-injection attacks.

14 recipes

The order the tools go in

Most signing tasks are a sequence, not a single call. These are the recipes the server ships to agents: the same ones getsign_help(flow=…) returns in conversation. Six of them also ship as skills in the GetSign plugin.

`send_new_document`

Send a document that has no GetSign template yet: upload it, attach it to a workflow, map the signature fields, point them at a signer column, send, and track through to the signed copy.

getsign_create_template
getsign_validate_document_placeholders
getsign_list_workflows_for_board
getsign_ensure_board_view
getsign_create_workflow
getsign_get_document_url
getsign_get_signer_data
getsign_save_document_configuration
getsign_send_signature_request
getsign_status
getsign_download_signed_documents

`sign_from_file_column`

Send a document that already sits in a board File column, with no template: switch the workflow to "use stored document", point it at that column, map the fields on the item’s own file, send.

getsign_list_workflows_for_board
getsign_monday_item
getsign_update_workflow_settings
getsign_list_envelope_documents
getsign_detect_placeholders_ai
getsign_save_document_configuration
getsign_get_document_url
getsign_send_signature_request
getsign_status

`create_or_update_workflow`

Create a signing workflow on a board, or change an existing one: sender identity and email, reminders, OTP, document generation, signature collection, share and track, or sourcing the document from a File column.

getsign_list_workflows_for_board
getsign_ensure_board_view
getsign_create_workflow
getsign_get_workflow
getsign_monday_item
getsign_update_workflow_settings

`install_getsign_on_new_account`

Set GetSign up on a monday account for the first time: check whether the app is installed, hand the admin one link covering both the install screen and OAuth consent, confirm it works, add a board view.

getsign_account
getsign_connect
getsign_account
getsign_list_workflows_for_board
getsign_ensure_board_view
getsign_create_workflow

`ai_detect_and_assign`

Find the signature pads, initials, dates, text boxes and checkboxes with AI, then assign each one to a board email column and save. Detection alone persists nothing: the save step is what commits it.

getsign_detect_placeholders_ai
getsign_monday_item
getsign_save_document_configuration
getsign_get_document_url
getsign_send_signature_request

`generate_and_send`

Generate item-specific documents from a workflow’s templates: merged with the board’s own column values: and then send them for signing.

getsign_get_workflow
getsign_get_signer_data
getsign_save_document_configuration
getsign_get_document_url
getsign_generate_documents
getsign_send_signature_request
getsign_status

`board_pending_signatures`

Find who still has not signed across a whole board, then drill into one item’s history and audit trail to see where it stalled and who to chase.

getsign_status

`download_after_completion`

Confirm an item is fully signed and collect the sealed PDF, with its audit trail.

getsign_status
getsign_download_signed_documents

`save_signed_document_to_file_column`

Get the signed PDF back onto the board. Signature collection writes it to a File column automatically on completion; this recipe covers the case where that was never switched on.

getsign_download_signed_documents

`edit_document_map_fields`

Open a document in the PDF editor to place signature and signer fields by hand, then review them before sending.

getsign_list_envelope_documents
getsign_get_document_url
getsign_get_signer_data

`template_picker`

Browse the reusable template gallery, attach one to a workflow, and duplicate it when this board needs its own customized copy.

getsign_list_template_gallery
getsign_select_template_for_workflow
getsign_validate_document_placeholders
getsign_duplicate_template_for_workflow

`preview_before_sending`

See exactly what the signer will see, before anything is emailed.

getsign_get_document_url
getsign_send_signature_request

`ensure_board_view`

Add the GetSign tab to a monday board so signing status is visible where the work already happens. Needs only a board ID, and is safe to run more than once.

getsign_ensure_board_view

`setup_no_ui_assistant`

Stand up a working signing workflow on a board entirely in conversation, without opening GetSign at all.

getsign_account
getsign_list_workflows_for_board
getsign_ensure_board_view
getsign_create_workflow
getsign_update_workflow_settings
getsign_send_signature_request

Safety

How writes are gated

Two confirmation layers, plus one hard limit: each independent of the others.

Your client asks first

Every MCP client prompts before a tool call unless you have allowlisted that tool. That is the layer you control, and we recommend leaving it on for anything marked writes.

GetSign asks again for the risky ones

Sending a signature request, cancelling one, resetting a signing process, deleting a document and generating a signing link each take a confirmation step on the server, no matter what your client allows.

Signers are never invented

An agent can only point a signature field at an email, people or mirrored-email column that already exists on your board. It cannot type in an arbitrary address and make that person a signer.

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 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.

Put the tools into practice with the quickstart, or add guided signing recipes with the plugin guide.

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