# MCP server

Connect Codex, Claude, ChatGPT, Grok and other AI agents to your q-bitf data.

The q-bitf MCP server lets an AI assistant read your q-bitf data, so you can
ask it things like "where are the ES walls and is price above the flip?". It
is read-only: the assistant cannot trade, change your account or see your
billing, journal or broker connections.

**The easiest path is [Agent setup](https://q-bitf.com/mcp).** It has current instructions for
Codex, Claude and Claude Code, ChatGPT, Grok, Hermes, OpenClaw, Cursor and
generic MCP clients, plus copyable setup prompts and the portable q-bitf skill.

```
https://api.q-bitf.com/mcp
```

MCP needs an active **Pro** or **Ultra** plan and the q-bitf Discord member
role. Both are checked on every request.

## Connect with Clerk sign-in

Most assistants use Clerk OAuth in your browser. No key to copy. The MCP URL
must be exactly `https://api.q-bitf.com/mcp`: Clerk binds each access token to
that exact audience, and q-bitf rejects a token issued for any other URL.

- **Codex**:

```
codex mcp add qbitf --url https://api.q-bitf.com/mcp
codex mcp login qbitf
```

- **Claude** (web and desktop): **Settings → Connectors → Add custom
  connector**, paste the address above, click **Connect**, complete the Clerk
  sign-in and approve.
- **ChatGPT**: open **Plugins → + → Add custom MCP server**, paste the address
  above, choose OAuth, create it and sign in.
- **Claude Code**:

```
claude mcp add --transport http qbitf https://api.q-bitf.com/mcp
```

  Then run `/mcp` and choose q-bitf to sign in.
- **Grok**: open **grok.com/connectors → New Connector → Custom**, paste the
  address above, choose OAuth and connect.
- **Hermes**:

```
hermes mcp add --url https://api.q-bitf.com/mcp --auth oauth qbitf
hermes mcp test qbitf
```

- **OpenClaw**:

```
openclaw mcp set qbitf '{"url":"https://api.q-bitf.com/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login qbitf
openclaw mcp doctor qbitf --probe
```

- **Cursor**: add this to `~/.cursor/mcp.json`, then sign in when asked.

```
{ "mcpServers": { "qbitf": { "url": "https://api.q-bitf.com/mcp" } } }
```

Clerk shows the sign-in and consent screen. Only approve an app you just added
yourself. Revoke a Clerk OAuth grant from the AI client or your account security
settings; the q-bitf connection list below is for fallback keys and older
connections.

## Connect with a key

For apps without browser sign-in, create an **MCP key** in **Settings →
Platforms & API keys → AI assistants (MCP)** and send it as a bearer header.
The key is shown once. You can have up to five.

```
{
  "mcpServers": {
    "qbitf": {
      "type": "http",
      "url": "https://api.q-bitf.com/mcp",
      "headers": { "Authorization": "Bearer qbm_your_key" }
    }
  }
}
```

## Tools

| Tool | What it returns |
|---|---|
| `qbitf_levels` | The key levels, regime and bias for a symbol |
| `qbitf_exposure` | Net greek exposure, the strongest strikes per greek and the vol regime |
| `qbitf_gex_by_strike` | Call and put GEX, or today's traded positioning, per strike |
| `qbitf_order_flow` | How an exposure metric moved through the session |
| `qbitf_greek_map` | The interval map: exposure by strike and time |
| `qbitf_volatility_regime` | VIX term structure and the named vol regime |
| `qbitf_market_session` | Whether the market is open, and today's hours |
| `qbitf_dark_pool` | Weekly dark pool volume for a stock or ETF |
| `qbitf_economic_calendar` | Upcoming releases with impact ratings |
| `qbitf_symbols` | What q-bitf covers |

## Ready-made workflows

Compatible clients discover these as MCP prompts. The [portable q-bitf
skill](https://q-bitf.com/mcp/qbitf-agent-skill.md) also maps them to easy slash-style names.

| Workflow | What it does |
|---|---|
| `qbitf_coach` | Picks the smallest useful q-bitf workflow and a next check |
| `market_brief` | Session, levels, volatility and event context |
| `level_check` | Price versus the gamma flip and nearest walls |
| `gex_map` | The strongest gamma strikes around price |
| `greek_exposure` | Net gamma, delta, vanna and charm |
| `order_flow` | Exposure changes through the session |
| `volatility_regime` | VIX term structure and regime |
| `event_risk` | Upcoming high-impact releases |
| `dark_pool_context` | Delayed weekly off-exchange context |
| `symbol_coverage` | Supported symbols, frames and sources |
| `qbitf_report` | A structured factual report |

The earlier `morning_brief` prompt remains available for existing setups.

## Data timestamps

The assistant should show source timestamps when a tool returns them. Options-
chain inputs can lag by about 15 minutes, open interest is settled after the
close, and spot may be fresher. A client should not call a value real-time
unless its timestamp proves that.

## Limits

Each member can make 30 tool calls a minute and ask about a limited number of
different symbols per hour. Over the limit, the assistant is told to wait.

## Disconnect

Every connected app and key is listed under [Agent setup → Connection
management](https://q-bitf.com/mcp#connections). Disconnect one there and it stops working at
once.

> **Note:** Answers come from your AI assistant, which can make mistakes.
> Check the numbers in q-bitf before you trade on them.