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