list_signature_templates — SignatureForever MCP Tool Read-only
list_signature_templates
(list signature templates) is one of 5 tools on the
SignatureForever
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_signature_templates from your client
- Claude Code SignatureForever list_signature_templates run in your project directory
- Claude Desktop SignatureForever list_signature_templates ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SignatureForever list_signature_templates ~/.cursor/mcp.json
- VS Code SignatureForever list_signature_templates .vscode/mcp.json
- Zed SignatureForever list_signature_templates ~/.config/zed/settings.json
- Windsurf SignatureForever list_signature_templates ~/.codeium/windsurf/mcp_config.json
- Cline SignatureForever list_signature_templates ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SignatureForever list_signature_templates ~/.gemini/settings.json
- Grok SignatureForever list_signature_templates .mcp.json (in your project root)
- ChatGPT SignatureForever list_signature_templates Settings → Connectors → Advanced → Developer mode
- Claude.ai SignatureForever list_signature_templates Settings → Connectors → Add custom connector
- LangChain SignatureForever list_signature_templates pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email-signatures https://signatureforever.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.