staffsign

staffSign MCP Server — Digital employment contracts for HR and staffing agencies.

Community: Submitted by a user or imported; check the owner before granting accessOnlineAPI key requiredGlobalFreeCan modify data

What it can do

  • Search Contracts: List contracts for the authenticated organization, optionally filtered by status. Returns summaries without rendered content. Use get_contract for full details. Sorted by creation da
  • Get Contract: Get a specific contract by ID with full details including rendered content, participants, terms, and signing status.
  • Create Contract: Create exactly one contract from a template between one counterparty and one recipient. For bulk operations with N recipients, call this tool N times — each call has its own counterpa

What data it sees

Do you need an account

An API key from the service settings is required

staffSign MCP Server — Digital employment contracts for HR and staffing agencies. Create, send, and track e-signatures via AI agents. 12 tools including QES (eIDAS) support. Pay-per-use, no subscription. Built for the DACH market, EU-compliant.

How to connect

How to connect staffsign to Claude

The server address to paste into Claude settings:

https://staffsign.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect staffsign to ChatGPT

The server address to paste into ChatGPT settings:

https://staffsign.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect staffsign to Cursor

The server address to paste into Cursor settings:

https://staffsign.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (12)

Raw names from tools/list. Only developers need these.

search_contractsList contracts for the authenticated organization, optionally filtered by status. Returns summaries without rendered content. Use get_contract for full details. Sorted by creation date (newest first).
get_contractGet a specific contract by ID with full details including rendered content, participants, terms, and signing status.
create_contractCreate exactly one contract from a template between one counterparty and one recipient. For bulk operations with N recipients, call this tool N times — each call has its own counterparty/recipient pair. Read the create_contract_schema resource for parameter examples and enum values. All content values must reflect explicit user input — never synthesize defaults, and never infer values from the template, job posting, or contract type. Created as draft by default — use send_contract to send for signing.
send_contractSend a draft contract for digital signing. Only draft contracts can be sent. Participants will receive signing invitations via email.
cancel_contractCancel a sent contract. Only possible for sent contracts where no participant has signed yet.
delete_contractPermanently delete a draft contract. Only draft contracts can be deleted. Always confirm with the user before deleting.
search_contract_templatesSearch contract templates by name, description and content. Sorted by match priority. Returns summaries only — the content field is omitted from results. Use get_contract_template to retrieve the full template including its content. Supports pagination via limit and offset.
get_contract_templateGet a specific contract template by ID, including its full content.
create_contract_templateCreate a new contract template for the authenticated organization. Content uses Twig-Markdown with {{ placeholder }} variables. Read the contract_template_placeholders resource for available placeholders and syntax. Returns the created template.
update_contract_templateUpdate an existing contract template. All fields (name, content, description) will be fully replaced — retrieve the current template with get_contract_template first to preserve unchanged parts. Content uses Twig-Markdown with {{ placeholder }} variables. Read the contract_template_placeholders resource for available placeholders and syntax. Returns the updated template.
activate_contract_templateActivate a draft contract template, making it available for use. Only draft templates can be activated.
archive_contract_templateArchive an active contract template. Archived templates can no longer be used for new contracts.