brk_mcp 0.11.2

A stateless MCP bridge to BRK's Cloudflare-cached REST API
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

# brk_mcp

`brk_mcp` is a thin, stateless, read-only MCP adapter for the BRK REST API. It
exposes the generated OpenAPI operations as MCP tools and forwards every tool
call to the configured public REST origin as a `GET` request.

The official public endpoint is
[mcp.bitview.space](https://mcp.bitview.space/). It is stateless, read-only, and
requires no authentication.

## Caching model

`brk_mcp` does not cache API responses or retain MCP sessions. Point it at the
public Cloudflare-fronted REST origin so its upstream `GET` requests use the
existing Cloudflare cache:

```text
MCP client -> brk_mcp -> Cloudflare-cached REST API -> BRK server
```

Cloudflare does not need to cache the MCP endpoint. The MCP catalog TTL is
only a standard client-side cache hint for the static discovery and tool-list
metadata.

## Run

From the workspace:

```sh
cargo run --bin brk_mcp -- bitview.space
```

Or run an installed binary:

```sh
brk_mcp bitview.space
```

A bare host tries HTTPS first and retries over HTTP only if the HTTPS request
fails at the transport layer. An explicit origin uses only that origin:

```sh
brk_mcp http://127.0.0.1:3110
```

The Streamable HTTP endpoint is `http://127.0.0.1:3111/` by default. If that
port is unavailable, the server tries each port through `3211`. The server
supports MCP protocol version `2026-07-28`.

The REST URL or host is the only configuration. It must be an HTTP(S) origin
without a path, query, or credentials.

## Generated catalog

The tool catalog is generated from the canonical OpenAPI document by
`brk_bindgen` and embedded in the binary at compile time from
`generated/manifest.json`. Do not edit the generated manifest by hand; rerun
the BRK bindgen target after changing the API.