estimate_cost — BridgeNode MCP MCP Prompt
estimate_cost
is one of 1 prompt on the
BridgeNode MCP
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke estimate_cost from your client
- Claude Code BridgeNode MCP Prompt/estimate_cost run in your project directory
- Claude Desktop BridgeNode MCP Prompt/estimate_cost ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BridgeNode MCP Prompt/estimate_cost ~/.cursor/mcp.json
- VS Code BridgeNode MCP Prompt/estimate_cost .vscode/mcp.json
- Zed BridgeNode MCP Prompt/estimate_cost ~/.config/zed/settings.json
- Windsurf BridgeNode MCP Prompt/estimate_cost ~/.codeium/windsurf/mcp_config.json
- Cline BridgeNode MCP Prompt/estimate_cost ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BridgeNode MCP Prompt/estimate_cost ~/.gemini/settings.json
- Grok BridgeNode MCP Prompt/estimate_cost .mcp.json (in your project root)
- ChatGPT BridgeNode MCP Prompt/estimate_cost Settings → Connectors → Advanced → Developer mode
- Claude.ai BridgeNode MCP Prompt/estimate_cost Settings → Connectors → Add custom connector
- LangChain BridgeNode MCP Prompt/estimate_cost pip install langchain-mcp-adapters
BridgeNode MCP also offers 1 resource — data you attach as context, where a prompt is something you run.
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.