Skip to content
Conduit

mcp server

mcp-boe-uk

Bank of England Interactive Statistical Database (IADB) MCP.

pipeworx-io/mcp-boe-ukcommunitylistedunreviewed

Set up

Hosted by its author. Add the URL to your agent — nothing to install.

~/Library/Application Support/Claude/claude_desktop_config.json
Settings → Connectors → Add custom connector

Name: mcp-boe-uk
URL:  https://gateway.pipeworx.io/boe-uk/mcp

same format Cursor, GitHub Copilot CLI, Junie, JetBrains AI Assistant, Augment (Auggie CLI), Factory Droid, Kiro, Devin CLI +12

Values in angle brackets are placeholders. Restart Claude Desktop after editing its config.Claude Desktop docs

README

synced Oct 14, 2026

mcp-boe-uk

Bank of England Interactive Statistical Database (IADB) MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1819+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
get_seriesFetch one or more Bank of England IADB series by code over a date range. Requires BoE series codes (e.g. IUDBEDR = Bank Rate, IUDSOIA = SONIA, XUDLUSS = USD/GBP, XUDLERS = EUR/GBP). Use list_known_series or the convenience tools (bank_rate, sonia, usd_gbp, eur_gbp) if you do not know the code. Returns parsed JSON: one entry per series with observations [{date, value}].
bank_rateThe Bank of England's official Bank Rate: the current rate, the date it took effect, the previous rate and when that one took effect, plus recent decision history (series IUDBEDR) — not just a raw observations list to infer a decision date from. Also returns the last N daily observations.
soniaLatest N observations of SONIA, the Sterling Overnight Index Average (series IUDSOIA), most recent first.
usd_gbpLatest N observations of the USD/GBP spot rate — US$ per £1 (series XUDLUSS), most recent first.
eur_gbpLatest N observations of the EUR/GBP spot rate — € per £1 (series XUDLERS), most recent first.
list_known_seriesList the friendly BoE series codes this pack surfaces (Bank Rate, SONIA, USD/GBP, EUR/GBP) with their IADB codes.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "boe-uk": {
      "url": "https://gateway.pipeworx.io/boe-uk/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/boe-uk/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1819+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/boe_uk_get_series \
  -H 'Content-Type: application/json' \
  -d '{"series_codes":["IUDBEDR"],"from":"2024-01-01"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/boe_uk_get_series. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "boe-uk": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-boe-uk"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-boe-uk

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Boe Uk data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

↑↓ navigate openesc close