should_i_bid — tenders MCP Prompt

should_i_bid is one of 3 prompts on the tenders MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke should_i_bid from your client

• Claude Code tenders Prompt/should_i_bid run in your project directory
• Claude Desktop tenders Prompt/should_i_bid ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor tenders Prompt/should_i_bid ~/.cursor/mcp.json
• VS Code tenders Prompt/should_i_bid .vscode/mcp.json
• Zed tenders Prompt/should_i_bid ~/.config/zed/settings.json
• Windsurf tenders Prompt/should_i_bid ~/.codeium/windsurf/mcp_config.json
• Cline tenders Prompt/should_i_bid ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI tenders Prompt/should_i_bid ~/.gemini/settings.json
• Grok tenders Prompt/should_i_bid .mcp.json (in your project root)
• ChatGPT tenders Prompt/should_i_bid Settings → Connectors → Advanced → Developer mode
• Claude.ai tenders Prompt/should_i_bid Settings → Connectors → Add custom connector
• LangChain tenders Prompt/should_i_bid pip install langchain-mcp-adapters

Other prompts on this server

• find_bids
• analyze_competitor

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.