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

> Answers on Scribe MCP access, data safety, and which AI assistants are supported when you connect one to your email signatures.

Common questions about connecting an AI assistant to Scribe through the MCP server.

## What access does the connection have?

The connection acts as you in one workspace. It can read your signatures, teammates, smart fields, folders, assets, integrations, campaigns, and analytics, and it can make changes only after you confirm each write.

## Is my data safe?

Yes. Scribe signs you in with OAuth, stores no API key from your assistant, and scopes every action to your own workspace. Read actions run automatically, and write actions ask for your confirmation first.

## Which assistants are supported?

Any assistant that supports custom MCP connectors works. Documented flows include Claude, ChatGPT, Mistral Vibe, Grok, Gemini, and Microsoft Copilot for chat, and Claude Code, Cursor, Codex, Hermes, and OpenClaw for coding.

## Keep going

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

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