export_user — SignOps MCP Tool Read-only
export_user
(export user) is one of 23 tools on the
SignOps
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call export_user from your client
- Claude Code SignOps export_user run in your project directory
- Claude Desktop SignOps export_user ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SignOps export_user ~/.cursor/mcp.json
- VS Code SignOps export_user .vscode/mcp.json
- Zed SignOps export_user ~/.config/zed/settings.json
- Windsurf SignOps export_user ~/.codeium/windsurf/mcp_config.json
- Cline SignOps export_user ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SignOps export_user ~/.gemini/settings.json
- Grok SignOps export_user .mcp.json (in your project root)
- ChatGPT SignOps export_user Settings → Connectors → Advanced → Developer mode
- Claude.ai SignOps export_user Settings → Connectors → Add custom connector
- LangChain SignOps export_user pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http signops https://api.signops.dev/mcpOther tools on this server
- send_push
- get_push
- list_pushes
- cancel_push
- register_device
- list_devices
- remove_device
- list_topics
- subscribe_topic
- unsubscribe_topic
- list_templates
- get_template
- save_template
- delete_template
- create_approval
- get_approval
- cancel_approval
- list_passkeys
- get_authenticator
- remove_authenticator
- unlock_user
- get_consent
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.