Developer · Local MCP server
TimeBase
Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.epam/TimeBase-MCP- Version
- 0.2.5
- Status
- Active
- Category
- developer
- Transport
- stdio (local process), Streamable HTTP
- Package
- PyPI, OCI image (Docker)
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- epam (GitHub)
- Website
- github.com/epam/TimeBase-MCP
- Repository
- github.com/epam/TimeBase-MCP
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | timebase-mcp | 0.2.5 | stdio |
| OCI image (Docker)runtime: docker | ghcr.io/epam/timebase-mcp:0.2.5 | — | HTTP |
How to connect TimeBase
TimeBase runs locally from a Python package published to PyPI: timebase-mcp version 0.2.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx timebase-mcp. It reads these environment variables: TIMEBASE_URL, TIMEBASE_SERVERS, TIMEBASE_USERNAME, TIMEBASE_PASSWORD (secret), TIMEBASE_OAUTH2_TOKEN_URL, TIMEBASE_OAUTH2_CLIENT_ID, TIMEBASE_OAUTH2_CLIENT_SECRET (secret), TIMEBASE_OAUTH2_SCOPE, MCP_LOG_LEVEL, TIMEBASE_AUTH_MODE, MCP_HOST and MCP_PORT; set them in the client's configuration for this server.
TimeBase runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/epam/timebase-mcp:0.2.5. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names docker as the runtime). It reads these environment variables: TIMEBASE_URL, TIMEBASE_SERVERS, TIMEBASE_USERNAME, TIMEBASE_PASSWORD (secret), TIMEBASE_OAUTH2_TOKEN_URL, TIMEBASE_OAUTH2_CLIENT_ID, TIMEBASE_OAUTH2_CLIENT_SECRET (secret), TIMEBASE_OAUTH2_SCOPE, MCP_LOG_LEVEL, TIMEBASE_AUTH_MODE, MCP_AUTH_PUBLIC_URL, MCP_AUTH_AUDIENCE and MCP_AUTH_API_KEYS_FILE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"timebase-mcp": {
"command": "uvx",
"args": [
"timebase-mcp"
],
"env": {
"TIMEBASE_URL": "<value>",
"TIMEBASE_SERVERS": "<value>",
"TIMEBASE_USERNAME": "<value>",
"TIMEBASE_PASSWORD": "<secret>",
"TIMEBASE_OAUTH2_TOKEN_URL": "<value>",
"TIMEBASE_OAUTH2_CLIENT_ID": "<value>",
"TIMEBASE_OAUTH2_CLIENT_SECRET": "<secret>",
"TIMEBASE_OAUTH2_SCOPE": "<value>",
"MCP_LOG_LEVEL": "<value>",
"TIMEBASE_AUTH_MODE": "<value>",
"MCP_HOST": "<value>",
"MCP_PORT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| TildeYour AI agents' home directory — privacy-first MCP server for portable AI identity. | Local · stdio |
| Time ManagementRead your Pyunto Time Management schedule and log time from an AI assistant. E2EE project planning. | Local · stdio |
| Time MCP ServerGet the current UTC time in RFC 3339 format. | Local · stdio |
| Time MCP ServerMCP server for timezone conversions and time queries with support for IANA timezones. | Local · stdio |
| TimebookTrack time on usetimebook.com - start/stop timers, log entries, list projects/clients. | Remote & Local · HTTP, stdio |
| TimestampMCP server for timestamp conversion — Unix, ISO 8601, relative time. | Local · stdio |
| Timeweaver MCPSynthetic time-series test data with trend, seasonality, noise, and anomalies, for any MCP client. | Local · stdio |
| TimpsPersistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools. | Local · stdio |