Yes. The SignWith MCP server is at app.signwith.co/mcp. It works with Claude, ChatGPT, Cursor, VS Code and any client that supports remote MCP servers over Streamable HTTP.
MCP server
Send documents for signature from Claude, ChatGPT or Cursor
The SignWith MCP server connects your AI assistant to your SignWith account. Ask it to draft a contract, add the signature fields, send it with email verification and tell you who has signed. It checks with you before anything goes out.
- Secure OAuth sign-in, no API key
- Asks before it sends
- Same pay-per-doc credits
Draft a consulting agreement for Jordan Ellis and send it to jordan@example.com. Turn on email verification.
SignWith create_template Consulting-Agreement.pdf
I drafted the agreement and added these fields for Jordan:
SignatureDateFull nameInitialsI agree checkbox
Claude wants to use send_signature_request from SignWith
To jordan@example.com · email OTP onAllow onceAlways allowDenySent. Jordan must enter a code from his email before he can open it.
Has Jordan signed yet?
SignWith get_signature_request
- Email sent 10:02
- Viewed the document 10:14
- Not signed yet
Want me to send him a reminder?
Reply to Claude…
Connect
Set up SignWith in your assistant
Pick your assistant, add SignWith, then sign in to SignWith to approve the connection.
Claude
A custom connector on the web or desktop app. It then works on mobile too.
Claude setup guideChatGPT
An app in developer mode, on ChatGPT Plus, Pro, Business, Enterprise or Education on the web.
Open the ChatGPT guideChatGPT setup guideCursor
One click installs SignWith in Cursor. Then sign in when Cursor asks.
Cursor setup guideVS Code
One click adds SignWith to GitHub Copilot agent mode in VS Code.
VS Code setup guideClaude Code
Run one command in your terminal.
claude mcp add --transport http \ signwith https://app.signwith.co/mcpClaude Code guideAny other MCP client
Use the server URL over Streamable HTTP. Sign in with OAuth, or send an API key as a Bearer token.
https://app.signwith.co/mcpMCP overview
How it works
Connected in under a minute
No API key to copy and nothing to install on your computer.
- Add custom connectorName SignWithURL app.signwith.co/mcpAdd1
Add SignWith
One click for Claude, Cursor or VS Code. For other clients, paste the server URL.
- SignWith · Authorize Claude Full access View onlyApprove2
Approve in SignWith
Sign in to SignWith and choose Full access, or View only to let it look but never send.
Send the NDA template to jordan@example.com
send_signature_requestSent. Jordan has the signing link.
3Ask in plain language
Your assistant picks the right SignWith tool and shows you what it is about to do.
Just ask
Type the request in your own words. Your assistant picks the right SignWith tool. See all 18 tools.
- > Draft an NDA and send it to jordan@example.com with OTP on
- > Which documents are still waiting for a signature?
- > Remind everyone who has not signed the office lease
- > Has Maya signed the offer letter yet?
- > Is this PDF really signed with SignWith?
- > Send the consulting agreement to the client first, then to me
- > Cancel the lease I sent to the wrong person
- > Turn this contract into a template with signature and date fields
- > How many credits do I have left?
- > Fix Jordan’s email address and resend his signing link
- > Duplicate my NDA template for a new client
- > Send the W-9 to alex@example.com and just give me the link
- > Which credit pack is cheapest per document?
- > Archive the templates I no longer use
What it can do
Everything you do in SignWith, from a chat
Draft and prepare
Turn a contract your assistant wrote, or a PDF you share, into a template with signature, date and text fields.
Send for signature
Send to one signer or several, in order or all at once, with email OTP when it matters.
Track every document
Ask what is waiting, who has opened it and who has signed.
Remind signers
Resend the signing email to everyone whose turn it is, or fix a signer’s email and resend.
Verify signed PDFs
Check that a PDF was completed in SignWith and has not been changed since.
Check your credits
See your balance and get a checkout link when you need more. You always pay in your browser.
All 18 tools
You stay in control
Nothing goes out without your say
Cancel the lease I sent to the wrong person
Claude wants to use cancel_signature_request from SignWith
Office-Lease-Renewal · cannot be undoneAllow onceAlways allowDenySending, reminding, canceling and archiving always ask first
Security
A secure connection between your assistant and SignWith
The SignWith MCP server follows the MCP authorization standard. Your assistant gets a short-lived, limited token, never your password.
Sign in with OAuth 2.1
Your assistant sends you to SignWith to sign in and approve. It uses OAuth 2.1 with PKCE, so no password or API key is pasted into a chat.
Short-lived tokens
Access tokens expire after 1 hour. Refresh tokens are replaced every time they are used and expire after 60 days.
Locked to the SignWith MCP server
Tokens are bound to app.signwith.co/mcp. They cannot be used to call the REST API or any other service.
Only what you can see
The connection acts as your SignWith login, so your assistant only sees the templates and documents your account can see.
The same rules as the API
Every tool call runs through the SignWith API with the same validation, credits and a limit of 300 requests a minute per connection.
Revoke access in one click
Disconnect any assistant under Settings → Connected apps. Its tokens stop working.
OAuth and protocol reference
Security and proof
Every signed document comes with proof
Check who is signing, keep a full record of what happened, and show anyone that the document has not changed since.
Verify your email to access this documentFreelance-Services-Agreement · code sent to c***@example.com
284517
Verify Email verified. Opening documentFree to connect, pay per signed document
Documents sent from your assistant use the same credits as the SignWith app. There is no AI fee and no plan.
- 3documents free every month
- $0.58per signed document, from
- $0monthly fee or plan
FAQ
team@signwith.co Frequently asked questions
Still unsure? Email us and a real person will help.
Yes. Add SignWith as an app in ChatGPT developer mode, sign in to SignWith, and ask ChatGPT to send a document. The ChatGPT setup guide has every step.
Sending, reminding, canceling and archiving are marked as actions to confirm, and most clients, including Claude and ChatGPT, ask you first unless you have chosen to always allow them. A View only connection cannot send anything.
Yes. Assistants connect with OAuth 2.1 and PKCE, so you sign in on SignWith and no password or API key is shared. Access tokens last 1 hour and only work on the SignWith MCP server. You choose Full access or View only, and you can disconnect any assistant under Settings → Connected apps.
It sees what your own SignWith login can see, and nothing more. With a View only connection it can read and verify, but it cannot send, change or cancel anything.
No. Claude and ChatGPT send you to SignWith to sign in and approve the connection. Clients that only take headers can use an API key instead.
Yes. When an assistant writes a document for you, it places the signature, date and other fields with text tags, then turns it into a SignWith template ready to send.
The MCP server is free to connect. Documents use the same credits as the SignWith app: 3 free every month, then one credit per signed document. There is no monthly fee.
Connect SignWith to your assistant
Create a free account, add the connector, and send your first document from a chat. 3 documents are free every month.
Create a free accountYour signers do not need an account.