No API key to manage
scribe login opens your browser and signs you in with your Scribe account. Credentials stay on your machine and refresh on their own.
Scribe CLI
Manage email signatures from your terminal
Install @scribemail/cli, sign in once with your browser, and run every Scribe tool as a command with JSON output. Or serve the same tools to Claude Code, Cursor, and any local AI agent over MCP. Open source, MIT licence.
Ask your coding agent to set up the Scribe CLI
Connect Scribe with your AI agent
Copy prompt
I want to manage my email signatures from the terminal with the Scribe (https://www.scribe-mail.com) CLI. Walk me through it step by step. Read the docs at https://help.scribe-mail.com/en/ai-agents/cli. Then help me install it with npm install -g @scribemail/cli (it needs Node.js 20 or newer), sign in with scribe login, and check the session with scribe whoami. If I don't have a Scribe account yet, send me to https://www.scribe-mail.com to start a free 14-day trial first. Then run scribe signatures list and show me the output so I can confirm it worked. If you can launch local MCP servers, add scribe mcp as one so you can use the Scribe tools directly.
Benefits
Why teams use the Scribe CLI
One install gives your terminal, your scripts, and your local AI agents the same 57 tools as the hosted Scribe MCP server.
Built for scripts
Results are JSON on stdout, errors are text on stderr, and exit codes tell success from a usage error or a missing sign-in.
Every tool is a command
Signatures, teammates, Smartfields, campaigns, analytics, and more, each as a subcommand. scribe call runs any tool by its MCP name.
A local MCP server
scribe mcp serves every Scribe tool to Claude Code, Claude Desktop, Cursor, or any agent that can launch a command over stdio.
Never out of sync
The CLI is generated from the same code as the hosted MCP server, so tool names and behaviour always match.
Open source
Published under the MIT licence. Read the code, follow releases, and report issues on GitHub.
How it works
Up and running in three commands
Install from npm, sign in once, then work from the shell or hand the tools to your agent.
1
Install from npm
Run npm install -g @scribemail/cli. It needs Node.js 20 or newer.
2
Sign in with your browser
Run scribe login and sign in with your Scribe account, then scribe whoami to check the workspace you are in.
3
Run a command or serve your agent
Run scribe signatures list to see your signatures, or scribe mcp to give a local AI agent every Scribe tool.
Commands
Every Scribe tool, one command away
Run scribe tools to list every command. Partial updates never overwrite a field you left out.
scribe signatures
Create, update, publish, install, and preview signatures, and get the installed HTML.
scribe signatures variants
Manage the reply and internal versions of a signature.
scribe signatures recipients
Choose who gets a signature: teammates, groups, and assignment rules.
scribe teammates
List, add, update, and remove teammates. emails, folders, and assets work the same way.
scribe smart-fields
Manage the dynamic fields that fill your signatures, like titles and phone numbers.
scribe campaigns
Create, preview, schedule, pause, and resume banner campaigns.
scribe analytics
Pull views, clicks, and events, grouped by signature, teammate, or campaign.
scribe visitors
List and break down the people who clicked your signatures.
scribe integrations
See the integrations connected to your workspace and their entities.
scribe workspace
Read workspace settings and billing documents, and search the help centre with scribe docs search.
FAQ
Your Scribe CLI questions answered
The Scribe CLI (@scribemail/cli on npm) is a command line tool to manage email signatures, teammates, Smartfields, campaigns, and analytics from your terminal. Every Scribe tool is a subcommand with JSON output, and scribe mcp serves the same tools to a local AI agent over MCP.
Run npm install -g @scribemail/cli with Node.js 20 or newer, then scribe login to sign in with your browser and scribe whoami to check the session.
No. scribe login signs you in with your Scribe account in the browser. Credentials are stored on your machine with owner-only permissions and refresh automatically. Over SSH, run scribe login --no-browser and open the printed URL locally.
Yes. Run claude mcp add --scope user scribe -- scribe mcp for Claude Code. For Claude Desktop, Cursor, and other clients configured in JSON, add a server with the command scribe and the argument mcp. The agent then calls every Scribe tool as you.
They share the same tools. The hosted MCP server at mcp.scribe-mail.com/mcp is the right choice for chat assistants like Claude and ChatGPT. The CLI runs on your machine, for scripts, for agents that only speak stdio, and for tool calls that run as your signed-in terminal session.
Yes. It is published under the MIT licence, with its code, releases, and issues on GitHub at github.com/scribemail/cli.
The CLI is part of the Scribe API, included in the Business and Enterprise plans and in the 14-day free trial. The signed-in member must be a workspace owner or admin.
ROI
Calculate your potential revenue
and savings
See how much revenue and time your team could gain with Scribe email signatures.
12% average click-through rate - 6x higher than email marketing standards. Measured on 50,000+ emails with Scribe marketing banners.
With Scribe's conversion tracking, it's a number you will be able to measure.
ROI Calculation
Monthly
Yearly
Save 20%252,0000
Yearly outreach emails
New leads per year
30,2400
Paying customers
6000
Average order value
$100$0
Potential yearly revenue
$60,000$0
Yearly billing discount
-$348$0
Scribe Yearly Cost
-$1,392$0
Total Earned
+$58,608$0
This is earned back on a yearly basis
