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