usd_gbp — Boe Uk MCP Tool
usd_gbp
(usd gbp) is one of 42 tools on the
Boe Uk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call usd_gbp from your client
- Claude Code Boe Uk usd_gbp run in your project directory
- Claude Desktop Boe Uk usd_gbp ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Boe Uk usd_gbp ~/.cursor/mcp.json
- VS Code Boe Uk usd_gbp .vscode/mcp.json
- Zed Boe Uk usd_gbp ~/.config/zed/settings.json
- Windsurf Boe Uk usd_gbp ~/.codeium/windsurf/mcp_config.json
- Cline Boe Uk usd_gbp ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Boe Uk usd_gbp ~/.gemini/settings.json
- Grok Boe Uk usd_gbp .mcp.json (in your project root)
- ChatGPT Boe Uk usd_gbp Settings → Connectors → Advanced → Developer mode
- Claude.ai Boe Uk usd_gbp Settings → Connectors → Add custom connector
- LangChain Boe Uk usd_gbp pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http boe-uk https://gateway.pipeworx.io/boe-uk/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- get_series
- bank_rate
- sonia
- eur_gbp
- list_known_series
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.