Model Context Protocol

Your signatures.
Your assistant.

Connect a compatible MCP client to the same account-scoped operations as the REST API. Inspect your setup, upload brand assets, manage schedules and apply signatures without switching tools.

Connect your client

Add an HTTP MCP server using the URL below. Configure an Authorization header containing your account key. The exact configuration format depends on your client; use its HTTP server settings.

HTTP connection settings
URL: https://signatures.workflowcorp.com/api/mcp
Transport: Streamable HTTP (JSON responses)
Header: Authorization: Bearer YOUR_ACCOUNT_KEY
This server uses a manually supplied bearer key. It does not offer an OAuth sign-in flow. Your MCP client must support custom authentication headers.

Available tools

Tool definitions below come from the server’s published catalogue.

Get account status

signaturebuddy_get_status

Read billing, Google connections, saved schedule summary, auto-apply setting and last deployment for the authenticated account.

Read only

Upload a signature image

signaturebuddy_upload_image

Host a PNG, JPEG, GIF or WebP image (up to 3 MB by default) at a permanent public URL. Images are content-addressed and cannot be deleted; do not upload private content.

Changes your account or connected service

Get signature schedule

signaturebuddy_get_schedule

Read this account's complete saved signature schedule, or null if none exists.

Read only

Save signature schedule

signaturebuddy_save_schedule

Replace this account's complete schedule. Updates billed seat quantity to match the team and may create prorated charges. The daily job will publish it when auto-apply is enabled; this call does not publish immediately. Confirm the team and schedule before saving.

Changes your account or connected service

Apply signatures to Gmail

signaturebuddy_apply_signatures

Publish today's saved signatures to connected Gmail mailboxes. Overwrites the current Gmail signatures; confirm the intended account and people first. Returns each mailbox's updated, unchanged, skipped or failed result.

Changes your account or connected service

Set daily auto-apply

signaturebuddy_set_auto_apply

Enable or disable daily publication of this account's saved signature schedule. Enabling allows the next daily job to overwrite connected Gmail signatures.

Changes your account or connected service

List Workspace people

signaturebuddy_list_directory

Read people in this account's connected Google Workspace directory. Requires an existing Workspace connection.

Read only

A useful first request

Start with a read
Check my Signature Buddy account status and show me the stored signature schedule. Do not make changes yet.

When you are ready to make changes, ask your assistant to show the proposed schedule and confirm the affected people before publishing. Applying signatures writes to connected Gmail accounts.

Authentication and account boundaries

Use your customer account key, stored in Account & image hosting in the editor. All calls run in that account. Active subscription and provider setup requirements are the same as the API. Keep keys in the client’s secret settings, and avoid pasting them into shared chats or source control.

Protocol support

The endpoint accepts MCP JSON-RPC over HTTP POST. It supports initialize, tools/list and tools/call, with protocol versions 2025-11-25, 2025-06-18 and 2025-03-26. Responses are JSON; persistent SSE sessions are not required. /mcp is also available as an alias.

For payload schemas, deployment prerequisites and API examples, see the REST API guide.