> ## Documentation Index
> Fetch the complete documentation index at: https://help.scribe-mail.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scribe MCP server: manage email signatures with AI

> Connect your AI assistant to the Scribe MCP server to create, audit, and report on email signatures by chatting in plain English.

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.

Point your assistant at this endpoint:

```
https://mcp.scribe-mail.com/mcp
```

* Connector name: `Scribe`
* Auth: OAuth sign-in with your Scribe account, no API keys
* Scope: your workspace, with read actions auto-approved and writes confirmed

## How does it work?

<Steps>
  <Step title="Connect your assistant">
    Add the Scribe connector once, then sign in with your Scribe account.
  </Step>

  <Step title="Ask in plain English">
    Tell your assistant what you want, like building a signature or checking last quarter's clicks.
  </Step>

  <Step title="Scribe does the work">
    Your assistant calls the right Scribe tools for you, with no copy and paste.
  </Step>

  <Step title="Review and confirm">
    You see the results, and any change is confirmed before it happens.
  </Step>
</Steps>

## 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.

| Scenario                                                          | Example prompt to your assistant                                                                                                                        | Outcome                                                                                |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| <a id="design-signature" />Design a signature template            | "Create a signature called Sales 2026 with our logo, each person's title and phone, and LinkedIn and X icons, then show me the draft before publishing" | A draft signature built and shown for your approval before it goes live                |
| <a id="audit-installs" />Audit install and compliance status      | "Which signatures are published, who are they assigned to, and are any integrations failing?"                                                           | A read-only report of published templates, assignment coverage, and integration errors |
| <a id="look-up-teammates" />Look up teammate and smart field data | "List teammates who are missing a job title or a phone number"                                                                                          | A read-only list of teammates with gaps in their smart field data                      |
| <a id="automate-setup" />Automate workspace setup                 | "Create a folder called Sales, add these three teammates, and set their job titles"                                                                     | Folders, teammates, and fields created, with each change confirmed first               |
| <a id="track-campaigns" />Track campaign performance              | "Show views and clicks for our spring banner campaign, week by week"                                                                                    | A read-only performance breakdown for the campaign over time                           |
| <a id="measure-engagement" />Measure clicks and clickthrough rate | "Rank our signatures by clickthrough rate over the last 90 days"                                                                                        | A read-only ranking of signatures by views, clicks, and clickthrough rate              |
| <a id="export-data" />Export engagement data                      | "Give me signature engagement by country for last quarter as a table"                                                                                   | A read-only dataset your assistant can format as a table or CSV                        |

## Before you connect

<Note>
  **What connecting means**

  Signing 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.
</Note>

## Set up Scribe MCP

<CardGroup cols={2}>
  <Card title="Connect your assistant" icon="link" href="/en/ai-agents/connect">
    Step-by-step setup for Claude, ChatGPT, Cursor, and more
  </Card>

  <Card title="Skills" icon="book" href="/en/ai-agents/skills">
    Give your assistant the full Scribe workflow
  </Card>

  <Card title="Troubleshooting" icon="bug" href="/en/ai-agents/troubleshooting">
    Fix connection and tool issues
  </Card>

  <Card title="FAQ" icon="circle-help" href="/en/ai-agents/faq">
    Access, data safety, supported assistants
  </Card>

  <Card title="Tools reference" icon="wrench" href="/en/ai-agents/tools">
    Every Scribe MCP tool, grouped by area
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Smart fields" icon="database" href="/en/smart-fields">
    The data that populates your signatures
  </Card>

  <Card title="Teammates" icon="users" href="/en/teammates/teammates-overview">
    The people your signatures deploy to
  </Card>

  <Card title="Analytics" icon="chart-line" href="/en/analytics-overview">
    Views, clicks, and clickthrough rate
  </Card>

  <Card title="Integrations" icon="plug" href="/en/integrations-overview">
    Connect your directory, HRIS, and mail
  </Card>

  <Card title="API reference" icon="code" href="/api-reference/introduction">
    The REST API behind the MCP server
  </Card>
</CardGroup>