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

GetSign MCP documentation

Use this hub to move from setup to a real signing workflow with GetSign MCP. Start by connecting your AI client, then send a first document, inspect the available tools, and choose the plugin path when your client supports guided skills.

Start with setupSend your first document
Illustrative workflowMCP

Your MCP learning path

Example prompt

“Help me send my first document with GetSign.”

  1. 1
    Set up your client

    Connect your preferred AI assistant.

  2. 2
    Follow the quickstart

    Prepare, review and send a document.

  3. 3
    Explore the reference

    Find the tools and recipes for your workflow.

Everything you need, in one place.
Example workflow: not a live session or product screenshot.
Guide library

Choose the MCP guide that matches your next step

Each guide covers one part of the GetSign MCP journey, from adding the server URL to sending a document and reading the underlying tool catalog.

Set up your AI client

Add the hosted GetSign MCP server to Claude Code, ChatGPT, Claude Desktop, Cursor, Codex, VS Code, or another MCP-compatible client. Start here if this is the first time the account is being connected.

Open setup guide

Send your first document

Use one connected client to prepare a document, review the signing plan, send through GetSign, and track the request until the signed PDF is ready.

Open quickstart

Understand tools and recipes

See every GetSign MCP tool, which ones write data, which ones are read-only, and how the recipes combine them into common document workflows.

Open tool reference

Use the plugin path

For Claude Code, Cursor, and Codex, the plugin adds skills so the agent can load the right GetSign recipe before it starts a signing workflow.

Open plugin guide
How to use these docs

Start with the job you want your AI agent to finish

The MCP docs are not meant to be read like a manual from top to bottom. Use them as a path: connect the client first, run one real signing workflow, then use the reference when you need exact tool behavior or a repeatable recipe.

If you are connecting an AI client

Open the setup guide first. It shows where the GetSign MCP server URL goes, how OAuth authorization works, and which client-specific page to follow for Claude Code or ChatGPT.

Open setup

If you want proof it works

Use the quickstart. It follows one signing request from prompt to signed PDF, including the review point before anything is sent from GetSign.

Follow quickstart

If you are planning workflows

Use the tool reference and plugin guide. They explain the available actions, the order they run in, and when a plugin with skills helps an agent follow a repeatable signing recipe.

View reference

A good review flow is: setup guide, quickstart, tool reference, then plugin guide if your team uses Claude Code, Cursor, or Codex.

Recommended path

From connection to a working signing flow

This is the practical order for testing GetSign MCP before you move the pages to staging or share them with a team member.

1

Connect the AI client

Add the GetSign MCP server to the client your team uses and complete the monday.com OAuth approval. No API key or local server is required.

Setup guides
2

Run one real document flow

Ask the agent to prepare a document for signature, review the plan, approve the send, and confirm that GetSign can track the signing status.

Quickstart
3

Use the reference when you need precision

When you need to explain a tool, debug a flow, or build a prompt for a recurring job, the tool and recipe reference shows what the server exposes and what changes data.

Tool reference

Keep users inside the MCP pages while they are learning: the setup, quickstart, tools, and plugin guides now link to one another and end with the same connection CTA.

Which page answers what?

Use the right guide for the question in front of you

Each page has a different job. The docs index now gives enough context for a visitor to choose the next page without already knowing MCP terminology.

Setup guide

Best for a new user who needs the server URL, supported client choices, and the first authorization step. It points to Claude Code and ChatGPT walkthroughs when those paths need more detail.

Open setup

Quickstart

Best for validating the first end-to-end signing flow. It shows how the agent prepares the document, asks for approval, sends through GetSign, and follows the result.

Open quickstart

Tool reference

Best for operators, builders, and support. It explains read tools, write tools, confirmation steps, and the recipes that combine tools into complete signing jobs.

Open tools

Plugin guide

Best for clients that support plugins and skills. It explains why the plugin helps an agent load the right signing recipe before it starts calling tools.

Open plugin guide

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 guideChatGPT

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.

Connect another client with the setup guide, or send a first document with the quickstart.

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.