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-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
1 maintainer
Metadata
1 maintainer
Release files for timebase-mcp 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| timebase_mcp-0.2.4.tar.gz | 77.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| timebase_mcp-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 186.4 kB
Release files / timebase_mcp-0.2.4.tar.gz
| Download URL | timebase_mcp-0.2.4.tar.gz |
|---|---|
| Size | 77.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b61ef8d14107f0daa4094c209dd51212310154f95c1fbf1b396e090708fcc6d
|
|
BLAKE2b-256 checksum How to use checksums |
39876f435907256ac4328e085350b5bd6b77f89fccfac447918270edc462c998
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / timebase_mcp-0.2.4-py3-none-any.whl
| Download URL | timebase_mcp-0.2.4-py3-none-any.whl |
|---|---|
| Size | 109.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6195bbd3c4139f000f896bb3b5ab0e6f1e993b4d427e3a563d61139eb480f4c
|
|
BLAKE2b-256 checksum How to use checksums |
b1f5d17d2d632f7b237348980678a595c07e32db2feebafee8f1224158f6a03f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logSecurity for timebase-mcp 0.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for timebase_mcp-0.2.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
