Use Sign from Claude, ChatGPT and other assistants

Connect Tyms Sign and ask your assistant to send an agreement for signature, chase whoever hasn't signed, or find a signed copy. People still sign themselves, on any phone. It works on the same envelopes your team sees in the browser, as you.

The address

Add this address to your assistant as a connector (also called an MCP server). It's the same for everyone:

https://sign.tyms.ai/mcp

The first time your assistant connects, you sign in with your Tyms account and choose the workspace it works in. No account yet? Get started for free; an owner or admin switches Sign on for your organisation in one click.

Set it up

Claude

In Claude (web or desktop), open Settings → Connectors and choose Add custom connector.
Name it Tyms Sign and paste the address as the URL.
Select Connect, sign in with your Tyms account and choose your workspace.
In a chat, turn on Tyms Sign from the tools menu and ask it to send a document for signature or who still has to sign.

On Claude Team or Enterprise, an owner may need to add the connector for the organisation first; then each person selects Connect.

ChatGPT

In ChatGPT, open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
Back in Apps & Connectors, choose Create. Name it Tyms Sign, paste the address and pick OAuth.
Sign in with your Tyms account and choose your workspace.
In a chat, add Tyms Sign from the tools menu.

Custom connectors need a paid ChatGPT plan; on Business plans an admin may need to allow them.

Claude Code

Run claude mcp add --transport http tyms-sign https://sign.tyms.ai/mcp in your terminal.
In Claude Code, run /mcp, choose tyms-sign and sign in.

Cursor

Open Cursor Settings → MCP → Add new MCP server.
Paste the address. Cursor asks you to sign in the first time it uses Sign.

VS Code

Run MCP: Add Server from the command palette, choose HTTP and paste the address.
Use it from Copilot Chat in agent mode; VS Code asks you to sign in the first time.

Other assistants

Any assistant that supports remote MCP servers over HTTP with OAuth can connect: add a server with the address and sign in when asked.

Assistant menus change from time to time; if a step doesn't match what you see, look for “connectors”, “apps” or “MCP” in its settings.

Try asking

“Send the offer letter template to jane@example.com, with Allan to countersign.”
“Who hasn't signed the contractor agreements yet?”
“Remind everyone who still has to sign the supplier NDA.”
“Find the signed copy of the Acme agreement.”

Assistants that offer prompts also list ready-made ones, such as sending from a template and chasing signatures.

What it can do

It acts as you. It sees the envelopes you can see and can do what you can do in Sign, nothing more.
It prepares and sends. From a template, with the people and order you name and the values you give it, or from a document with its fields.
It chases. Who still has to sign, who opened it, what's about to expire, and a reminder to whoever is next.
It never signs for anyone. No tool signs, approves or declines, and none files a document to Organization Intelligence. Each signer does that themselves.
Everything is in the audit trail. What it does is recorded with your name and marked “via Claude” (or your assistant's name), in the envelope's tamper-evident history and on its certificate of completion.
Same price as the browser. Envelopes it sends count towards your workspace's 25 completed free a month, then $0.50 each.

Tools

What your assistant may call. Read-only access offers only the tools that read.

Tool	What it does	Kind
`list_envelopes`	Lists envelopes you can see: waiting for you, waiting for others, completed, declined, voided or expired; narrows by words or status.	Reads
`get_envelope`	Shows one envelope: its documents, who signs in what order, where each person is, and its history.	Reads
`list_templates`	Lists your templates with their roles and the fields the sender fills in.	Reads
`get_signed_document`	Gives a link to the sealed PDF and its certificate of completion.	Reads
`send_for_signature`	Sends an envelope from a template or a document, to the people and in the order you name.	Changes
`remind_signers`	Emails a reminder to everyone who still has to sign or approve.	Changes
`void_envelope`	Voids an envelope with a reason; everyone already emailed is told.	Changes

Privacy and control

See and disconnect. Every assistant you've allowed, in which workspace and when it was last used, is on Connected apps. Disconnecting ends its access within the hour.
Admins decide. Owners and admins can turn assistants off for the whole workspace in Tyms Admin, which disconnects every assistant there at once. Someone removed from a workspace loses their assistants' access with it.
No conversations kept. Sign records which assistant called which tool and what changed, never the text of your chats.
Secure sign-in. Assistants sign in through auth.tyms.ai with OAuth; they never see your password, and their access expires and renews on its own.

Read the privacy policy and terms.

Questions

Which workspace does my assistant use?

The one you choose when you connect. Everyone uses the same address; after you sign in, Tyms lists your workspaces that have Sign switched on and you pick one. To switch, disconnect it in Connected apps and connect again. To connect one workspace only, without being asked, use its own address: your-team.sign.tyms.ai/mcp.

Can my assistant sign or approve for me?

No. No tool signs, approves or declines for anyone, and no tool files a document to Organization Intelligence: those are each signer's own acts, in the browser. Your assistant can prepare and send envelopes from your templates, chase people who haven't signed, and void an envelope you ask it to.

It says AI assistants are turned off for this workspace.

An owner or admin of the workspace has turned assistants off in Tyms Admin. Ask them to turn “Allow AI assistants to connect” back on.

It says Sign is switched off, or offers no workspace.

Sign isn't on for your workspace yet. An owner or admin can switch it on for free at sign.tyms.ai. If you don't have a Tyms account, get started there with your work email.

Does my assistant cost extra?

No. Sign is billed the same way whoever sends: the first 25 envelopes completed each month are free per workspace, then $0.50 per envelope. Drafts and envelopes that are declined, voided or expire are never charged.

What does Tyms keep about my conversations?

Nothing from them. Sign records which assistant called which tool, in which workspace, and what it changed, in the envelope's audit trail like everyone else's actions. It never sees or stores the text of your chats.

Still stuck?

Email support@tyms.ai with the assistant you're using and what it said. We'll help you get connected.