swiftsign_send_from_template — mcp MCP Tool
swiftsign_send_from_template
(swiftsign send from template) is one of 10 tools on the
mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call swiftsign_send_from_template from your client
- Claude Code mcp swiftsign_send_from_template run in your project directory
- Claude Desktop mcp swiftsign_send_from_template ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp swiftsign_send_from_template ~/.cursor/mcp.json
- VS Code mcp swiftsign_send_from_template .vscode/mcp.json
- Zed mcp swiftsign_send_from_template ~/.config/zed/settings.json
- Windsurf mcp swiftsign_send_from_template ~/.codeium/windsurf/mcp_config.json
- Cline mcp swiftsign_send_from_template ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp swiftsign_send_from_template ~/.gemini/settings.json
- Grok mcp swiftsign_send_from_template .mcp.json (in your project root)
- ChatGPT mcp swiftsign_send_from_template Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp swiftsign_send_from_template Settings → Connectors → Add custom connector
- LangChain mcp swiftsign_send_from_template pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://swiftsign.ca/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.