TimeBase MCP
Official# TimeBase MCP
<!-- mcp-name: io.github.epam/TimeBase-MCP -->
A [Model Context Protocol](https://modelcontextprotocol.io/introduction) server that lets a coding agent (Claude Code, VS Code, Cursor, Claude Desktop, etc.) explore and query [TimeBase](https://kb.timebase.info): 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](https://github.com/epam/TimeBase-Agent-Plugins#quickstart) |
| Manual local setup | [Local setup](docs/local-setup.md) |
| Deploy a shared remote MCP server | [Remote deployment](docs/remote-deployment.md) |
| Connect to a running remote server | [Connect to a remote server](docs/connect-remote.md) |
## Documentation
| Topic | Go to |
| - | - |
| Updating | [Local setup: Updating](docs/local-setup.md#updating) |
| Troubleshooting | [Troubleshooting](docs/troubleshooting.md) |
| Reference | [Environment variables, auth, capabilities](docs/reference/README.md) |
## See also
- [TimeBase Agent Plugins](https://github.com/epam/TimeBase-Agent-Plugins)
TDQS
Scored across 15 tools
Most tools map cleanly to distinct resources and actions: streams, spaces, activity, QQL functions, and queries are all clearly separated. The only mild ambiguity is between get_server_configuration and get_timebase_status, though their descriptions clarify one is MCP runtime configuration and the other is TimeBase server status.
The tool names follow a consistent snake_case verb_noun pattern, with list_ for enumeration and get_ for single-resource retrieval. get_server_configuration is a slight semantic outlier because it refers to the MCP server runtime rather than the TimeBase server, breaking the otherwise predictable pattern.
15 tools is at the upper end of the well-scoped range, but each tool covers a distinct facet of TimeBase: instance discovery, status, activity, stream metadata, messages, and QQL query support. There is no obvious redundancy or padding.
The tool set thoroughly covers the read/query surface: streams, schemas, time ranges, spaces, symbols, messages, QQL compilation/execution, and server functions. However, there are no write or control operations such as creating/deleting streams, writing messages, or canceling active activity, so it is not a full TimeBase administration surface.