swiftsign_confirm_send — mcp MCP Tool
swiftsign_confirm_send
(swiftsign confirm send) 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_confirm_send from your client
- Claude Code mcp swiftsign_confirm_send run in your project directory
- Claude Desktop mcp swiftsign_confirm_send ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp swiftsign_confirm_send ~/.cursor/mcp.json
- VS Code mcp swiftsign_confirm_send .vscode/mcp.json
- Zed mcp swiftsign_confirm_send ~/.config/zed/settings.json
- Windsurf mcp swiftsign_confirm_send ~/.codeium/windsurf/mcp_config.json
- Cline mcp swiftsign_confirm_send ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp swiftsign_confirm_send ~/.gemini/settings.json
- Grok mcp swiftsign_confirm_send .mcp.json (in your project root)
- ChatGPT mcp swiftsign_confirm_send Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp swiftsign_confirm_send Settings → Connectors → Add custom connector
- LangChain mcp swiftsign_confirm_send 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.