English Français العربية

TimeBase

Official registry Other

Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package timebase-mcp
Claude Code 
claude mcp add timebase -e 'TIMEBASE_URL=dxtick://localhost:8011' -e 'TIMEBASE_SERVERS=<TIMEBASE_SERVERS>' -e 'TIMEBASE_USERNAME=<TIMEBASE_USERNAME>' -e 'TIMEBASE_PASSWORD=<your timebase_password>' -e 'TIMEBASE_OAUTH2_TOKEN_URL=<TIMEBASE_OAUTH2_TOKEN_URL>' -e 'TIMEBASE_OAUTH2_CLIENT_ID=<TIMEBASE_OAUTH2_CLIENT_ID>' -e 'TIMEBASE_OAUTH2_CLIENT_SECRET=<your timebase_oauth2_client_secret>' -e 'TIMEBASE_OAUTH2_SCOPE=<TIMEBASE_OAUTH2_SCOPE>' -e 'MCP_LOG_LEVEL=INFO' -e 'TIMEBASE_AUTH_MODE=auto' -e 'MCP_HOST=127.0.0.1' -e 'MCP_PORT=8000' -- uvx timebase-mcp==0.2.7
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "timebase": {
            "command": "uvx",
            "args": [
                "timebase-mcp==0.2.7"
            ],
            "env": {
                "TIMEBASE_URL": "dxtick://localhost:8011",
                "TIMEBASE_SERVERS": "<TIMEBASE_SERVERS>",
                "TIMEBASE_USERNAME": "<TIMEBASE_USERNAME>",
                "TIMEBASE_PASSWORD": "<your timebase_password>",
                "TIMEBASE_OAUTH2_TOKEN_URL": "<TIMEBASE_OAUTH2_TOKEN_URL>",
                "TIMEBASE_OAUTH2_CLIENT_ID": "<TIMEBASE_OAUTH2_CLIENT_ID>",
                "TIMEBASE_OAUTH2_CLIENT_SECRET": "<your timebase_oauth2_client_secret>",
                "TIMEBASE_OAUTH2_SCOPE": "<TIMEBASE_OAUTH2_SCOPE>",
                "MCP_LOG_LEVEL": "INFO",
                "TIMEBASE_AUTH_MODE": "auto",
                "MCP_HOST": "127.0.0.1",
                "MCP_PORT": "8000"
            }
        }
    }
}

Environment variables

  • TIMEBASE_URL TimeBase native connection URL.
  • TIMEBASE_SERVERS Multi-server config as a JSON array string or path to a JSON file.
  • TIMEBASE_USERNAME Username for basic auth or oauth2_client_credentials.
  • TIMEBASE_PASSWORD secret Password for basic auth.
  • TIMEBASE_OAUTH2_TOKEN_URL OAuth2 token endpoint for service-account client credentials.
  • TIMEBASE_OAUTH2_CLIENT_ID OAuth2 client ID for service-account or interactive login.
  • TIMEBASE_OAUTH2_CLIENT_SECRET secret OAuth2 client secret for service-account auth.
  • TIMEBASE_OAUTH2_SCOPE OAuth2 scope(s) for service-account or interactive login.
  • MCP_LOG_LEVEL Log level: DEBUG, INFO, WARNING, ERROR, or CRITICAL.
  • TIMEBASE_AUTH_MODE Outbound auth: auto, none, basic, oauth2_client_credentials, interactive.
  • MCP_HOST Loopback host for interactive OAuth redirect in stdio mode.
  • MCP_PORT Loopback port for interactive OAuth redirect in stdio mode.
OCI package ghcr.io/epam/timebase-mcp:0.2.7
Claude Code 
claude mcp add timebase -e 'TIMEBASE_URL=dxtick://localhost:8011' -e 'TIMEBASE_SERVERS=<TIMEBASE_SERVERS>' -e 'TIMEBASE_USERNAME=<TIMEBASE_USERNAME>' -e 'TIMEBASE_PASSWORD=<your timebase_password>' -e 'TIMEBASE_OAUTH2_TOKEN_URL=<TIMEBASE_OAUTH2_TOKEN_URL>' -e 'TIMEBASE_OAUTH2_CLIENT_ID=<TIMEBASE_OAUTH2_CLIENT_ID>' -e 'TIMEBASE_OAUTH2_CLIENT_SECRET=<your timebase_oauth2_client_secret>' -e 'TIMEBASE_OAUTH2_SCOPE=<TIMEBASE_OAUTH2_SCOPE>' -e 'MCP_LOG_LEVEL=INFO' -e 'TIMEBASE_AUTH_MODE=auto' -e 'MCP_AUTH_PUBLIC_URL=<MCP_AUTH_PUBLIC_URL>' -e 'MCP_AUTH_AUDIENCE=<MCP_AUTH_AUDIENCE>' -e 'MCP_AUTH_API_KEYS_FILE=<MCP_AUTH_API_KEYS_FILE>' -- docker run -i --rm ghcr.io/epam/timebase-mcp:0.2.7
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "timebase": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/epam/timebase-mcp:0.2.7"
            ],
            "env": {
                "TIMEBASE_URL": "dxtick://localhost:8011",
                "TIMEBASE_SERVERS": "<TIMEBASE_SERVERS>",
                "TIMEBASE_USERNAME": "<TIMEBASE_USERNAME>",
                "TIMEBASE_PASSWORD": "<your timebase_password>",
                "TIMEBASE_OAUTH2_TOKEN_URL": "<TIMEBASE_OAUTH2_TOKEN_URL>",
                "TIMEBASE_OAUTH2_CLIENT_ID": "<TIMEBASE_OAUTH2_CLIENT_ID>",
                "TIMEBASE_OAUTH2_CLIENT_SECRET": "<your timebase_oauth2_client_secret>",
                "TIMEBASE_OAUTH2_SCOPE": "<TIMEBASE_OAUTH2_SCOPE>",
                "MCP_LOG_LEVEL": "INFO",
                "TIMEBASE_AUTH_MODE": "auto",
                "MCP_AUTH_PUBLIC_URL": "<MCP_AUTH_PUBLIC_URL>",
                "MCP_AUTH_AUDIENCE": "<MCP_AUTH_AUDIENCE>",
                "MCP_AUTH_API_KEYS_FILE": "<MCP_AUTH_API_KEYS_FILE>"
            }
        }
    }
}

Environment variables

  • TIMEBASE_URL TimeBase native connection URL.
  • TIMEBASE_SERVERS Multi-server config as a JSON array string or path to a JSON file.
  • TIMEBASE_USERNAME Username for basic auth or oauth2_client_credentials.
  • TIMEBASE_PASSWORD secret Password for basic auth.
  • TIMEBASE_OAUTH2_TOKEN_URL OAuth2 token endpoint for service-account client credentials.
  • TIMEBASE_OAUTH2_CLIENT_ID OAuth2 client ID for service-account or interactive login.
  • TIMEBASE_OAUTH2_CLIENT_SECRET secret OAuth2 client secret for service-account auth.
  • TIMEBASE_OAUTH2_SCOPE OAuth2 scope(s) for service-account or interactive login.
  • MCP_LOG_LEVEL Log level: DEBUG, INFO, WARNING, ERROR, or CRITICAL.
  • TIMEBASE_AUTH_MODE Outbound auth: auto, none, basic, oauth2_client_credentials, forward_identity.
  • MCP_AUTH_PUBLIC_URL Public HTTPS URL of this MCP endpoint (e.g. https://mcp.example.com/mcp).
  • MCP_AUTH_AUDIENCE Expected JWT audience for inbound IdP auth.
  • MCP_AUTH_API_KEYS_FILE Path to a hashed API-key store for inbound bearer-key auth.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. TimeBase MCP
  2. Which guide do I need?
  3. Documentation
  4. See also

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 | | Add optional WebAdmin inspection | Add WebAdmin access |

Documentation

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

See also

Frequently asked questions

What is TimeBase?

Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.

How do I install TimeBase?

It runs on your machine. In Claude Code: claude mcp add timebase -e 'TIMEBASE_URL=dxtick://localhost:8011' -e 'TIMEBASE_SERVERS=<TIMEBASE_SERVERS>' -e 'TIMEBASE_USERNAME=<TIMEBASE_USERNAME>' -e 'TIMEBASE_PASSWORD=<your timebase_password>' -e 'TIMEBASE_OAUTH2_TOKEN_URL=<TIMEBASE_OAUTH2_TOKEN_URL>' -e 'TIMEBASE_OAUTH2_CLIENT_ID=<TIMEBASE_OAUTH2_CLIENT_ID>' -e 'TIMEBASE_OAUTH2_CLIENT_SECRET=<your timebase_oauth2_client_secret>' -e 'TIMEBASE_OAUTH2_SCOPE=<TIMEBASE_OAUTH2_SCOPE>' -e 'MCP_LOG_LEVEL=INFO' -e 'TIMEBASE_AUTH_MODE=auto' -e 'MCP_HOST=127.0.0.1' -e 'MCP_PORT=8000' -- uvx timebase-mcp==0.2.7. For other clients, paste the JSON configuration from this page into their MCP settings.

Does TimeBase need an API key?

Yes. It expects TIMEBASE_PASSWORD, TIMEBASE_OAUTH2_CLIENT_SECRET, which you set in its configuration.

Is TimeBase open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains TimeBase?

It is published by epam. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.