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