Scribe

Manage a Scribe workspace through the Scribe MCP server: signatures, teammates, smart fields, folders, assets, integrations, marketing campaigns, and analytics.

When to use this skill

Use it whenever the user wants to:

create, edit, publish, install, or audit email signatures
assign signatures to teammates, org units, or rule-based audiences
add, update, or look up teammates and their email aliases
read or set smart fields (the merge fields that populate signatures)
organize folders or upload assets (logos, banners, pictures)
create, schedule, pause, or report on marketing campaigns
pull signature analytics (views, clicks, clickthrough rate)

Connection

Endpoint: https://mcp.scribe-mail.com/mcp
Auth: OAuth sign-in as the user. No API keys are pasted into the client.
Scope: one user in one workspace. Read tools run automatically. Write tools (create, update, delete, publish) ask the user for confirmation in the app.

Core workflow: create a signature in the fewest calls

From a cold session, a complete signature takes three calls:

Call get_content_schema first. In one response it returns the strict block-tree schema, a flat lookup of every allowed enum value (including the non-obvious icon names such as linkedin-in, facebook-f), and a complete worked example with a populated social-icon row.
Adapt that example into a draft_content block tree and call create_signature with a name and the draft_content.
Call publish_signature to copy the draft into the live content and trigger installation.

Do not hand-write a block tree or guess enum spellings. Always call get_content_schema before any create_signature, update_signature, or marketing-campaign content write. An invalid tree returns a 422 that names each offending field.

Common patterns

Audit installs: list_signatures (which templates are published and activated), then list_signature_recipients (who each one covers), then list_integrations (any failing connections).
Look up teammate data: list_teammates (emails and smart-field values), with list_smart_fields for the field catalog.
Fill gaps: read with list_teammates, then set values with update_teammate.
Target a signature: set_signature_recipient_rules for auto-assign and conditions, add_signature_recipients for specific emails, or add_signature_recipient_entities for directory org units and groups.
Run a campaign: create_marketing_campaign, then schedule_marketing_campaign.
Report: get_analytics_overview for totals and a time series, get_analytics_breakdown to rank signatures, teammates, campaigns, or countries.

Tool reference

Access key: Read runs automatically, Write asks for confirmation, Delete asks for confirmation and is destructive.

Schema

Tool	Access	What it does
`get_content_schema`	Read	Returns the signature block-tree schema, all enum values, and a worked example. Call before authoring content

Signatures

Tool	Access	What it does
`list_signatures`	Read	List signature templates (block trees omitted unless you pass `include_content`)
`create_signature`	Write	Create a template, staged as `draft_content` until you publish
`update_signature`	Write	Update a template by id, staged as a draft until you publish
`publish_signature`	Write	Publish a template so the draft becomes live and installs
`install_signature`	Write	Install the current live content without publishing
`delete_signature`	Delete	Delete a template and unassign it from teammates

Signature recipients

Tool	Access	What it does
`list_signature_recipients`	Read	List who a signature is assigned to, with the targeting rules
`add_signature_recipients`	Write	Assign a signature to a batch of teammate emails
`remove_signature_recipients`	Write	Remove manually assigned recipients from a signature
`set_signature_recipient_rules`	Write	Set auto-assign and the smart-field condition rules
`add_signature_recipient_entities`	Write	Target a signature at directory org units or groups
`remove_signature_recipient_entities`	Write	Untarget directory org units or groups

Teammates

Tool	Access	What it does
`list_teammates`	Read	List teammates with their emails and smart-field values
`create_teammate`	Write	Add a teammate from an email and optional field values
`update_teammate`	Write	Set a teammate’s smart-field values
`delete_teammate`	Delete	Soft-delete a teammate

Emails

Tool	Access	What it does
`list_emails`	Read	List teammate emails (primary and aliases)
`create_email`	Write	Add an alias email to a teammate
`update_email`	Write	Change an email address
`delete_email`	Delete	Soft-delete an alias email (a primary email cannot be deleted)

Smart fields

Tool	Access	What it does
`list_smart_fields`	Read	List smart-field definitions with kind and data source
`create_smart_field`	Write	Define a custom field, optionally synced from an integration
`update_smart_field`	Write	Update a custom field or its integration link
`delete_smart_field`	Delete	Delete a custom field and its values on every teammate

Folders

Tool	Access	What it does
`list_folders`	Read	List signature folders with their signature counts
`create_folder`	Write	Create a folder to organize templates
`update_folder`	Write	Rename a folder
`delete_folder`	Delete	Delete a folder (it must be empty first)

Assets

Tool	Access	What it does
`list_assets`	Read	List the image library (logos, banners, pictures)
`create_asset`	Write	Upload an image from base64 or a source URL
`update_asset`	Write	Update an asset’s name or role
`delete_asset`	Delete	Delete an asset (in-use assets are soft-deleted so they keep rendering)

Integrations

Tool	Access	What it does
`list_integrations`	Read	List active integrations with status and any error details
`list_integration_entities`	Read	List directory org units and groups to target a signature at

Financial documents

Tool	Access	What it does
`list_financial_documents`	Read	List invoices and credit notes with downloadable PDF links

Analytics

Tool	Access	What it does
`get_analytics_overview`	Read	Views and clicks over a date range, with totals and a time series
`get_analytics_breakdown`	Read	Rank a dimension by views, clicks, or clickthrough rate

Marketing campaigns

Tool	Access	What it does
`list_marketing_campaigns`	Read	List campaigns with status, targeting, and content
`create_marketing_campaign`	Write	Create a campaign draft with a name and time window
`update_marketing_campaign`	Write	Update a campaign by id
`schedule_marketing_campaign`	Write	Activate or schedule a draft or paused campaign
`pause_marketing_campaign`	Write	Pause an active campaign
`resume_marketing_campaign`	Write	Resume a paused campaign
`delete_marketing_campaign`	Delete	Delete a campaign (an active one stops first)

Important notes

Always call get_content_schema before writing any signature draft_content or campaign content. It is the fastest path to a valid block tree.
Writes are staged. create_signature and update_signature set draft_content; the live content changes only when you call publish_signature.
Some actions are blocked when a directory integration (Google Workspace or Microsoft Entra ID) manages the team list. Creating or deleting teammates and emails then returns a 409.
Default and integration-synced fields are read-only. Setting them is skipped or returns a 422.
List tools are paginated with cursor and limit (1 to 100), plus a bounded auto_paginate and max_pages (cap 20).
Every write asks the user to confirm in the connected app, and every action is scoped to the user’s own workspace.

​Scribe

​When to use this skill

​Connection

​Core workflow: create a signature in the fewest calls

​Common patterns

​Tool reference

​Schema

​Signatures

​Signature recipients

​Teammates

​Emails

​Smart fields

​Folders

​Assets

​Integrations

​Financial documents

​Analytics

​Marketing campaigns

​Important notes