Integrations
Sig.Surf MCP server
An assistant asked to make an email signature can finish the job with Sig.Surf through MCP, with no account for the basics.
Signatures made through this interface are for Gmail and Google Workspace.
Connection
The server is at https://sig.surf/mcp and uses Streamable HTTP. It is stateless.
Tools
| Tool | Needs sign-in or an API key | What it does |
|---|---|---|
create_signature | No | Creates a signature from a template or document and returns HTML plus a claim link; when signed in, saves it to the account |
get_signature | No, with the claim token | Reads a signature you created, or one saved in your account |
update_signature | No, with the claim token | Edits a signature you created, or one saved in your account |
list_templates | No | Lists the template catalogue |
list_signatures | Yes | Lists the signatures saved in your account |
list_employees | Yes: an owner or admin, or an API key | Lists employees in your organization |
create_employee | Yes: an owner or admin, or an API key | Adds an employee |
update_employee | Yes: an owner or admin, or an API key | Edits an employee |
Signing in
- Assistants that support MCP authorization (OAuth 2.1) can connect to your Sig.Surf account: you sign in with Google and approve what the assistant may do. It can never do more than you can.
- Signature access covers your own saved signatures. Employee access is offered only to owners and admins.
- Servers can use an API key as a bearer token instead.
- Details for client developers are on the API page.
Limits today
- OAuth sign-in has been tested with the official MCP SDK client, not yet with every assistant.
- There are no campaign tools.
The same operations are available over the REST API.
This page is also available as Markdown.