Skip to main content
Connect any MCP-capable assistant to Scribe in a couple of minutes. The endpoint is the same everywhere, and you sign in with your Scribe account (OAuth), so no API key is pasted in. 
https://mcp.scribe-mail.com/mcp
Read actions run automatically once connected. Write actions ask you to confirm first. For what the connection can access, see the FAQ.

​
Chat assistants

Works on all Claude plans.
  1. Open Settings, then Connectors, then Add custom connector.
  2. Name it Scribe and paste the URL: 
    https://mcp.scribe-mail.com/mcp
  3. Click Add, then sign in to Scribe when prompted.
The Scribe tools then appear in the chat composer’s tool menu.
Requires a Plus, Pro, Business, or Enterprise plan with Developer Mode enabled, on the web.
  1. Open Settings, then Connectors (Apps), and turn on Developer Mode.
  2. Choose Add custom connector and paste the URL: 
    https://mcp.scribe-mail.com/mcp
  3. Complete the Scribe sign-in.
Write actions prompt you to confirm before anything changes.
Works on the free plan.
  1. Open Connectors, then Add.
  2. Paste the URL: 
    https://mcp.scribe-mail.com/mcp
  3. Complete the Scribe sign-in.
Requires a paid account.
  1. On grok.com, open connector settings and add a remote MCP server.
  2. Paste the URL: 
    https://mcp.scribe-mail.com/mcp
  3. Complete the Scribe sign-in.
Set up by your Google Workspace admin in Gemini Enterprise, from the Google Cloud console.
  1. The admin adds a custom MCP server data store and enters the URL: 
    https://mcp.scribe-mail.com/mcp
  2. The admin registers an OAuth client (a client id and secret plus a redirect), then authorizes it.
  3. The admin enables the Scribe tools for users.
A two-role setup: an admin or maker builds a Scribe agent once in Copilot Studio, then the team chats with that published agent. Plain Copilot chat does not get the Scribe tools on its own.Prerequisites
  • A Microsoft 365 Copilot seat for each person who will use it
  • Copilot Studio capacity for the person who sets it up
  • Generative orchestration enabled on the agent
Set up (admin or maker)
  1. Open or create an agent in Copilot Studio, then Tools, Add tool, New tool, Model Context Protocol
  2. Enter the URL over Streamable HTTP: 
    https://mcp.scribe-mail.com/mcp
  3. Create the connection with OAuth, then enable the tool
  4. Enable generative orchestration if it is not already on
  5. Publish the agent
  6. Under Channels, make it available where the team works, in Microsoft Teams or the Microsoft 365 Copilot app
How your team uses it
  1. Open the published Scribe agent in Microsoft Teams or the Microsoft 365 Copilot app
  2. Manage Scribe by chatting with it
Writes ask for confirmation before anything changes.
A tenant-wide federated connector surfaces Scribe for retrieval and grounding in Copilot chat. The published-agent route above is what enables actions like creating signatures and installing to the team.
The DeepSeek app has no built-in connector. Use Scribe through any MCP-capable client, such as Claude or Cursor, with DeepSeek selected as the model.
Use Qwen Code, the command-line tool. The Qwen chat app has no connector.Add Scribe to its settings.json under mcpServers, then complete the sign-in on first connect:
{
  "mcpServers": {
    "scribe": {
      "type": "http",
      "url": "https://mcp.scribe-mail.com/mcp"
    }
  }
}

​
Coding assistants

Add the server, then verify it:
claude mcp add --transport http scribe https://mcp.scribe-mail.com/mcp
claude mcp list
Sign in to Scribe on first use.
Add Scribe to ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for one project. Reload the window, then sign in on connect:
{
  "mcpServers": {
    "scribe": {
      "type": "http",
      "url": "https://mcp.scribe-mail.com/mcp"
    }
  }
}
Or add it in one click:Add Scribe to Cursor
Add the server, which writes ~/.codex/config.toml, then sign in with OAuth:
codex mcp add scribe --url https://mcp.scribe-mail.com/mcp
Add the server with OAuth. A browser opens for sign-in on first connect:
hermes mcp add scribe --url https://mcp.scribe-mail.com/mcp
Add a mcpServers entry to ~/.openclaw/openclaw.json, or use mcporter:
{
  "mcpServers": {
    "scribe": {
      "type": "http",
      "url": "https://mcp.scribe-mail.com/mcp"
    }
  }
}

​
Next steps

Skills

Give your assistant the full Scribe workflow

Tools reference

Every Scribe MCP tool, grouped by area

Troubleshooting

Fix connection and tool issues

FAQ

Access, data safety, supported assistants