This release is a pre-release and may not be stable for production use.
tiretrack-mcp
MCP server for TireTrack project management. Manage projects, issues, sprints, and teams from any AI assistant that supports the Model Context Protocol.
The TireTrack Settings → MCP Server Setup page renders the exact config block for your environment and chosen client (Claude Code / Codex CLI / Gemini CLI). Use that as the canonical source — this README is a reference for offline setup.
Tools
| Category | Tools |
|---|---|
| Projects | list_projects, get_project, create_project |
| Members | list_project_members, add_project_member |
| Issues | list_issues, get_issue, get_issue_by_key, create_issue, update_issue |
| Comments | list_comments, add_comment |
| Sprints | list_sprints, get_sprint_metrics |
| Search | search_issues |
| Users | list_users, get_current_user |
Quick Start
Using uvx (recommended)
uvx tiretrack-mcp
Using pip
pip install tiretrack-mcp
tiretrack-mcp
Configuration
Set these environment variables:
| Variable | Required | Description |
|---|---|---|
TIRETRACK_API_URL |
Yes | API base URL — https://api.tiretrack.mi.tirerack.com (prod) or https://api-dev.tiretrack.mi.tirerack.com (dev) |
TIRETRACK_API_TOKEN |
Yes | Personal access token minted at Settings → Security → Personal Access Tokens |
Tokens look like
tt_pat_…, expire after 90 days by default, and can be revoked at any time from the same page.The examples below use
${TIRETRACK_API_TOKEN}so the value resolves from your shell environment. If you'd rather not export it, paste the token string directly into theTIRETRACK_API_TOKENfield instead.
Claude Code / Claude Desktop
Stable (production):
{
"mcpServers": {
"tiretrack": {
"command": "uvx",
"args": ["--refresh", "tiretrack-mcp"],
"env": {
"TIRETRACK_API_URL": "https://api.tiretrack.mi.tirerack.com",
"TIRETRACK_API_TOKEN": "${TIRETRACK_API_TOKEN}"
}
}
}
}
Dev (pre-release):
{
"mcpServers": {
"tiretrack": {
"command": "uvx",
"args": ["--refresh", "--prerelease", "allow", "tiretrack-mcp"],
"env": {
"TIRETRACK_API_URL": "https://api-dev.tiretrack.mi.tirerack.com",
"TIRETRACK_API_TOKEN": "${TIRETRACK_API_TOKEN}"
}
}
}
}
--refreshchecks PyPI for newer versions on each invocation.--prerelease allowinstalls.devpre-release versions.
OpenAI Codex CLI
Stable (production):
# .codex/config.toml
[mcp_servers.tiretrack]
command = "uvx"
args = ["--refresh", "tiretrack-mcp"]
[mcp_servers.tiretrack.env]
TIRETRACK_API_URL = "https://api.tiretrack.mi.tirerack.com"
TIRETRACK_API_TOKEN = "${TIRETRACK_API_TOKEN}"
Dev (pre-release):
# .codex/config.toml
[mcp_servers.tiretrack]
command = "uvx"
args = ["--refresh", "--prerelease", "allow", "tiretrack-mcp"]
[mcp_servers.tiretrack.env]
TIRETRACK_API_URL = "https://api-dev.tiretrack.mi.tirerack.com"
TIRETRACK_API_TOKEN = "${TIRETRACK_API_TOKEN}"
Gemini CLI
Stable (production):
{
"mcpServers": {
"tiretrack": {
"command": "uvx",
"args": ["--refresh", "tiretrack-mcp"],
"env": {
"TIRETRACK_API_URL": "https://api.tiretrack.mi.tirerack.com",
"TIRETRACK_API_TOKEN": "${TIRETRACK_API_TOKEN}"
}
}
}
}
Dev (pre-release):
{
"mcpServers": {
"tiretrack": {
"command": "uvx",
"args": ["--refresh", "--prerelease", "allow", "tiretrack-mcp"],
"env": {
"TIRETRACK_API_URL": "https://api-dev.tiretrack.mi.tirerack.com",
"TIRETRACK_API_TOKEN": "${TIRETRACK_API_TOKEN}"
}
}
}
}
Transports
| Transport | Command | Use case |
|---|---|---|
| stdio (default) | tiretrack-mcp |
Claude Code, Codex, Gemini CLI, Claude Desktop |
| Streamable HTTP | tiretrack-mcp --transport streamable-http --port 8080 |
ChatGPT, remote clients |
| SSE (legacy) | tiretrack-mcp --transport sse --port 8080 |
Older clients |
Development
cd mcp-server
uv sync
uv run tiretrack-mcp --help
Metadata
Release files for tiretrack-mcp 0.2.12.dev20261017031033
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 | |
|---|---|---|---|---|
| tiretrack_mcp-0.2.12.dev20261017031033.tar.gz | 74.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tiretrack_mcp-0.2.12.dev20261017031033-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 90.9 kB
Release files / tiretrack_mcp-0.2.12.dev20261017031033.tar.gz
| Download URL | tiretrack_mcp-0.2.12.dev20261017031033.tar.gz |
|---|---|
| Size | 74.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f14cd6c480a24b8ec3241e385a361d1242925b41dcc80f733afc7a6eb6b6851
|
|
BLAKE2b-256 checksum How to use checksums |
c0ed7fb2ce9ef04e04c5445079cbec15472974c8e00f937db60a3160d3752459
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tiretrack_mcp-0.2.12.dev20261017031033-py3-none-any.whl
| Download URL | tiretrack_mcp-0.2.12.dev20261017031033-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
35b619ecb93dff641bcc24df1fcc4a7e39a5454161f7c23c6a5f1dd5100e3e41
|
|
BLAKE2b-256 checksum How to use checksums |
f06e9559bda5e1c052f160943be10e9c9ba14df2189e761c33948ab80aa43f6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tiretrack-mcp 0.2.12.dev20261017031033
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.