About TimeBase
TimeBase MCP is an MCP server for coding agents to explore and query TimeBase. It runs locally over stdio or can be deployed as a shared remote HTTP service for multiple users.
Key features
- 01List streams and read schemas
- 02Inspect symbols and preview messages
- 03Run QQL queries
- 04Check server status and activity
- 05Support local and remote deployment
Use cases
- 01Explore available TimeBase streams
- 02Inspect schemas and symbol definitions
- 03Preview messages or run QQL queries
- 04Connect to TimeBase through a shared HTTP service
MCP support
The server exposes TimeBase streams, schemas, symbols, message previews, QQL queries, and status and activity information to MCP clients. Clients can connect through a local stdio process or a remote HTTP service.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx timebase-mcpTIMEBASE_URLTimeBase native connection URL.TIMEBASE_SERVERSMulti-server config as a JSON array string or path to a JSON file.TIMEBASE_USERNAMEUsername for basic auth or oauth2_client_credentials.TIMEBASE_PASSWORDSecretPassword for basic auth.TIMEBASE_OAUTH2_TOKEN_URLSecretOAuth2 token endpoint for service-account client credentials.TIMEBASE_OAUTH2_CLIENT_IDSecretOAuth2 client ID for service-account or interactive login.TIMEBASE_OAUTH2_CLIENT_SECRETSecretOAuth2 client secret for service-account auth.TIMEBASE_OAUTH2_SCOPESecretOAuth2 scope(s) for service-account or interactive login.MCP_LOG_LEVELLog level: DEBUG, INFO, WARNING, ERROR, or CRITICAL.TIMEBASE_AUTH_MODESecretOutbound auth: auto, none, basic, oauth2_client_credentials, interactive.MCP_HOSTLoopback host for interactive OAuth redirect in stdio mode.MCP_PORTLoopback port for interactive OAuth redirect in stdio mode.MCP_AUTH_PUBLIC_URLSecretPublic HTTPS URL of this MCP endpoint (e.g. https://mcp.example.com/mcp).MCP_AUTH_AUDIENCESecretExpected JWT audience for inbound IdP auth.MCP_AUTH_API_KEYS_FILESecretPath to a hashed API-key store for inbound bearer-key auth.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
16Saved tool list · updated 6d ago
This tool takes no parameters.
Details
From the project READMETimeBase 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-mcpas a local process (stdio) that connects to your TimeBase. - Remotely, you deploy
timebase-mcpas 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.