Manage email signatures from Codex
Connect SyncSignature to the Codex CLI and manage your workspace with natural language: import teammates, audit missing details, and preview signature templates. Sign in with your SyncSignature account, no API key.
Copy this prompt to connect Codex
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.
How to connect Codex
Register the MCP server
Run `codex mcp add syncsignature --url https://mcp.syncsignature.com/mcp` in your terminal. Codex saves the connection to `~/.codex/config.toml`.
Sign in to SyncSignature
Codex detects the sign-in and opens your browser. Sign in with your SyncSignature account, choose the workspace to connect, and click Allow. Run `codex mcp login syncsignature` if you need to sign in again later.
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.
Ask Codex to...
Import teammates from a CSV
Read new-hires.csv (name, email, title, department) and add each person to SyncSignature in the Engineering group. Show me the full list and wait for my go-ahead before creating anyone.
Audit teammate data
List every teammate in my SyncSignature workspace and write a Markdown table of who is missing a job title, phone number, or department.
Preview a signature
List the SyncSignature signature templates, then render a preview of template 1 with my details from team.json and save the HTML to preview.html.
Report on campaigns
List our SyncSignature banner campaigns and summarize which are active, which are paused, and when each one ends.
Map synced fields
List the SyncSignature smart fields in my workspace and tell me which ones sync from Google Workspace or a CSV and which are filled in by hand.
Frequently asked questions
Add the SyncSignature MCP server (https://mcp.syncsignature.com/mcp) as a connector in Codex, sign in with your SyncSignature account when asked, choose your workspace, and click Allow. The setup steps above walk you through it.
It can look up teammates and fill in missing details, add people to groups, inspect and update signature templates, run banner campaigns, check smart fields and integrations, and pull click analytics for a teammate's signature.
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 at syncsignature.com 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.
SyncSignature marks every lookup as read-only and every change as a write, flags deletes as destructive, and tells Codex to show you what will change and wait for your yes. How Codex asks for approval also depends on its own settings.
The MCP setup guide covers setup in Claude, ChatGPT, Claude Code, Cursor and VS Code, every tool the server offers, what asks for confirmation, and how to fix common connection errors.
Use the MCP server. It is the supported way for AI agents to work with SyncSignature, and OAuth sign-in means there are no keys to manage in your project.
Connect Codex to SyncSignature
Manage your team's email signatures without leaving your AI workflow.