Scribe Mail

com.scribe-mailPublished by scribe-mail.comOfficial publisherv1.0.2Updated Oct 24, 2026

Email signature management finally simple and measurable. Built for teams & AI agents.

Overview

AI-generated overview

Scribe Mail is a remote MCP server that lets an assistant author, publish and roll out company email signatures, run signature campaigns and read engagement.

What you can do
Author and publish signature templates and variants, with smart fields and reply or internal variants, previewing before publishing and installing them for teammates. Assign signatures through manual recipients, condition rules, org-unit targeting or future-email auto-assignment. Run marketing campaigns: create banner content, target recipients, and schedule, pause or resume them. Read analytics such as views, clicks, clickthrough rate, conversion events and visitors, as timeseries or breakdowns. Audit the workspace for missing signatures, failed installs, erroring integrations and unpublished drafts. Manage teammates, aliases and smart-field definitions, and consult the Scribe help center.
When to use it
Useful when a team manages company email signatures in Scribe and wants an assistant to draft and roll them out, diagnose why a signature is missing or stale, launch signature marketing campaigns, or report on signature engagement.
Requirements
A remote endpoint reached over streamable HTTP; no local package. A Scribe workspace with an owner or admin account, since signature and analytics scopes depend on those roles. OAuth 2.0 sign-in through WorkOS AuthKit, opened in the browser on first use. Claude Code v2.1.0+ or Cowork.
Before you install
The session acts as the signed-in user with that user's permissions, so an owner or admin account grants broad access to the workspace. Writes such as creating, publishing, installing, assigning, scheduling and deleting change what goes out on real company email; the server states each write is confirmed first and templates are previewed before publishing, but review changes before approving. Publishing a template is the point at which it reaches mailboxes.

Installation

In SourceWeft

  1. Open Scribe Mail in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.scribe-mail%2Fscribe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

Scribe Mail plugin for Claude

Manage your company's email signatures from Claude. This plugin connects Claude Code and Cowork to your Scribe workspace and adds the workflow knowledge to use it well: author and publish signature templates, roll them out to the right teammates, run signature marketing campaigns, and read engagement analytics.

Install

bash
claude plugin marketplace add scribemail/claude-pluginclaude plugin install scribe-mail@scribe-mail

On first use Claude opens the Scribe sign-in in your browser. Authentication is OAuth 2.0 via WorkOS AuthKit. No API key is pasted anywhere, and the session acts as you, in your own workspace, with your own permissions.

What it adds

The Scribe MCP server (https://mcp.scribe-mail.com/mcp): 60+ tools covering signature templates and variants, teammates, emails, smart fields, folders, assets, integrations, recipients and installations, marketing campaigns, analytics, and the Scribe help center.

Seven skills that carry the workflows an agent otherwise gets wrong:

SkillCovers
signature-authoringThe draft → preview → publish → install loop, the block-tree content format, smart fields, reply/internal variants
signature-rolloutManual recipients vs. condition rules vs. org-unit targeting vs. future-email auto-assign, and how they stack
signature-troubleshootingWhy a signature is missing, stale, or wrong, in the order that finds the cause fastest
marketing-campaignsBanner content, targeting, the draft → schedule → pause → resume lifecycle
signature-analyticsViews, clicks, clickthrough rate, conversion events, visitors; timeseries vs. breakdown
workspace-auditA one-pass health sweep: no-signature teammates, failed installs, erroring integrations, unpublished drafts
teammate-dataBulk smart-field edits, people and aliases, field definitions, and which writes silently do nothing because an integration owns the field

Try it

Which teammates are missing an email signature?Audit our Scribe workspace and tell me what to fix first.Create a signature template for the sales team and show me a preview.Why isn't [email protected]'s signature showing up in Outlook?Show me signature clickthrough by country for the last 30 days.Launch a campaign banner for our user conference, running 1–15 October.

Safety

Reads run freely. Every write (creating, publishing, installing, assigning, scheduling, deleting) is confirmed with you first, because it changes what goes out on real company email. Publishing a template is the moment it reaches mailboxes; the skills preview before they publish, every time.

Requirements

  • A Scribe workspace, and an owner or admin account in it (signature and analytics scopes ride on those roles).
  • Claude Code v2.1.0+, or Cowork.

Links

License

MIT, see LICENSE.

Source: README.md at commit ffd2361

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.2LatestOct 12, 2026
  2. v1.0.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts