explain_result — governance platform MCP Prompt

explain_result is one of 2 prompts on the governance platform MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke explain_result from your client

• Claude Code governance platform Prompt/explain_result run in your project directory
• Claude Desktop governance platform Prompt/explain_result ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor governance platform Prompt/explain_result ~/.cursor/mcp.json
• VS Code governance platform Prompt/explain_result .vscode/mcp.json
• Zed governance platform Prompt/explain_result ~/.config/zed/settings.json
• Windsurf governance platform Prompt/explain_result ~/.codeium/windsurf/mcp_config.json
• Cline governance platform Prompt/explain_result ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI governance platform Prompt/explain_result ~/.gemini/settings.json
• Grok governance platform Prompt/explain_result .mcp.json (in your project root)
• ChatGPT governance platform Prompt/explain_result Settings → Connectors → Advanced → Developer mode
• Claude.ai governance platform Prompt/explain_result Settings → Connectors → Add custom connector
• LangChain governance platform Prompt/explain_result pip install langchain-mcp-adapters

Other prompts on this server

• blueprint_guide

governance platform also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.