ChatGPT
- Sends as
- YouYour Gmail or Outlook
- How it gets your signature
- Signatoro plugin from ChatGPT's plugin directory, or your signature as text in custom instructions
- Stays current
- Updates by itself
Add Signatoro to your agent as an MCP server:
https://signatoro.com/mcpThen ask it to make your email signature. It gives you a link to save it to Signatoro.
Copy this into your assistant's instructions, and it adds your signature to every email it sends. Coding agents take it in AGENTS.md or CLAUDE.md.
## Email signature
Before you send, reply to, forward or draft any email for me, with any mail tool, fetch my saved email signature from Signatoro and append it after the body.
- MCP: call Signatoro's `get_signature` (server `https://signatoro.com/mcp`). REST: `GET https://signatoro.com/api/v1/signature` with the header `Authorization: Bearer $SIGNATORO_API_KEY`. Keep the key in the environment and out of every output.
- Fetch it for every email. Append `html` to an HTML body and `text` to a plain-text body, after a blank line, as returned.
- Do not write your own sign-off or signature block.
- For my name, title, phone, email or links anywhere in the body, use only the values in `sender`. If one is missing, leave it out and tell me - never guess.
- If it is unclear which signature an email should carry, mine, one of my AI assistants' or a company AI agent's, call `list_signatures` and ask me before sending.Whoever sends it, an email from you or your company needs a consistent, on-brand signature, with the footnote your company sets on the Up to 15 plan or larger. Agents that fetch it from Signatoro get every change on their next email.
| Agent | Sends as | How it gets your signature | Stays current | Details |
|---|---|---|---|---|
| AI assistantsThey help while you work: they answer when you ask, or prepare drafts for you to check and send. You stay in control. | ||||
| ChatGPT | YouYour Gmail or Outlook | Signatoro plugin from ChatGPT's plugin directory, or your signature as text in custom instructions | Updates by itself | PageGuide |
| Claude | YouYour Gmail or Outlook; Claude for Outlook drafts in your Outlook | The Signatoro connector from Claude's directory; Claude for Outlook drafts get Outlook's own signature | Updates by itself | PageGuide |
| Grok | YouYour Gmail or Outlook; Grok for Outlook drafts in your Outlook | Signatoro MCP as a custom connector, or your signature as text; Grok for Outlook drafts get Outlook's own signature | Updates by itself | PageGuide |
| Gemini | YouYour Gmail | Gmail adds its own signature to "Help me write" drafts; for Gemini Spark, your signature as text in "Instructions for Gemini" | Re-paste after a change | PageGuide |
| Microsoft Copilot | YouYour Outlook | Outlook adds its own signature to "Draft with Copilot"; for Copilot Chat, your signature as text; Copilot Studio agents over MCP | Updates by itself | PageGuide |
| Shortwave | YouYour Gmail | Shortwave syncs your default Gmail signature; Signatoro MCP connects as a remote MCP server (beta, Business plans and up) | Re-paste after a change | PageGuideSource |
| Fyxer | YouDrafts in your Gmail or Outlook | Fyxer keeps its own copy: paste your signature under Dashboard > Drafts > Signatures, or sync it from Outlook | Re-paste after a change | PageGuideSource |
| Comet, Claude in Chrome, ChatGPT's cloud browser | YouYour Gmail or Outlook tab | Your mail app's own signature, set up once | Re-paste after a change | Guide |
| AI agentsThey work for you on their own: they start tasks themselves, on a schedule or when something happens, and can act without you. | ||||
| Claude Duet | YouYour Gmail or Outlook, through the connectors on your Claude account (research preview; the exact route is not yet confirmed) | Your signature as text, told to Duet once; it may already see a connector you added in Claude, not yet confirmed | Re-paste after a change | PageGuideSource |
| Meta Muse | YouYour Gmail, after you approve the send | Your Gmail signature, or text given to Muse once | Re-paste after a change | PageSource |
| Manus | YouYour Gmail or Outlook, typed in its Cloud Browser or your own browser, or through its Gmail and Outlook connectors | Your mail app's own signature in the compose window; for connector sends, Signatoro MCP as a custom MCP server, signed in (tested) | Updates by itself | PageGuideSource |
| Cue | ItselfThe agent's own email address | Signatoro MCP as a custom connector, or the Signatoro API with an agent key | Updates by itself | PageGuideSource |
| Poke | YouYour Gmail or Outlook | Signatoro MCP as a custom MCP integration | Updates by itself | PageGuideSource |
| Grok Bot | YouItselfYour Gmail or Outlook, or an agent address at mail.grokbot.com and its plus aliases, or AgentMail | Each Bot fetches its own from the Signatoro API with its own API key | Updates by itself | PageGuide |
| OpenAI dots | YouYour connected account, such as Gmail | Your Gmail signature, or text given to the dot once | Re-paste after a change | Page |
| Squad | ItselfThe teammate's own inbox | Paste the Signatoro MCP URL into the teammate | Updates by itself | Page |
| Viktor | ItselfIts own inbox, such as yourteam@viktor-mail.com | Signatoro as a custom MCP connection | Updates by itself | Page |
| OpenClaw | YouItselfYour Gmail, or an agent inbox such as AgentMail | Signatoro MCP as a remote MCP server in mcp.servers | Updates by itself | PageGuideSource |
| Hermes Agent | YouItselfYour Gmail, through the Google Workspace skill, or a mailbox of its own over IMAP and SMTP | Signatoro MCP in mcp_servers, signed in with hermes mcp login | Updates by itself | PageGuideSource |
| Salesforce Agentforce Engagement | ItselfYouThe agent's own connected mailbox, or the record owner's with Send as Seller | Send as Seller uses the record owner's own email signature | Re-paste after a change | GuideSource |
| Artisan Ava | YouYour connected Google or Microsoft mailbox | Paste your Signatoro signature as HTML into the sender signature under Outreach channels | Re-paste after a change | GuideSource |
| Intercom Fin | Your companyYour support address on your own domain | Fin replies carry your Intercom email signature, with an AI agent footer below it | Re-paste after a change | GuideSource |
| Gorgias AI Agent | Your companyYour store's connected support address | The email integration's signature, rich text with links and images; AI Agent adds its own signature line | Re-paste after a change | GuideSource |
| Agentic toolsWhat people use to build agents and automations. | ||||
| Lindy | YouYour Gmail or Outlook | Signatoro MCP as a Lindy MCP integration, or the Signatoro API with a Lindy credential | Updates by itself | PageGuideSource |
| Notion Custom Agents | YouYour Gmail or Outlook | Signatoro as a custom MCP server in the agent's Tools & Access | Updates by itself | PageGuideSource |
| n8n, Zapier and Make | YouItselfYour companyYour Gmail or Outlook, or SMTP | A step before the send fetches it from the Signatoro API | Updates by itself | Guide |
| Power Automate | YouItselfYour companyYour Outlook | An HTTP action fetches it from the Signatoro API on every run | Updates by itself | Guide |
| Base44 | ItselfYour companyBase44's no-reply address, or your app's custom domain | A backend function fetches it through a custom integration of the Signatoro API before SendEmail | Updates by itself | Guide |
| Twenty | YouYour companyThe connected account the workflow sends from | An HTTP Request step fetches it before Send Email, which adds its text after the message | Updates by itself | GuideSource |
| Google Apps Script | YouYour Gmail | UrlFetchApp fetches it from the Signatoro API | Updates by itself | Guide |
| Relevance AI and Dust | YouItselfYour companyYour Gmail or Outlook | Signatoro MCP added to the agent as a remote MCP server | Updates by itself | GuideSource |
| Claude Code, Cursor, Codex, Gemini CLI, Kimi Code, Windsurf, GitHub Copilot, Cline | YouItselfYour companyYour Gmail or Outlook, through a mail MCP server | Signatoro MCP as a second remote MCP server | Updates by itself | PageGuide |
| Open models such as DeepSeek, Kimi, Qwen and GLM | YouItselfYour companyThe mail tool of the app that runs the model | The app running the model, such as Goose or LM Studio, connects Signatoro MCP | Updates by itself | GuideSource |
| OpenAI Agents SDK, LangChain, CrewAI, AI SDK, Mastra, Google ADK | YouItselfYour companyWhichever mail tool your agent has | Signatoro MCP as an MCP toolset, or the Signatoro API as a tool | Updates by itself | Guide |
| Agentic infrastructureWhat agents run on and send through: inboxes, sending services, mail connections and identity. | ||||
| AgentMail | ItselfYour companyThe agent's own inbox | The agent fetches it over MCP or the REST API | Updates by itself | Page |
| Nylas Agent Accounts | ItselfYour companyThe agent's own inbox | Fetched from the Signatoro API and kept as one Nylas signature, passed on every send | Updates by itself | PageGuide |
| Microsoft Agent 365 | ItselfThe agent's own Microsoft 365 mailbox (Frontier preview) | The agent appends it from the Signatoro API, or an Exchange mail flow rule adds it | Updates by itself | PageGuideSource |
| Cloudflare Email Service | ItselfYour companyAn address on your own domain, from a Worker | The Worker fetches it from the Signatoro API before sendEmail | Updates by itself | GuideSource |
| Gmail and Outlook MCP servers | YouYour Gmail or Outlook | The agent calls Signatoro MCP before it sends | Updates by itself | Guide |
| Gmail API | YouYour Gmail | Your code fetches it from the Signatoro API, or reads Gmail's signature with sendAs | Updates by itself | Guide |
| Microsoft Graph | YouItselfYour companyYour Outlook | Your code appends it from the Signatoro API, or an Exchange mail flow rule adds it | Updates by itself | Guide |
| Superhuman Mail MCP | YouYour Superhuman inbox, Gmail or Outlook | Your signature set in Superhuman; an agent sending over the MCP calls Signatoro MCP first | Updates by itself | GuideSource |
| Resend, Postmark and Mailtrap MCP servers | ItselfYour companyAn address on your own verified domain | The agent calls Signatoro MCP or the API before it sends | Updates by itself | GuideSource |
They help while you work: they answer when you ask, or prepare drafts for you to check and send. You stay in control.
They work for you on their own: they start tasks themselves, on a schedule or when something happens, and can act without you.
What people use to build agents and automations.
What agents run on and send through: inboxes, sending services, mail connections and identity.
Three ways in, all reading the same saved signature. Each fetch returns the current version, so an edit on Signatoro reaches the next email.
Connect your assistant to Signatoro once, and you can ask it to work on your signature for you.
The tool names and the API are on the developer page. Email signature API
Commune's guide to agent email signatures lists what each agent's signature should hold. A Signatoro agent signature carries each point by default:
Source: Commune, "How do I set up email signatures for my agent?"
Each AI assistant or agent gets its own key or MCP connection and signs as the person it works for or as itself, by default with a line saying it is an AI and whom it acts for.
Free includes 1 AI assistant; each person on a Company plan gets 3 AI assistants, and the company gets 3, 10 or 25 agents by size, on top of the people the plan covers.
Gmail and Outlook add your saved signature in their own compose windows. An agent that sends on its own, outside those windows, skips that step, so the email ends wherever the agent's text ends. The agent has to add the signature itself, and Signatoro gives it the one to add.
An agent that sends from your mailbox, as you, uses your signature. An agent with an address of its own signs as itself, in your company brand, by default with a line saying it is an AI and whom it acts for.
Assistants such as Claude and ChatGPT ask you to sign in to Signatoro once. Automations and tools your team builds use a key you create on the Connect page, under "For tools and assistants".
Yes. An agent with the rule above fetches the signature for every email, and each fetch returns the version saved on Signatoro, so an edit reaches the next email.
Save the signature once on Signatoro, connect every agent to it (Claude, ChatGPT, Grok Bots, n8n, Nylas or tools your team builds) and give each the rule above. Each agent fetches its saved signature before every email, so a new agent or provider sends it from its first email, with nothing to paste.
Give each agent its own signature on Signatoro, signing as you with an AI line or as the agent with its own name and role, and its own connection. A connection made for one agent always signs as that agent, so two agents sending from one address each sign as themselves.
On Company, the owner sets the logo, layout, color, font and company details once for every person and every company AI agent. People keep their own name, title, phone and photo, company agents sign with their own name, role and AI line, and agents use no seat.
A pasted signature belongs to one assistant and stays as it was until you paste it again, in every assistant that holds a copy. Connected to Signatoro with the rule above, every agent fetches the current signature before each email, and each agent can have its own.