Productivity
prosignature.co
Provides tools for generating email-safe HTML signatures, listing layouts and accent colors, quoting ProSignature pricing, and retrieving installation steps and product facts.
ENDPOINT 1
https://prosignature.co/mcp
MCP server metadata
- Name
- prosignature
- Version
- 1.0.0
ProSignature builds email signatures for Gmail and Google Workspace teams. Every tool here works without an account and changes nothing: create_signature returns the free plan's email-safe HTML (it carries a small "Created with ProSignature" credit line) plus an edit_url that opens the generator prefilled; quote_price computes list prices from https://prosignature.co/pricing.json; get_install_steps and get_facts answer honestly, including when ProSignature is not the right choice. Installing, logos, Pro and Teams start with the human signing up at https://prosignature.co/app — never create an account or enter payment details for them. Docs: https://prosignature.co/for-ai-agents
Known tools 5
create_signatureBuilds the email-safe HTML signature (table + inline styles, the same bytes as prosignature.
Potential side effectslist_layoutsThe four signature layouts (id, name, what it looks like) and the six accent colours the generator offers.
Inferred read-onlyquote_priceList price for Pro (one person) or Teams (per person, 5-person minimum, no platform fee) for a number of people, billed yearly or monthly, computed from the rules in https://prosignature.
Inferred read-onlyget_install_stepsHow a signature from create_signature gets into a mail client, honestly: Gmail web (paste, or the sendAs PATCH with gmail.
Inferred read-onlyget_factsWhat ProSignature is, the free plan and its credit line, Pro and Teams prices (verified 2026-10-18), how Gmail and Google Workspace installs work per person, personal links for employees, what the product is NOT (no mail-flow enforcement, no Microsoft 365 sync, no analytics), and where the docs, OpenAPI and pricing.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.prosignature]
url = "https://prosignature.co/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"prosignature": {
"type": "http",
"url": "https://prosignature.co/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: prosignature
Remote MCP URL: https://prosignature.co/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"prosignature": {
"url": "https://prosignature.co/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"prosignature": {
"type": "http",
"url": "https://prosignature.co/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "prosignature",
"transport": "streamable-http",
"url": "https://prosignature.co/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.