boe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOE_MCP_HTTP_HOST | No | Bind host for HTTP mode. Use 0.0.0.0 to expose to network (behind reverse proxy or firewall). | 127.0.0.1 |
| BOE_MCP_HTTP_PORT | No | Enable HTTP mode on this port (e.g., 8080). If not set, stdio mode is used. | |
| BOE_CACHE_TTL_MINUTES | No | How long to cache BoE responses in memory (0 disables caching). | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_rateA | Get the current Bank of England base rate, the date it took effect, and how many whole months it has been held at this level. |
| get_rate_historyA | Get the last N Bank of England base rate changes: date, new rate, and the move in basis points vs the previous level (null for the earliest known entry). |
| get_rate_atA | Get the Bank of England base rate that was in force on a specific historical date, and when that level took effect. |
| get_rate_statsA | Get summary statistics of the Bank of England base rate over a date range: minimum and maximum (with the date each level first applied), the time-weighted average, and the rates in force at the start and end of the window with the net move in basis points. Both dates are optional — omit them for the full available history through today. The rate level in force on the start date counts even if it took effect earlier. |
| get_next_mpc_meetingA | Get the date of the next scheduled Bank of England Monetary Policy Committee announcement and the number of days until it. |
| get_mpc_datesA | Get every upcoming Bank of England Monetary Policy Committee announcement date on the published schedule (typically a year or more ahead), each with the number of calendar days until it. Use get_next_mpc_meeting when only the next date is needed. |
| list_seriesA | List a curated catalog of well-known Bank of England IADB statistical series (policy rates, market rates, exchange rates, household rates) with their code, name, description, unit and frequency. Use this to discover series codes to pass to get_series. get_series also accepts any other IADB code, not only these. |
| get_seriesA | Fetch observations for any Bank of England IADB statistical series by its code (e.g. IUDSOIA for SONIA, XUDLUSS for USD/GBP). Optionally restrict to a date range and cap how many of the most recent points are returned. Use list_series to discover codes; any valid IADB code works, not only catalogued ones. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: current rate, historical rate, rate changes, rate statistics, next MPC meeting, all MPC dates, series discovery, and series data. The descriptions explicitly clarify boundaries, such as using get_next_mpc_meeting when only the next date is needed.
All tool names follow a consistent verb_noun pattern in snake_case (get_rate_at, get_next_mpc_meeting). The only non-get tool is list_series, which is a standard verb for collection listing and fits the pattern well.
8 tools is well-scoped for a Bank of England data server, covering base rate queries, MPC meeting schedules, and statistical series. There is no unnecessary overlap or bloat.
The tool set provides comprehensive coverage for its domain: full base rate lifecycle (current, history, at-date, stats), all MPC meeting dates (next and full schedule), and series discovery plus arbitrary data retrieval. No obvious gaps exist.