Manage your team's email signatures from your AI assistant
Connect Claude, ChatGPT, Cursor, and other AI assistants to your SyncSignature workspace. Ask who is missing a job title, add new hires to the right group, or launch a banner campaign, all by chatting. Sign in with your SyncSignature account, no API key.
MCP server URL
https://mcp.syncsignature.com/mcp
Connect in three steps
Add the server URL
Add it as a custom connector or remote MCP server in your assistant's settings.
Sign in to SyncSignature
Your assistant opens a SyncSignature sign-in page. Sign in, choose the workspace to connect, and click Allow. There is no API key to copy.
Ask in plain English
Ask about your teammates, groups, signature templates, and banner campaigns. Lookups are marked read-only, and SyncSignature instructs your assistant to confirm with you before any change.
What you can do today
Audit teammate details
Ask who is missing a job title, phone number, or department, then fill in the gaps you approve. Fields synced from your directory or a CSV stay locked, so a manual edit never fights your sync.
Onboard new hires
Add new teammates and assign them to a group. Each one gets a signature built from that group's template.
Run banner campaigns
Schedule a clickable banner for one or more groups, then pause, resume, or edit it by asking. A paused banner comes out of signatures right away.
Inspect and update templates
See which template each group uses and what it contains. A template edit applies to everyone in the groups that use it, and SyncSignature tells your assistant to state the head count first.
Troubleshoot missing signatures
Ask why someone has no signature. Your assistant checks their install record and whether a connected integration has expired.
Check signature clicks
Pull link clicks for a teammate's signature, broken down by country, browser, and device, for any date range.
Try it now
Copy this prompt to get started
Connect SyncSignature to this assistant. If you are Claude, open https://claude.ai/directory/syncsignature and click Connect. Any other assistant: add a custom MCP connector with the URL https://mcp.syncsignature.com/mcp. Sign in with my SyncSignature account, then read https://mcp.syncsignature.com/skills before doing anything.
For teams
One workspace, one sign-in
Each connection is tied to the workspace you choose when you sign in, and it acts as you. It cannot see or change any other workspace.
The same rules as the dashboard
Every request goes through SyncSignature's own API, so owner-only actions, synced-field locks, and rate limits apply exactly as they do in the app.
Changes roll out the usual way
Signatures you update through your assistant reach your team the same way edits made in the dashboard do.
What the connection can and cannot do
You sign in, with no API key
Connecting opens a SyncSignature sign-in page. You choose a workspace and approve access, and your assistant never sees your password or a key.
It acts as you, in one workspace
The connection has the same permissions you have in the workspace you picked. Actions limited to workspace owners stay limited to owners.
It is instructed to ask before any change
Lookups are marked read-only. Every change is marked as a write, deletes are flagged as destructive, and SyncSignature instructs your assistant to confirm with you first. How your assistant asks for approval also depends on its own settings.
It cannot read your email
The server works only with your SyncSignature workspace. It has no access to your inbox, contacts, or calendar.
Frequently asked questions
It is a hosted endpoint that connects your AI assistant to your SyncSignature workspace, so you can manage your team's email signatures by chatting. MCP (Model Context Protocol) is the open standard that lets assistants use outside tools like this one.
Any assistant that can connect to a remote MCP server and sign in with OAuth. That includes Claude, ChatGPT, and coding assistants such as Claude Code, Cursor, and Codex. See the AI agents page for step-by-step setup in each one.
Yes. Install it from https://claude.ai/directory/syncsignature and click Connect. It is also listed in the official MCP Registry as com.syncsignature/email-signatures.
Yes. The MCP server works on an existing SyncSignature workspace, so you sign in with your account when you connect. If you don't have one yet, create an account first.
No. You sign in with OAuth, the same way you sign in to other apps from your assistant. There is no key to copy, paste, or store.
Your assistant can do what your SyncSignature account can do in the dashboard, so team features such as groups and banner campaigns depend on your plan.
You sign in through SyncSignature, so your assistant never sees your password or an API key. The connection is limited to the one workspace you choose, carries your own permissions, and cannot read your email. Removing SyncSignature from your assistant's connectors stops it from connecting. To revoke its access completely, contact SyncSignature support.
The change applies to everyone in the groups that use that template, and it goes live as soon as it is made. SyncSignature tells your assistant to say how many people will be affected and get your agreement first, and the result reports how many signatures were queued for update.
Connect your AI assistant to SyncSignature
Manage your team's email signatures without leaving your AI workflow.