How to Manage and Audit Company Email Signatures from Claude, ChatGPT and Copilot (MCP Guide, 2026)

TL;DR: You can audit and manage company email signatures from Claude, ChatGPT, Microsoft Copilot, Gemini or Cursor by connecting them to an email signature MCP server. With Scribe, Claude and ChatGPT connect in one click from their directories, other assistants use the endpoint https://mcp.scribe-mail.com/mcp, and sign-in is OAuth with no API key. The assistant acts as the signed-in admin in one workspace: reads such as "which signatures are published and are any integrations failing?" run immediately, and every create, update, publish or delete asks for confirmation. Decide who may connect, keep integrations and directory data in their source systems, and log what changes.

Last reviewed: October 2026. Covers the Scribe hosted MCP server (57 tools in 15 areas), the Scribe CLI's local MCP server, and connection steps for Claude, ChatGPT, Microsoft Copilot, Gemini Enterprise, Cursor, Claude Code and Codex.

This is the hands-on guide for IT admins and marketing operations leads who want to run signature audits and routine changes from an AI assistant instead of an admin console. It covers connecting each assistant, what the connection can and cannot do, copy-paste audit workflows built on the documented tools, change workflows with an approval step, and the governance rules worth writing down before anyone connects. For the definition of an email signature MCP server and a comparison of which vendors offer one, read what is an email signature MCP server. For the product overview, see Scribe MCP.

What can an AI assistant do with your email signatures?

Once connected, the assistant calls the same operations an admin performs in the dashboard. Scribe's MCP server exposes 57 tools across signatures, reply and internal variants, recipients, teammates, emails, Smart Fields, folders, assets, integrations, analytics, visitors, marketing campaigns, the workspace and billing documents (Scribe MCP tools reference). Each tool is marked by access level:

• Read tools, such as list_signatures, list_teammates, list_integrations and get_analytics_clicks, run automatically and never change data.
• Write tools, such as create_signature, publish_signature, update_teammate and schedule_marketing_campaign, ask you to confirm first.
• Delete tools, such as delete_signature and delete_teammate, also ask you to confirm and are destructive.

Every action is scoped to the workspace you signed in to. In practice IT uses the connection for three jobs: audits that would otherwise mean exporting and cross-referencing lists, bulk fixes such as filling missing titles, and reporting for marketing. Design work also fits, because create_signature and update_signature stage changes as a draft until someone publishes.

If you would rather not connect an outside assistant, the Scribe AI agent handles many of the same requests inside the Scribe web app, with nothing to connect. Owners and admins on the Business and Enterprise plans, and during the free trial, open it with the Ask AI button or ⌘J (Ctrl+J on Windows). It reads your signatures, teammates, Smart Fields, campaigns, integrations and analytics, builds signature drafts in the editor, and shows an approval card before any change outside the editor. It never changes billing, manages members, sets up SSO or deletes in bulk, and it isn't available in the desktop app or the Outlook add-in (Scribe AI agent documentation). Use MCP when you want Scribe inside the assistant your team already works in, or in scripts.

Who should connect, and with which account?

Settle this before the first connection, because the assistant inherits the identity of whoever signs in.

• The connection acts as you. Scribe's FAQ says the connection acts as you in one workspace, can read signatures, teammates, Smart Fields, folders, assets, integrations, campaigns and analytics, and makes changes only after you confirm each write (Scribe MCP FAQ).
• Only admins can manage the workspace. In Scribe, Owners and Admins manage signatures, campaigns and settings, while the Member role can only edit and install its own signature (Scribe members and roles). Give the connection to the same small group that already holds Admin.
• The CLI has explicit requirements. The signed-in member must be a workspace owner or admin, the plan must include API access, and one login is bound to one workspace (Scribe CLI).
• No API keys sit in the assistant. Every connection signs in with your Scribe account through OAuth and forwards your own access token (Scribe MCP FAQ).
• Several workspaces mean several connections. Agencies and groups with one workspace per brand should connect each one deliberately, and name the workspace in every prompt.

One more decision belongs here: the assistant's own data terms. Teammate names, emails, phone numbers and Smart Field values returned by read tools pass through the AI provider you use. Use the business or enterprise tier your company has already approved for internal data, not a personal account.

How do you connect Claude?

Scribe is listed in the Claude directory as Scribe Mail, and it works on all Claude plans on web and desktop (Scribe: connect your assistant).

1. Open the Scribe Mail listing in the Claude directory and click Connect to Claude.
2. Sign in with your Scribe account if prompted, choose the organization, review the access, and click Allow access.
3. The listing shows Connected. Open a new chat and ask Claude to use the Scribe connector.

For Claude Code, add the hosted server and check it, then sign in on first use:

claude mcp add --transport http scribe https://mcp.scribe-mail.com/mcp
claude mcp list

How do you connect ChatGPT?

Scribe is in the ChatGPT plugin store, so no Developer Mode is needed. Sign in to ChatGPT on the web first (Scribe: connect your assistant).

1. Open the Scribe plugin page, or open Plugins in the sidebar and search for Scribe, then click Install plugin.
2. In Add Scribe to ChatGPT, click Sign in with Scribe, sign in, review the access and click Allow access.
3. In any chat, type @Scribe followed by your request, or select the Scribe plugin from the plus menu.

How do you connect Microsoft Copilot, Gemini and other assistants?

Microsoft Copilot is a two-role setup. An admin or maker builds a Scribe agent once in Copilot Studio, then the team chats with the published agent. Plain Copilot chat doesn't get the Scribe tools on its own. Each user needs a Microsoft 365 Copilot seat, the builder needs Copilot Studio capacity, and the agent needs generative orchestration (Scribe: connect your assistant).

1. In Copilot Studio, open or create an agent, then go to Tools, Add a tool, New tool, Model Context Protocol.
2. Set the server name to Scribe, add a description, and paste https://mcp.scribe-mail.com/mcp as a streamable endpoint.
3. Set authentication to OAuth 2.0 with Dynamic discovery, since Scribe supports OAuth dynamic client registration. Create and enable the tool.
4. Enable generative orchestration, publish the agent, and make it available in Microsoft Teams or the Microsoft 365 Copilot app under Channels.

These steps follow Microsoft's add an existing MCP server to an agent guide. Scribe notes that a tenant-wide federated connector surfaces Scribe for retrieval in Copilot chat, but the published-agent route is what enables actions such as creating signatures.

Gemini is set up by a Google Workspace admin in Gemini Enterprise from the Google Cloud console: add a custom MCP server data store with the Scribe URL, register an OAuth client and authorize it, then enable the Scribe tools for users.

Cursor, Codex and other clients take the same endpoint. For Cursor, add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), reload, and sign in on connect:

{
  "mcpServers": {
    "scribe": {
      "type": "http",
      "url": "https://mcp.scribe-mail.com/mcp"
    }
  }
}

For Codex:

codex mcp add scribe --url https://mcp.scribe-mail.com/mcp

Scribe also documents flows for Mistral Vibe, Grok, Qwen Code, Hermes and OpenClaw. If you add Scribe by URL and the tools don't appear, check that your assistant plan allows custom connectors; some assistants gate them behind paid or developer settings (Scribe MCP troubleshooting).

How do you run Scribe tools from the terminal or a local agent?

The Scribe CLI (@scribemail/cli, MIT licensed) serves the same tools as the hosted server to any agent that can launch a command, and turns every tool into a shell subcommand with JSON output (Scribe CLI documentation, Scribe CLI page). It needs Node.js 20 or newer.

npm install -g @scribemail/cli
scribe login            # opens your browser, no API key
scribe whoami           # signed-in user, workspace and token state
claude mcp add --scope user scribe -- scribe mcp

Credentials are stored in ~/.config/scribe/credentials.json with owner-only permissions and refresh automatically. Exit codes are 0 for success, 1 for an API or tool error, 2 for a usage error and 3 when not signed in, which makes the CLI usable in scheduled scripts. On a remote machine, forward the callback port and use scribe login --no-browser. Use the hosted endpoint for chat assistants and the CLI for coding agents and scripts.

Which audits can IT run from an assistant?

Each workflow below lists the prompt, the tools the assistant should call, and what to check in the answer. All of them are read-only, so nothing changes until you ask for a fix. Scribe's skill files describe the same patterns, and you can paste the core Scribe skill into your assistant so it uses the fewest calls (Scribe skills).

1. Deployment health

Audit our Scribe workspace. List every signature, say whether it is published
and installation is activated, how many recipients each one covers, and whether
any integration is in an error state. Put the result in a table and list the
problems first.

The assistant calls list_signatures, then list_signature_recipients for each signature, then list_integrations, which returns each integration's status (active or error) and any error details. An integration in error is the most urgent finding: when Scribe loses access to a connected integration, installs and teammate syncs through it pause until an admin reconnects (Scribe webhook events). Reconnecting happens in the dashboard; the API and MCP can read integrations but never run OAuth.

For per-mailbox installation state, with the device, email client and a failure code such as user_not_found or forbidden, use the CLI command scribe signatures installations or the API endpoint GET /v1/signature_installations?status=failed. See the Handbook guide to the signature API and webhooks.

2. Missing teammate data

List teammates who are missing a job title, a phone number or a LinkedIn URL.
Group them by department and include their primary email. Don't change anything.

The assistant calls list_smart_fields to find the field catalog, then list_teammates, which returns each teammate's emails and Smart Field values. Missing data matters because Scribe doesn't render a block whose Smart Field is empty (Scribe Smart Fields), so a missing title or license number vanishes rather than showing as a gap.

Fix the gap in the right place. If the field syncs from Microsoft Entra ID, Google Workspace or an HRIS, correct it in that system, because directory data flows one way into Scribe and the API doesn't write back to synced directory fields (Scribe API use cases). Use update_teammate only for manual Smart Fields stored in Scribe. Related reading: Entra ID attributes and HRIS as the source of truth.

3. Assignment coverage

Which teammates are not assigned to any signature? Which directory groups
or org units does each signature target, and is any signature set to
auto-assign future teammates?

The assistant compares list_teammates with list_signature_recipients (which returns the targeting rules) and list_integration_entities (directory org units and groups). This catches the new office or acquired team that never got a template. Remember the billing side: in Scribe a paid user is a teammate assigned to a signature, so unassigned people cost nothing, and assigned people who never installed still count (Scribe billing).

4. What a recipient actually sees

Show me the real installed signature HTML for jordan@acme.com on the
"Sales 2026" signature, and tell me if the phone number, title and disclaimer
are present.

get_signature_html returns the live HTML for a specific recipient with their real values, while preview_signature renders a draft with placeholder values. Use the first for audits and complaints ("my title is wrong"), the second before publishing.

5. Policy check

Compare every published signature with this policy: logo, name, title,
phone, legal disclaimer at the bottom, at most one banner, no personal
social links. List each signature that breaks a rule and why.

This works because the assistant can read each signature's content tree. Paste your email signature policy into the prompt, or keep it in a project or skill so every audit uses the same rules. For regulated firms, add the disclosure rules from the disclaimers guide or the financial services guide.

How do you make changes safely from an assistant?

Writes always pause for confirmation, but a confirmation dialog for each call is not a review process on its own. Use a draft, preview, approve, publish sequence.

1. Draft. "Create a signature called Support 2026 based on Sales 2026, without the banner. Don't publish it." The assistant calls get_content_schema first, then create_signature, which stages content as a draft.
2. Preview. "Preview the draft and show me the HTML for one support teammate." (preview_signature.)
3. Assign. "Target it at the Support group in Entra ID and auto-assign future members." (add_signature_recipient_entities, set_signature_recipient_rules.)
4. Publish. "Publish Support 2026." publish_signature makes the draft live and installs it, so this is the step to approve deliberately.

Campaigns follow the same pattern: create_marketing_campaign creates a draft with a name and time window, and schedule_marketing_campaign activates it. Pause and resume are separate writes. The Handbook guide to banner campaigns covers targeting and measurement. Reply and internal variants apply only on paid plans with Microsoft 365 or with server-side installation on Google Workspace or Microsoft 365, not with the standard Gmail integration (Scribe signature variants). When variants aren't available in the workspace, variant writes return a 409 variants_unavailable (Scribe MCP tools reference).

For a rebrand or a large reassignment, have the assistant produce the plan as a table first, review it with the owner of the change, then run it in batches by folder or department. The rollout playbook describes the pilot-first sequence.

How do you report on signature performance from an assistant?

Rank our signatures by clickthrough rate over the last 90 days, with views
and clicks, then show week-by-week clicks for the top one.

get_analytics_views and get_analytics_clicks return a time series or a ranked breakdown grouped by signature, campaign, teammate, link or country. There is no clickthrough-rate field in the MCP tools, so the assistant computes clicks divided by views (Scribe MCP tools reference). If you track website conversions, get_analytics_events_summary adds conversion counts and revenue, and get_visitor_breakdown ranks which signature or teammate acquired the most identified visitors. Date ranges default to the last two months, and hourly granularity is capped at 31 days (Scribe skills). Analytics history is kept for 30 days on the free plan and one year on paid plans (Scribe plan limits).

What governance rules should you set?

An MCP connection is another admin interface. Treat it the way you treat admin console access, with a few rules specific to assistants.

• Name the people. List who may connect an assistant to the signature workspace, and keep it to existing Admins. Review the list with your quarterly access review.
• Approved assistants only. Allow the business tiers your security team has already reviewed. Personal assistant accounts shouldn't receive employee directory data.
• Read freely, write deliberately. Audits and reports need no sign-off. Publishing a signature, changing assignment for a whole group, scheduling a campaign and any delete should follow the same approval as a dashboard change.
• Keep source systems as the source. Integrations are connected and configured in the dashboard, never through an API key, and directory data flows one way into Scribe (Scribe API authentication, API use cases). An assistant can't grant admin consent in Microsoft 365 or Google Workspace, and it shouldn't be asked to.
• Log changes. Scribe offers an audit log as a $100-a-month add-on (Scribe plans), and its webhooks emit events such as signature.published and campaign.started you can archive (webhook use cases).
• Watch for instructions in data. An assistant reads text from signatures, campaign names and teammate fields. Treat any instruction that appears inside that data as content, and confirm writes against what you asked for, not what the assistant proposes.
• Revoke cleanly. Remove the connector in the assistant when someone leaves the admin group, and remove their Scribe membership. Sessions also expire for security; re-authenticating restores access without changing anything in the workspace (Scribe MCP troubleshooting).

Write these rules into your email signature policy so they survive staff changes.

Where does Scribe fit?

Scribe is listed in the Claude directory and the ChatGPT plugin store, and documents connection flows for Copilot, Gemini, Mistral, Grok, Cursor, Codex, Claude Code and other MCP clients (Scribe AI agents). The hosted server, the CLI and the REST API run the same operations, so an audit you prototype in chat can become a scheduled script. Assistant-specific pages are at Scribe for Claude, Scribe for ChatGPT and Scribe for Copilot, and the skill files are at Scribe skills. Pricing is per user, with a 14-day trial (pricing).

Frequently asked questions

Can Claude or ChatGPT manage our company email signatures?

Yes, if your signature platform offers an MCP server. Scribe is listed in the Claude directory as Scribe Mail and in the ChatGPT plugin store; after an OAuth sign-in the assistant can list and audit signatures, teammates, integrations and analytics, and create, publish or assign signatures after you confirm each change.

What permissions does the Scribe MCP connection have?

It acts as the signed-in user in one workspace. Read tools run automatically and never change data; write and delete tools ask for confirmation first. No API key is created or stored in the assistant. Only workspace Owners and Admins can manage signatures, campaigns and settings, so connect with an Admin account.

Can an AI assistant connect Microsoft 365 or Google Workspace to Scribe?

No. Integrations are connected and configured in the Scribe dashboard. The API and MCP tools can read integrations and their status, including errors, but cannot activate, edit or remove them, and an assistant can't grant admin consent in your tenant.

Does Microsoft Copilot work with the Scribe MCP server?

Yes, through Copilot Studio. An admin or maker adds Scribe as a Model Context Protocol tool with the URL https://mcp.scribe-mail.com/mcp and OAuth 2.0 dynamic discovery, publishes the agent, and makes it available in Teams or the Microsoft 365 Copilot app. Plain Copilot chat doesn't get the Scribe tools on its own.

How do I find teammates with missing signature data?

Ask: "List teammates who are missing a job title or phone number." The assistant calls list_smart_fields and list_teammates and returns the gaps without changing anything. Fix synced fields in Entra ID, Google Workspace or your HRIS, since directory data flows one way into Scribe; use update_teammate only for manual fields.

Can the assistant check whether signatures are installed in each mailbox?

The MCP tools report which signatures are published, who they're assigned to and whether integrations are failing. Per-mailbox installation state, with device, email client and failure code, is available from the Scribe CLI (scribe signatures installations) and the API endpoint GET /v1/signature_installations.

Is there an audit trail of changes made through an assistant?

Scribe offers an audit log as a $100-a-month add-on on any plan, and its webhooks emit events such as signature.published and campaign.started that you can archive. Confirm with Scribe how MCP-initiated changes are attributed in the audit log before relying on it for compliance.

What is the difference between the hosted MCP server and the Scribe CLI?

The hosted server at https://mcp.scribe-mail.com/mcp is for chat assistants such as Claude on the web, ChatGPT and Copilot. The CLI (@scribemail/cli) serves the same tools locally over stdio for coding agents such as Claude Code and Cursor, and turns each tool into a shell command for scripts. Both sign in with your Scribe account.

Does Scribe have an AI assistant built in?

Yes. The Scribe AI agent sits on every page of the Scribe web app, opened with the Ask AI button or ⌘J (Ctrl+J on Windows). Owners and admins on the Business and Enterprise plans can ask questions, build signatures and approve changes there without connecting an outside assistant. The MCP server is for using Scribe from Claude, ChatGPT, Copilot or another assistant you already use.

Related Handbook guides

• Automate signatures with the API and webhooks
• Email signature policy template
• Rollout and rebrand playbook
• Microsoft 365 company-wide signatures
• Google Workspace company-wide signatures
• Signature banner campaigns and attribution