The io.github.epam/TimeBase-MCP MCP server enables developers to explore and query TimeBase resources. It supports access to TimeBase streams, schemas, QQL, symbols, and server status through the Model Context Protocol (MCP), exposing these capabilities for integration into MCP-enabled tooling and workflows.

🛠️ Key Features

Explore TimeBase streams
Query TimeBase schemas
Use QQL for TimeBase queries
Access TimeBase symbols
Retrieve TimeBase server status

🚀 Use Cases

Query data using TimeBase QQL
Discover and inspect TimeBase streams and schemas
Look up TimeBase symbols
Check TimeBase server status from an MCP client

⚡ Developer Benefits

Centralizes TimeBase exploration and querying behind MCP
Uses standard MCP interactions for streams, schemas, QQL, symbols, and status

⚠️ Limitations

Detailed tool behavior, count, and configuration are not provided in the available server data

TimeBase MCP

A Model Context Protocol server that lets a coding agent (Claude Code, VS Code, Cursor, Claude Desktop, etc.) explore and query TimeBase: list streams, read schemas and symbols, preview messages, run QQL queries, and inspect server status and activity.

The server can run two ways:

Locally, your agent launches timebase-mcp as a local process (stdio) that connects to your TimeBase.
Remotely, you deploy timebase-mcp as a shared HTTP service that multiple users connect their agents to.

Which guide do I need?

You want to	Go to
Use TimeBase MCP locally (Cursor, VS Code, Claude Code/Desktop)	Agent Plugins Quickstart
Manual local setup	Local setup
Deploy a shared remote MCP server	Remote deployment
Connect to a running remote server	Connect to a remote server

Documentation

Topic	Go to
Updating	Local setup: Updating
Troubleshooting	Troubleshooting
Reference	Environment variables, auth, capabilities

TimeBase

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

TimeBase MCP

Which guide do I need?

Documentation

See also

Install

Configuration