Team Signatures
Connect your AI assistant to SyncSignature (MCP)
The SyncSignature MCP server lets an AI assistant work on your SyncSignature workspace for you. You sign in once, and then you can ask it to find teammates with missing details, add people to groups, schedule banner campaigns and read click analytics in plain English.
Server URL:
https://mcp.syncsignature.com/mcp
Before you start
- A SyncSignature Teams workspace. The MCP server works on an existing workspace. If you don't have one, start the 7-day trial at syncsignature.com. No card is needed.
- The right role for what you want to change. Any teammate can connect and look things up. Editing templates, groups and banner campaigns needs the Owner or Manager role, the same as in the dashboard. See Manager vs teammate.
- An assistant that supports remote MCP servers with OAuth. The five below are covered step by step. More are on the AI assistants page.
Connect your assistant
Every assistant follows the same three steps: add the server URL, sign in to SyncSignature, then ask in plain English.
Claude
- Go to Customize, then Connectors, click + Add, choose Add custom connector, and paste
https://mcp.syncsignature.com/mcp. On Team and Enterprise plans, an owner adds it under Organization settings, then Connectors, and members click Connect. - Click Connect. If Claude asks how to register, choose Register automatically. A SyncSignature sign-in page opens: sign in with your SyncSignature account, choose the workspace to connect, and click Allow.
- Ask in plain English, for example: "Using SyncSignature, list the teammates in my workspace who are missing a job title."
More detail: Manage email signatures with Claude.
ChatGPT
- Open ChatGPT Plugins, click the + button, choose Add custom MCP server, and enter
https://mcp.syncsignature.com/mcp. Confirm, select Create as a plugin, then install it. - A SyncSignature sign-in page opens. Sign in, choose the workspace to connect, and click Allow.
- Ask in plain English.
More detail: Manage email signatures with ChatGPT.
Claude Code
-
Run this in your terminal:
claude mcp add --transport http syncsignature https://mcp.syncsignature.com/mcp -
In Claude Code, run
/mcp, pick syncsignature, and follow the steps in your browser. Sign in with your SyncSignature account, choose the workspace to connect, and click Allow. -
Ask in plain English.
More detail: Manage email signatures from Claude Code.
Cursor
-
Create or edit
.cursor/mcp.json(project) or~/.cursor/mcp.json(global) and add:{"mcpServers":{"syncsignature":{"url":"https://mcp.syncsignature.com/mcp"}}} -
When Cursor prompts you to authenticate, a SyncSignature sign-in page opens. Sign in with your SyncSignature account, choose the workspace to connect, and click Allow.
-
Ask in plain English.
More detail: Manage email signatures from Cursor.
VS Code
-
Create or edit
.vscode/mcp.jsonin your project and add:{"servers":{"syncsignature":{"type":"http","url":"https://mcp.syncsignature.com/mcp"}}} -
Start the server from the file or from the MCP servers list. When VS Code asks to authenticate, a SyncSignature sign-in page opens. Sign in, choose the workspace to connect, and click Allow.
-
Ask in plain English in Copilot Chat's agent mode.
Sign-in and access
- One workspace per connection. You choose the workspace on the sign-in page. To work on a second workspace, add a second connection.
- Read, or read and write. On the sign-in page you choose whether the assistant can only look things up, or can also make changes. A read-only connection answers questions but cannot change anything.
- It acts as you. The assistant can do what your SyncSignature account can do in the dashboard, no more. If your role cannot edit templates, neither can the assistant.
- No API key. Sign-in uses OAuth, so there is no key to copy, paste or store.
Tools
The server exposes 31 tools in three groups. Assistants pick the right tool from your request, so you never need to name one.
Read (14)
These only look things up and never change anything.
| Tool | What it does |
|---|---|
get_workspace |
The connected workspace: name, domain, seat usage and teammate count |
list_teammates |
Every teammate with their signature details, so it can spot missing job titles or phone numbers |
get_teammate |
One teammate's full record |
get_teammate_signature |
A teammate's current signature and whether it is installed |
get_teammate_analytics |
Clicks on a teammate's signature links by country, browser, OS and device, for an optional date range |
list_groups |
Every group, its template and its teammate count |
list_workspace_templates |
The signature templates in your workspace |
get_workspace_template |
One workspace template's fields and design |
list_signature_templates |
The SyncSignature template catalog |
preview_signature |
Renders a catalog template with a person's details, without saving anything |
list_smart_fields |
Every signature field, what it is bound to (a directory, a CSV or nothing), and whether it is required |
list_campaigns |
Banner campaigns, with status and dates |
list_signature_links |
The tracked links inside a teammate's signature |
list_integrations |
Connected integrations and whether their credentials have expired |
Add (3)
These create something new without changing or removing anything that exists.
| Tool | What it does |
|---|---|
create_teammate |
Adds a teammate |
create_group |
Creates a group with a template |
create_smart_field |
Adds a custom smart field |
Change, overwrite or remove (14)
These change existing data, overwrite live signatures or remove something, so they are marked destructive and assistants ask before running them. Changing a teammate's details or putting them in a group rebuilds their live signature, and campaign tools change the banner people see in their signatures.
| Tool | What it does |
|---|---|
update_teammate |
Changes a teammate's details, such as job title or phone |
add_teammates_to_group |
Puts teammates in a group, which gives them that group's signature |
create_campaign |
Schedules a banner campaign for chosen groups and dates |
update_campaign |
Changes a campaign's banner, link, groups or dates |
pause_campaign |
Pauses a running campaign |
resume_campaign |
Resumes a paused campaign |
update_workspace_template |
Edits a workspace template. The change goes live in every signature that uses it |
update_group |
Renames a group or points it at a different template, which reinstalls everyone's signature in it |
update_smart_field |
Renames a field, marks it required or rebinds its source. Binding it to a sync source overwrites teammate values on the next sync |
remove_teammates_from_group |
Takes teammates out of a group |
delete_teammate |
Deletes a teammate |
delete_group |
Deletes a group |
delete_smart_field |
Deletes a smart field |
delete_campaign |
Deletes a banner campaign |
What asks for confirmation
Lookups are marked read-only. Every tool that changes, overwrites or removes something is marked destructive, so assistants such as Claude and ChatGPT ask before they run them. On top of that, SyncSignature tells the assistant to show you what will change and wait for your yes, in particular for:
- Template edits. A workspace template is shared, so an edit changes the signature of every teammate in the groups that use it, with no draft step. The assistant should tell you which groups are affected before it saves.
- Deletes. Each delete is confirmed on its own, never as a batch. Deletes cannot be undone.
- Smart field changes. A smart field bound to Google Workspace, Microsoft 365, Chili Piper or a CSV is overwritten on the next sync, so a hand edit may not stick. The assistant should warn you first.
How an assistant asks for approval also depends on its own settings. Check what yours allows before you turn on auto-approval.
What it cannot do
- It does not route or read email. The server works on workspace data only: teammates, groups, templates, smart fields, campaigns and click analytics.
- Shared mailboxes are not supported. Signatures apply to teammates' own mailboxes.
- Directory sync is not real time. A change in Google Workspace or Microsoft 365 reaches SyncSignature on the next sync, which runs every 24 hours or on demand with one click.
Remove or revoke access
To stop an assistant using your workspace, remove the SyncSignature connector or MCP server in that assistant's settings. To revoke the connection's access completely on the SyncSignature side, email support@syncsignature.com with the workspace and the assistant you connected.
Troubleshooting
| What you see | Fix |
|---|---|
| The assistant says your session or token has expired | Reconnect: run the connect step again and sign in |
| "This connection has read-only access" | The connection was approved for read only. Remove it, reconnect, and allow changes on the sign-in page |
| A teammate field will not change, or changes back | The field is filled by directory sync. Edit it in Google Workspace or Microsoft 365, or rebind the smart field so it is no longer synced |
| The connection fails on an older URL ending in onrender.com | That address is being retired. Remove the connector and add https://mcp.syncsignature.com/mcp instead |
| The assistant cannot find a tool for what you asked | It may be outside what the server does. See Tools and What it cannot do |
Related articles
- What are smart fields explains which fields sync from your directory and which are edited by hand.
- Run banner campaigns for your team covers the campaigns your assistant can schedule.
- What are groups explains how a group's template reaches each teammate.
- Manager vs teammate covers which role can make which change.
- SyncSignature MCP server is the overview of what the server does.
Still stuck? Email support@syncsignature.com and include the assistant you are connecting and the message you see.
