Skip to main content
The Scribe MCP server lets your AI assistant manage your Scribe account by chatting with it. It is a hosted Model Context Protocol endpoint that connects assistants like Claude, ChatGPT, and Cursor to your email signatures, teammates, smart fields, campaigns, and analytics, so you can create and audit signatures in plain English instead of clicking through the dashboard. Scribe is listed in the Claude directory and the ChatGPT plugin store, the first email signature management platform available in both. Claude and ChatGPT users connect in one click from those listings. Every other MCP-capable assistant connects with this endpoint:
  • Connector name: Scribe (listed as Scribe Mail in the Claude directory)
  • Auth: OAuth sign-in with your Scribe account, no API keys
  • Scope: your workspace, with read actions auto-approved and writes confirmed
  • Tools: 57 tools across 15 areas, see the tools reference

Where to find Scribe

Claude directory

Listed as Scribe Mail under Sales and marketing, Legal, Data, and Communication. Click Connect to Claude, then sign in.

ChatGPT plugin store

Listed as Scribe under Business and Operations. Click Install plugin, then sign in with Scribe.
Both listings run on the same hosted MCP server, so the tools, permissions, and confirmation rules are identical whichever way you connect.

How does it work?

1

Connect your assistant

Add Scribe from the Claude directory or the ChatGPT plugin store, or paste the connector URL into any other MCP client, then sign in with your Scribe account.
2

Ask in plain English

Tell your assistant what you want, like building a signature or checking last quarter’s clicks.
3

Scribe does the work

Your assistant calls the right Scribe tools for you, with no copy and paste.
4

Review and confirm

You see the results, and any change is confirmed before it happens.

What can an AI agent do with Scribe?

Each example below is a prompt you type to your assistant. Read actions return an answer right away. Write actions ask you to confirm before anything changes.

Before you connect

What connecting meansSigning in authenticates the assistant as you, in your workspace only. Read actions like listing and reporting run automatically. Write actions like creating, updating, deleting, and publishing ask for your confirmation first. Scribe uses OAuth, so no API key is stored in your assistant.

Set up Scribe MCP

Connect your assistant

One-click setup from the Claude directory and ChatGPT plugin store, plus Cursor, Codex, and more

CLI

The terminal companion: local MCP for coding agents, plus shell commands

Skills

Give your assistant the full Scribe workflow

Troubleshooting

Fix connection and tool issues

FAQ

Access, data safety, supported assistants

Tools reference

Every Scribe MCP tool, grouped by area

Smart fields

The data that populates your signatures

Teammates

The people your signatures deploy to

Analytics

Views, clicks, and clickthrough rate

Integrations

Connect your directory, HRIS, and mail

API reference

The REST API behind the MCP server