TimeBase MCP
TimeBase MCP is a Model Context Protocol server that gives AI assistants direct access to your TimeBase instance — list streams, inspect schemas, run QQL queries, and reason over results from the chat.
MCP works with many AI tools (Claude Code, Cursor, VS Code, Claude Desktop) and supports several installation methods. The README covers all combinations in detail. This walkthrough picks one concrete path — uv as the package manager, TimeBase running in Kubernetes, and Claude Code as the AI client — so you can follow along step by step. The same approach applies to other setups.
Install
Run this on your local machine — the MCP server sits between your AI client and TimeBase, so it belongs on the developer's workstation, not on any server.
Replace `[user]` and `[password]` with your Deltix software repository credentials provided to you by our support.uv tool install -p 3.14 --index "https://[user]:[password]@nexus.deltixhub.com/repository/epm-rtc-public-python/simple" --from "timebase-mcp[enterprise]" timebase-mcp
Then register it with Claude Code:
claude mcp add timebase-mcp --transport stdio \
--env TIMEBASE_URL='dxtick://localhost:8011' \
-- timebase-mcp
Improve query accuracy (a must)
Install TimeBase Agent Plugins alongside MCP. It adds a QQL Generator skill that uses live schema context to produce more accurate queries.
For Claude Code, run these three commands in the chat:
/plugin marketplace add git@github.com:epam/TimeBase-Agent-Plugins.git
/plugin install timebase@timebase-plugins
/reload-plugins
For other AI tools, see the installation instructions in the plugin README.
Connect to a remote TimeBase
If TimeBase runs in Kubernetes, forward its ports before using the MCP server.
Remote TimeBase usually communicates over port `8011`. Let's provide it locally to our MCP:kubectl port-forward pod/timebase-0 8011:8011 -n krci-dl-dev
Leave that terminal open. The MCP server connects to dxtick://localhost:8011 as if TimeBase were local.
Try it!
With MCP connected and port forwarding active, ask your assistant something like:
❯ How is data in timebase today? how does it look compared to yesterday?
Called timebase-mcp 4 times (ctrl+o to expand)
● Today looks clean and busier than yesterday.
UTC time CH0 msgs CH1 msgs Notes
────────── ────────── ────────── ──────────────────────────────────
02:30 1,666 1,701 Feed starts ~02:09 (normal)
03:00 900 900 ✓ No gap
03:30 1,892 1,999
04:00–06:30 ~900/slot ~900/slot Heartbeats (no London pre-open today)
07:00 1,879 1,884 Pre-open
07:30 214,367 223,334 ← Main market open
08:00 164,466 208,966
08:30 155,302 194,838
09:00 141,894 166,574
09:30 130,648 171,910
10:00 122,762 166,985
10:30 175,877 229,331 Mid-morning pickup
11:00 109,379 154,007
11:30 103,175 160,151
12:00–13:30 99k–136k 158k–202k Sustained afternoon
14:00 335,499 470,900 ← Biggest spike of the week
14:30 18,238 23,386 (stream ends ~14:01, spike still settling)
vs yesterday (Monday):
- No XLON pre-open burst at 06:30 (yesterday had ~8.5k msgs there)
- Midday is more sustained — yesterday dipped to 61k at 11:00, today it's holding 100k–160k
- The 14:00 spike is significantly larger: 335k/471k today vs 215k/256k yesterday
- CHANNEL_1 is notably more active today, driven by XMIL (Milan) and XDUB (Dublin) instruments
No gaps, normal start time, and the highest per-bucket volumes we've seen all week. The 471k bucket on CHANNEL_1 at 14:00
The assistant will locate the right stream, scope the query to today, and run QQL to find the answer.
Feedback
Both the MCP server and the Agent Plugins are in active development. If something doesn't work, you have a feature request, or you just want to share what you built — open an issue on GitHub.