get_vendor_profile — VendorWatch MCP Tool Read-only
get_vendor_profile
(get vendor profile) is one of 4 tools on the
VendorWatch
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_vendor_profile from your client
- Claude Code VendorWatch get_vendor_profile run in your project directory
- Claude Desktop VendorWatch get_vendor_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VendorWatch get_vendor_profile ~/.cursor/mcp.json
- VS Code VendorWatch get_vendor_profile .vscode/mcp.json
- Zed VendorWatch get_vendor_profile ~/.config/zed/settings.json
- Windsurf VendorWatch get_vendor_profile ~/.codeium/windsurf/mcp_config.json
- Cline VendorWatch get_vendor_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VendorWatch get_vendor_profile ~/.gemini/settings.json
- Grok VendorWatch get_vendor_profile .mcp.json (in your project root)
- ChatGPT VendorWatch get_vendor_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai VendorWatch get_vendor_profile Settings → Connectors → Add custom connector
- LangChain VendorWatch get_vendor_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vendorwatch https://vendor.watch/api/v1/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 6 October 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.