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