Skip to main content
Glama
epam

TimeBase MCP

Official
by epam
README.md
# 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) |
| Add optional WebAdmin inspection | [Add WebAdmin access](docs/webadmin-setup.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

A3.7/5.0

Scored across 16 tools

Disambiguation4/5

Most tools target distinct resources and actions, but get_stream_time_range vs get_stream_space_time_range and get_server_configuration vs get_timebase_status have subtle overlaps that could cause occasional misselection.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern (e.g., list_streams, get_stream_schema, execute_query), with no mixed conventions.

Tool Count4/5

16 tools is slightly above the ideal range, but each tool maps to a specific TimeBase operation and the set remains well-scoped for querying and inspection.

Completeness4/5

The surface covers query execution, compilation, function listing, server status/activity, and stream metadata well, but lacks write operations or certain aggregate stream stats that could be expected.

Maintenance

ActivityActive
ResponsivenessUnresponsive