xbbg MCP

Stdio MCP server for Bloomberg request/response workflows backed byxbbg-async.

This binary is intended for coding agents such as Claude Code and OpenCode that can launch a local MCP server process and call tools over stdio.

The current server exposes request/response tools only:

- bdp- reference data
- bdh- historical data
- bds- bulk data
- bdib- intraday bars
- bql- Bloomberg Query Language
- bsrch- Bloomberg search
- bflds- field metadata lookup
- check_entitlements- entitlement-ID check for a Bloomberg service
- request- generic raw/custom request path

Responses are returned as bounded structured JSON with Arrow schema metadata so an agent can inspect the shape without receiving an unbounded payload.

Setreturn_eids: trueonly on routes backed by Bloomberg operations that supportreturnEids:

The dedicatedbdp,bds,bdh, andbdibtools advertisereturn_eidsdirectly. Use the genericrequesttool for intraday ticks:

{ "service": "//blp/refdata", "operation": "IntradayTickRequest", "extractor": "intraday_tick", "security": "AAPL US Equity", "start_datetime": "2024-01-15T09:30:00", "end_datetime": "2024-01-15T10:00:00", "event_types": ["TRADE"], "return_eids": true }

Bounded results expose the EID map as structured JSON atmetadata["xbbg.eid_data"], alongsideschema,row_count,returned_rows,truncated, androws. Pass the collected IDs to the read-onlycheck_entitlementstool;servicedefaults to//blp/refdata:

{ "eids": [101, 202], "service": "//blp/refdata" }

The check result includesservice,eids,entitled, andfailed_eids.

For macOS arm64 and Linux amd64, install the latest wrapper + binary pair with:

curl -fsSL https://raw.githubusercontent.com/xbbg-org/xbbg/main/scripts/install-xbbg-mcp.sh | sh

curl -fsSL https://raw.githubusercontent.com/xbbg-org/xbbg/main/scripts/install-xbbg-mcp.sh | sh -s -- 1.0.0

The installer places two files in~/.local/bin/by default:

- xbbg-mcp- launcher wrapper
- xbbg-mcp-real- compiled binary

GitHub release assets include only the launcher wrapper and compiled xbbg binary. They donotinclude Bloomberg SDK files or the Bloomberg runtime. You must provide those locally from a source you are authorized to use under your Bloomberg agreements and entitlements.

GitHub Release tar/zip assets remain the raw binary channel. The MCPB asset is the directory and one-click local connector channel for MCPB-aware clients and registries.

The wrapper locates the Bloomberg runtime in this order:
- XBBG_MCP_LIB_DIR
- BLPAPI_LIB_DIR
- BLPAPI_ROOT
- locally staged authorized SDK undervendor/blpapi-sdk/
- the official Pythonblpapipackage

If you install Bloomberg's Python package, the wrapper can usually run without any extra shell configuration:

pip install blpapi --index-url https://blpapi.bloomberg.com/repository/releases/python/simple/

Windows release assets are attached as.zipfiles, but the convenience installer currently targets macOS/Linux only.

Claude Desktop and MCPB-aware registries can use thexbbg-mcp-v<VERSION>.mcpbasset attached to GitHub Releases. The MCPB currently supports macOS arm64, Linux amd64, and Windows amd64. The raw platform tar/zip assets remain available for manual installs and troubleshooting.

The MCPB does not include Bloomberg SDK files, Bloomberg runtime libraries, credentials, or market data. ConfigureXBBG_MCP_LIB_DIR,BLPAPI_LIB_DIR,BLPAPI_ROOT, or install Bloomberg's official Pythonblpapipackage so the launcher can find the authorized Bloomberg runtime locally. On Windows, the MCPB PowerShell launcher prepends the resolved Bloomberg runtime directory toPATHbefore startingxbbg-mcp.exe.

bash ./scripts/sdktool.sh cargo build --release -p xbbg-mcp --locked ./scripts/xbbg-mcp

claude mcp add --transport stdio xbbg -- ~/.local/bin/xbbg-mcp

{ "$schema": "https://opencode.ai/config.json", "mcp": { "xbbg": { "type": "local", "command": ["/Users/you/.local/bin/xbbg-mcp"], "enabled": true } } }

Official MCP Registry: publish the generatedserver.jsonafter the release contains the.mcpbasset.

GitHub MCP Registry: verify the server appears after official registry ingestion.

Claude Connectors Directory: submit the MCPB as a desktop extension; remote connector submission is not the default for Bloomberg-local workflows.

Glama: verify indexing after official registry publication; if automated sandbox build cannot run without Bloomberg runtime, keep the listing metadata-focused.

PulseMCP: wait for official registry ingestion or use the Pulse submit page.

MCP.so: submit the GitHub repo/release after canonical registry metadata is live.

xbbg-mcpaccepts the same engine-oriented connection settings as the Rust core, with MCP-prefixed names taking precedence where available.

- XBBG_MCP_HOST/XBBG_HOST
- XBBG_MCP_PORT/XBBG_PORT
- XBBG_MCP_AUTH_METHOD/XBBG_AUTH_METHOD
- XBBG_MCP_APP_NAME
- XBBG_MCP_DIR_PROPERTY
- XBBG_MCP_USER_ID
- XBBG_MCP_IP_ADDRESS
- XBBG_MCP_TOKEN
- XBBG_MCP_REQUEST_POOL_SIZE
- XBBG_MCP_MAX_ROWS
- XBBG_MCP_MAX_STRING_CHARS

xbbg-mcpruns locally as a stdio MCP server. It does not send telemetry or usage data to xbbg-org, GitHub, Anthropic, Smithery, Glama, or any other third party.

Tool calls are handled on the user's machine and forwarded only to the Bloomberg runtime/API endpoint configured by the user (XBBG_MCP_HOST/XBBG_HOST, defaultlocalhost:8194) under that user's Bloomberg agreements and entitlements. Results are returned only to the MCP client process that launched the server.

Bloomberg validates entitlements at request time, including per-security and per-field access. A valid local session can still return empty or partial results when the user's DAPI, SAPI/B-PIPE, or ZFP entitlement set does not cover the requested data.

The server reads configuration from environment variables and does not persist request data, credentials, or Bloomberg responses to disk.

After building locally, verify the stdio handshake and a few live requests with:

uv run python -X utf8 scripts/xbbg_mcp_smoke.py

That script expects a live Bloomberg connection and a locally builttarget/debug/xbbg-mcpbinary, ortarget/release/xbbg-mcpif no debug build is present.

Bridge Town is an MCP-native, git-versioned financial modeling platform for FP&A teams and finance leaders. AI agents use Bridge Town tools to create projects, write Python model files, run models in isolated cloud sandboxes, query data, write outputs to Google Sheets, create dashboards, branch scenarios, and collaborate with teammates.

The Capital.com MCP Server lets your AI assistant talk to your trading account directly. Market data, position checks, trade previews – all in plain language, without leaving your AI tool.

Coinrule Agentic Trading MCP enables investors to create, backtest, execute, and manage trading agents through natural language across stocks, crypto and ETFs

Invest with Claude and other AI assistants

Australian Consumer Data Right Product Data

Remote MCP server for historical crypto & prediction-market data: search ~500K instruments, live market stats (OHLC, turnover, spreads, depth, slippage) and tick-data purchase. Keyless for catalog & stats; optional OAuth for account tools. Endpoint: https://cryptostruct.com/mcp

Cross-border debt collection from your AI assistant: check cases, get pricing, submit new cases.

Read-only MCP server for your Evibe investment portfolio + live market data (holdings, performance, dividends, benchmarks, screeners). Works with Claude & ChatGPT.

Financial and quantitative modeling engine for AI agents. Typed, named, deterministic.