1. Your AI assistant
You type a request in Claude, ChatGPT, Copilot, Cursor, or any MCP client. The assistant works out which tools it needs.
What is an email signature MCP server?
The connection that lets AI assistants read and manage your company's email signatures.
What it is, what you can ask it, and which signature tools offer one.
What it is, what you can ask it, and which signature tools offer one.
Definition
Email signature MCP server, defined
An email signature MCP server is a Model Context Protocol (MCP) server that connects AI assistants such as Claude, ChatGPT, Microsoft Copilot, Cursor, and Gemini to a company's email signature platform. It exposes signatures, teammate data, banner campaigns, and analytics as tools the assistant can call, so IT and marketing teams can audit, update, and report on every employee's signature by asking in plain English instead of working through an admin console.
- Protocol
- Model Context Protocol, the open standard AI assistants use to call external tools.
- Who uses it
- IT admins, marketing teams, and RevOps, from the AI assistant they already use.
- What it reaches
- Signatures, recipients, teammates, Smartfields, campaigns, and analytics.
- Access
- Signed in as you, in your workspace. In Scribe, reads run directly and every change is confirmed first.
How it works
From a sentence to a signature change
Three parts work together. You only ever talk to the first one.
2. The MCP server
The server lists the tools your signature platform offers, like list signatures or schedule a campaign, and runs the ones the assistant calls.
3. Your signature platform
The change lands in the same workspace your admins use, and deploys to every inbox the way a change made by hand would.
Who it's for
What it lets IT and marketing do
The same connection serves both teams. Each one asks for what it owns.
For IT
Audit which signatures are published and who they are assigned to, fix missing teammate data, target signatures at directory groups, and spot failing integrations, without opening the admin console.
For marketing
Schedule banner campaigns for a team and a date range, pause or resume them, and pull views, clicks, and clickthrough rate for any signature or campaign.
Use cases
Real requests, typed into Claude or ChatGPT
Each one works today with the Scribe MCP server. Copy any of them into your assistant once it is connected.
Audit compliance
Audit every published signature and list the ones that are missing our legal disclaimer, with who each one is assigned to.
Schedule a banner campaign
Schedule the Q4 webinar banner for the sales team from November 1 to November 30.
Update teammate data
Update the phone number for everyone in the Paris office to +33 1 84 88 00 00.
Find what performs
Which signature got the most clicks last month, and what was its clickthrough rate?
Fill data gaps
List the teammates who are missing a job title or a phone number.
Target a directory group
Assign the Sales 2026 signature to the Sales group from Microsoft Entra ID.
Check integrations
Are any of our integrations failing? Tell me which ones and what the error says.
Comparison
Which email signature tools have an API or MCP server?
Developer access across the main email signature platforms, from each vendor's public documentation.
| Tool | REST API | MCP server | Webhooks | CLI |
|---|---|---|---|---|
| Scribe | YesREST, versioned under /v1 | YesHosted, OAuth. In the Claude Directory and ChatGPT app directory | YesSigned events | Yes@scribemail/cli, also a local MCP server |
| Exclaimer | PartialDistributor and partner API only | Not public | Not public | Not public |
| CodeTwo | Not public | Not public | Not public | Not public |
| Letsignit | PartialRead a user's signature, plus SCIM | Not public | Not public | PartialPowerShell scripts, not a CLI |
| WiseStamp | PartialKey from support, no public reference | Not public | Not public | Not public |
| Rocketseed | PartialMentioned, no public reference | Not public | Not public | Not public |
| Opensense | PartialMentioned, no public reference | Not public | Not public | Not public |
| Xink | YesREST, OAuth 2.0 | Not public | Not public | Not public |
| Signitic | YesCore API | PartialOfficial, read-only | PartialContact data event only | Not public |
| SyncSignature | Not public | YesOfficial, hosted | Not public | Not public |
"Not public" means we found no public documentation for it, not that it cannot exist. Checked against each vendor's public docs in October 2026. Spotted something out of date? Tell us and we will fix it.
Connect
Connect the Scribe MCP server
One sign-in with your Scribe account. No API key, no code.
Claude
Listed as Scribe Mail in the Claude Directory. Click Connect to Claude and sign in.
ChatGPT
Listed as Scribe in the ChatGPT app directory. Install it like any ChatGPT app, no Developer Mode.
Copilot, Gemini, Cursor, and more
Step-by-step setup for every other assistant, from Microsoft Copilot and Gemini to Cursor, Codex, and Claude Code.
Scribe MCP server
The endpoint, every tool area, the security model, and copy-paste prompts.
Run it locally
The Scribe CLI serves the same tools over stdio with scribe mcp, for Claude Code, Cursor, and any local agent.
Tools reference
Every Scribe MCP tool, grouped by area, with read, write, and delete access marked.
FAQ
Email signature MCP server questions answered
It is a Model Context Protocol server that connects an AI assistant to an email signature platform. The assistant can then list, create, publish, and assign signatures, update teammate data, run banner campaigns, and report on clicks by calling the server's tools, so you manage signatures by chatting instead of clicking through an admin console.
A REST API is built for developers: you write code and manage an API key. An MCP server describes the same operations as tools an AI assistant can discover and call on its own, so anyone can use them in plain English. Scribe offers both, and its MCP server runs on the same REST API.
Any assistant that supports MCP. With Scribe, Claude and ChatGPT install it from their app directories, and Microsoft Copilot, Gemini, Grok, Mistral, Cursor, Codex, and Claude Code connect to https://mcp.scribe-mail.com/mcp.
The Scribe MCP server signs you in with OAuth, so no API key is stored in your assistant. It acts as you, in your own workspace only. Read actions like listing and reporting run directly, and every write, such as creating, updating, publishing, or deleting, asks for your confirmation first. Scribe is SOC 2 Type II, GDPR, and CCPA certified.
No. In Claude or ChatGPT you add Scribe from the app directory and sign in. Other assistants take one connector URL. Developers who want scripts or a local server can use the Scribe CLI or the REST API, but neither is required.
Scribe offers a hosted, official MCP server, listed in the Claude Directory, the ChatGPT app directory, and the official MCP Registry. Based on public documentation in October 2026, SyncSignature also offers a hosted MCP server and Signitic offers a read-only one. We found no public MCP server from Exclaimer, CodeTwo, Letsignit, WiseStamp, Rocketseed, Opensense, or Xink.
With Scribe: audit which signatures are published and who has them, find teammates missing a title or phone number, update their details, assign signatures to directory groups, schedule, pause, and resume banner campaigns, and rank signatures by views, clicks, and click-through rate.
The Scribe MCP server is available to every Scribe workspace. Connect any MCP-capable assistant and sign in with your Scribe account.
