Skip to main content
Glama
@pipeworx/mcp-bi-id

@pipeworx/mcp-bi-id

Official
by pipeworx-io
README.md
# @pipeworx/bi-id

Bank Indonesia statistics: the BI-Rate policy rate with its recent monthly decisions, the JISDOR rupiah-per-dollar reference rate by date, and the bank's buy/sell transaction rates for 23 currencies against the rupiah, each with units and the observation date.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1957+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

## Tools

- `bi_id_series_list()` — what the pack serves, the valid currency codes and the date rules. No upstream call.
- `bi_id_policy_rate()` — current BI-Rate (percent), the Board of Governors decision date, the change at the latest decision in basis points, and the latest ten monthly decisions with press-release links.
- `bi_id_jisdor({ date? | start_date?, end_date? })` — JISDOR USD/IDR reference rate; latest by default.
- `bi_id_exchange_rate({ currency?, date? | start_date?, end_date? })` — BI buying and selling rate, IDR per unit of the currency (per 100 for JPY); latest by default. A date with no publication returns `count: 0` and an `empty_reason`.

## Auth

Keyless.

## Data sources

- Bank Indonesia, BI-Rate (policy rate) decisions — the bank lists its latest ten monthly decisions; older ones are not available through this pack.
- Bank Indonesia, exchange-rate statistics — JISDOR and transaction rates. Each call reads live from the bank; nothing is stored.

Things worth knowing:

- No rate is published on weekends or Indonesian holidays; those dates come back as `no_publication_on_date`, not as zero or an error.
- The transaction rate for a date is derived from the previous business day's JISDOR (observed: mid of 2026-11-13 buy/sell equals JISDOR of 2026-11-12), so it lags JISDOR by one business day.
- Currencies outside the documented list return no rows upstream, which cannot be told apart from a holiday; the pack checks the code locally and names the valid list instead.
- Range queries are capped at 366 days.

## Quick Start

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

```json
{
  "mcpServers": {
    "bi-id": {
      "url": "https://gateway.pipeworx.io/bi-id/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/bi-id/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:

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

Both URLs reach the same gateway and the same 1957+ 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

```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/bi_id_series_list \
  -H 'Content-Type: application/json' \
  -d '{}'
```

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

## Run it from npm

`@pipeworx/mcp-bi-id` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/bi-id/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "bi-id": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-bi-id"]
    }
  }
}
```

Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.

It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.

## 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 Bi Id data" })
```

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

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT