Scribe Mail MCP server
2026년 11월 12일 커밋Manage email signatures, marketing campaigns, and analytics through a command line interface or an MCP server for AI agents.
다른 이름 scribemail/cli
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 12일
- 라이선스
- MIT
Scribe Mail MCP란?
Manage email signatures, marketing campaigns, and analytics through a command line interface or an MCP server for AI agents.
프로젝트 README에서 생성된 요약
Scribe Mail MCP server 정보
Managing company-wide email signatures and marketing campaigns through an AI agent is what this tool enables. It provides a command line interface and an MCP server that exposes over 60 tools for controlling Scribe workspaces. Users can handle everything from signature creation and publishing to managing teammates, assets, and smart fields.
Administrators and marketing teams use this to deploy consistent signatures without manual employee installation. The server runs locally via stdio, allowing integration with Claude Desktop, Cursor, or Claude Code. To get started, users install the package via npm and run a login command that uses WorkOS AuthKit OAuth 2.1 to authenticate through a browser. This setup requires the user to be a workspace owner or admin on a plan that includes API access. Once connected, an AI agent can execute complex tasks like scheduling campaigns, analyzing click-through rates, or searching documentation.
활용 사례
- 1Deploying new email signaturesAn AI agent can create and publish a new signature template for a specific sales team.
- 2Analyzing marketing performanceA developer can ask an AI to retrieve analytics data grouped by signature templates to track conversion.
- 3Managing team accessYou can use the tool to list or synchronize teammates within your workspace.
- 4Automating campaign schedulesAn agent can manage the lifecycle of marketing campaigns by pausing or resuming them.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
자동 검사
2026년 11월 15일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능scribemail/cli is public and reachablegithub.com/scribemail/cli ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/scribemail/cli ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기Scribe Mail CLI
Email signatures finally simple and measurable. Built for teams & AI agents.
Install consistent signatures company-wide in under a day. IT sets up once. Marketing takes over. AI agents assist. No employee installation. 12% average CTR on signature banners. Conversion tracking from click to revenue.
@scribemail/cli is the official Scribe command line: manage your workspace's email signatures, teammates, smart fields, folders, assets, marketing campaigns, and analytics, or serve the whole tool surface to a local AI agent over MCP.
The CLI ships the exact same 60+ tools as the Scribe remote MCP server, generated from the same code, so the two never drift.
Install & sign in
npm install -g @scribemail/cli
scribe login
scribe login opens your browser and signs you in with your Scribe account (WorkOS AuthKit OAuth 2.1 + PKCE, no API key to paste). Credentials are stored in ~/.config/scribe/credentials.json (0600) and refreshed automatically.
Requirements: the signed-in member must be a workspace owner or admin, and the workspace plan must include API access. One login is bound to one workspace: run
scribe loginagain to switch.
Use with a local agent (MCP)
claude mcp add --scope user scribe -- scribe mcp # Claude Code
Claude Desktop / Cursor config:
{ "mcpServers": { "scribe": { "command": "scribe", "args": ["mcp"] } } }
scribe mcp is a stdio MCP server running as you, with the same tools, names, and schemas as the remote server.
Use from the shell
Every tool is also a subcommand. JSON goes to stdout, errors to stderr:
scribe whoami
scribe signatures list --limit 10
scribe signatures create --name "Sales" --draft-content @tree.json
scribe signatures publish --id <uuid>
scribe teammates list --auto-paginate
scribe analytics views --start-date 2026-07-01 --end-date 2026-08-01 --group-by signature_template
scribe docs search --query "dns setup"
scribe tools: every MCP tool name and its CLI command.scribe call <tool_name> --json '{...}': call any tool by its exact MCP name.- Complex fields (block trees, conditions) take inline JSON,
@file, or-(stdin);--jsonsupplies the whole arguments object and explicit flags override it. - Booleans:
--x/--no-x; leaving both off omits the field (PATCH semantics).
Exit codes: 0 ok · 1 API/tool error · 2 usage error · 3 not signed in.
Global flags: --api-base-url, --timeout-ms, --max-retries, --pretty. The target environment (production for the published package) is baked in at build time; there is no user-facing environment switch.
Commands
| Group | Commands |
|---|---|
signatures |
list create update delete duplicate test-email publish install preview html installations |
signatures variants |
list update publish delete |
signatures recipients |
list add remove set-rules add-entities remove-entities |
teammates |
list create update delete sync |
emails |
list create update delete install |
smart-fields / folders / assets |
list create update delete |
campaigns |
list create update delete preview schedule pause resume |
analytics |
views clicks events events-summary |
visitors |
list get breakdown |
integrations |
list entities |
| top-level | workspace · billing documents · content-schema · docs search · docs read · feedback |
| session | login · logout · whoami · mcp · tools · call |
Headless / SSH
Login needs a browser reaching 127.0.0.1 on the machine running the CLI. Over SSH, forward the callback port and use --no-browser:
ssh -L 8976:127.0.0.1:8976 yourserver
scribe login --no-browser # then open the printed URL locally
Contributing
Bug reports and feature requests are welcome in issues.
The tools are defined in Scribe's MCP server, which is a private repository: this repo imports the tool core from a sibling ../mcp-server checkout and bundles it at build time. You can read everything here, but building, testing, and CI need access to scribemail/mcp-server, so pull requests from outside the Scribe team can't pass CI. Open an issue instead and we'll take it from there.
For the Scribe team, with both repos side by side:
git clone git@github.com:scribemail/mcp-server.git
git clone git@github.com:scribemail/cli.git
cd mcp-server && pnpm install && cd ../cli && pnpm install
pnpm typecheck && pnpm test && pnpm build && pnpm test:e2e
The target environment is fixed at build time with no runtime override: pnpm build targets production (what npm users get); pnpm build:staging produces an internal staging build. Dev runs (pnpm dev, tests) resolve to production defaults, so use a staging build to exercise staging.
Releases: pnpm release (bumps, tags vX.Y.Z, pushes; GitHub Actions publishes to npm via OIDC Trusted Publishing).
Scribe Mail MCP 질문
How do I use Scribe with an AI agent like Claude?
You can add the Scribe MCP server to Claude Desktop or Cursor by running 'scribe mcp' as a stdio MCP server.
How do I sign in to the CLI?
Run 'scribe login' to open your browser and sign in using WorkOS AuthKit OAuth 2.1 + PKCE.