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