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