committee_member — tenders MCP Tool
committee_member
(committee member) is one of 22 tools on the
tenders
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call committee_member from your client
- Claude Code tenders committee_member run in your project directory
- Claude Desktop tenders committee_member ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor tenders committee_member ~/.cursor/mcp.json
- VS Code tenders committee_member .vscode/mcp.json
- Zed tenders committee_member ~/.config/zed/settings.json
- Windsurf tenders committee_member ~/.codeium/windsurf/mcp_config.json
- Cline tenders committee_member ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI tenders committee_member ~/.gemini/settings.json
- Grok tenders committee_member .mcp.json (in your project root)
- ChatGPT tenders committee_member Settings → Connectors → Advanced → Developer mode
- Claude.ai tenders committee_member Settings → Connectors → Add custom connector
- LangChain tenders committee_member pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tenders https://api.tobid.tw/mcpOther tools on this server
- search_tenders
- get_tender
- likely_bidders
- bid_strategy
- price_analysis
- vendor_report
- vendor_awards
- unit_report
- compare_vendors
- hot_opportunities
- find_entity
- procurement_forecast
- public_reading
- vendor_compliance
- evaluation_committee
- search_committee_members
- unit_committee
- vendor_committee
- framework_contracts
- subcontract_opportunities
- asset_sales
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.