ofgem_price_cap — Ofgem MCP Tool
ofgem_price_cap
(ofgem price cap) is one of 39 tools on the
Ofgem
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ofgem_price_cap from your client
- Claude Code Ofgem ofgem_price_cap run in your project directory
- Claude Desktop Ofgem ofgem_price_cap ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ofgem ofgem_price_cap ~/.cursor/mcp.json
- VS Code Ofgem ofgem_price_cap .vscode/mcp.json
- Zed Ofgem ofgem_price_cap ~/.config/zed/settings.json
- Windsurf Ofgem ofgem_price_cap ~/.codeium/windsurf/mcp_config.json
- Cline Ofgem ofgem_price_cap ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ofgem ofgem_price_cap ~/.gemini/settings.json
- Grok Ofgem ofgem_price_cap .mcp.json (in your project root)
- ChatGPT Ofgem ofgem_price_cap Settings → Connectors → Advanced → Developer mode
- Claude.ai Ofgem ofgem_price_cap Settings → Connectors → Add custom connector
- LangChain Ofgem ofgem_price_cap pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ofgem https://gateway.pipeworx.io/ofgem/mcp
Other 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
- ofgem_datasets
- ofgem_dataset_rows
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.