Bekind-Labs/tracker-boot-mcp-server
If you are the rightful owner of tracker-boot-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
The Tracker Boot MCP Server is a Model Context Protocol server that integrates with Tracker Boot, allowing AI assistants to access stories and analytics for the current iteration.
Tracker Boot MCP Server
A Model Context Protocol (MCP) server that integrates with the Tracker Boot, enabling AI assistants to fetch stories and analytics for current iteration.
Prerequisites
-
Before running the MCP server, you need to set the following environment variables:
TRACKER_BOOT_API_KEY(required): Your Tracker Boot API Key.
Get your API key from the Tracker Boot Settings.
-
Pull the latest image from the public repository:
$ docker pull public.ecr.aws/tracker-boot/mcp-server:latest
Available Tools
The MCP server provides the following tools for interacting with the Tracker Boot API:
| Tool | Description | Parameters | Returns |
|---|---|---|---|
tb_get_story | Fetch story details | storyId | Complete story details |
tb_get_story_tasks | Fetch tasks in a story | storyId | List of tasks (title, finished) in a story |
tb_get_story_comments | Fetch comments in a story | storyId | List of comments (content) in a story |
tb_get_current_iteration | Fetch current iteration with stories | projectId | Iteration data with list of stories including cycle time details |
tb_create_story | Create a new story | projectId, title, description (optional), storyType (optional) | Details of the created story |
tb_update_story_title | Update the title of a story | storyId, title | Details of the updated story |
tb_update_story_description | Update the description of a story | storyId, description | Details of the updated story |
tb_update_story_status | Update the status of a story | storyId, status | Details of the updated story |
tb_create_task | Creat a new task in a story | storyId, title | Details of the created task |
tb_batch_create_tasks | Create multiple tasks in a story | storyId, titles | Details of the created tasks |
tb_update_task | Update a task in a story | taskId, storyId, finished, title (optional) | Details of the updated task |
tb_create_comment | Create a new comment in a story | storyId, content | Details of the created comment |
tb_get_projects | Get the list of projects | List of projects that the user has access to | |
tb_search_stories | Search stories by keyword or labels | projectId, query (optional), labels (optional) | List of stories matching the search criteria |
NOTE: If you don't see all the tools listed above, please ensure that you are using the latest docker image of the MCP server.
Installations
Claude Applications
Claude Desktop
Prerequisites Claude Desktop installed (latest version) Tracker Boot API Key (https://trackerboot.com/settings/api) For local setup: Docker installed and running
Configuration File Location
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Local Server Setup (Docker)
Add this codeblock to your claude_desktop_config.json and restart Claude Desktop:
{
"mcpServers": {
"tracker-boot": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "TRACKER_BOOT_API_KEY",
"public.ecr.aws/tracker-boot/mcp-server:latest"
],
"env": {
"TRACKER_BOOT_API_KEY": "YOUR_TRACKER_BOOT_API_KEY"
}
}
}
}
Claude Code CLI
Prerequisites
- Claude Code CLI installed
- Tracker Boot API Key (https://trackerboot.com/settings/api)
- For local setup: Docker installed and running
- Open Claude Code inside the directory for your project (recommended for best experience and clear scope of configuration)
Local Server Setup (Docker)
- Run the following command in the Claude Code CLI:
claude mcp add tracker-boot -e TRACKER_BOOT_API_KEY=YOUR_TRACKER_BOOT_API_KEY -- docker run -i --rm -e TRACKER_BOOT_API_KEY public.ecr.aws/tracker-boot/mcp-server:latest
- Restart Claude Code
- Run
claude mcp listto see the Tracker Boot server is configured from the terminal
Github Copilot Coding Agent
- Ensure that Copilot Coding Agent is enabled for your repository
- Add the following to Copilot's MCP Configuration in Repo Settings > Copilot > Coding Agent > MCP configuration
{
"mcpServers": {
"tracker-boot-mcp-server": {
"type": "local",
"tools": ["tb_get_story","tb_get_current_iteration","tb_get_story_tasks","tb_create_comment","tb_get_story_comments","tb_create_task","tb_create_story","tb_update_task","tb_update_story_title","tb_update_story_description","tb_update_story_status","tb_get_projects", "tb_batch_create_tasks", "tb_search_stories"],
"command": "docker",
"args": [
"run",
"-i",
"-e", "TRACKER_BOOT_API_KEY",
"public.ecr.aws/tracker-boot/mcp-server:latest"
],
"env": {
"TRACKER_BOOT_API_KEY": "COPILOT_MCP_TRACKER_BOOT_API_KEY"
}
}
}
}
- Create a secret called
COPILOT_MCP_TRACKER_BOOT_API_KEYcontaining your API Key in Repo Settings > Environments > copilot > Environment secrets- Get your Tracker Boot API Key from here: https://trackerboot.com/settings/api
Devin
- Navigate to https://app.devin.ai/settings/mcp-marketplace
- Click "Add Your Own"
- Create an MCP config with the following settings:
| Field | Value |
|---|---|
| Server Name | Tracker Boot MCP |
| Transport Type | STDIO |
| Short Description | Get Story and Iteration details from Tracker Boot |
| Secrets | Click + (Add a new secret) |
| * Secret Name | API_TOKEN |
| * Secret Value | your_api_key (get it here) |
| Command | docker |
| Arguments | |
| run | |
| -ie | |
| TRACKER_BOOT_API_KEY=$API_TOKEN | |
| public.ecr.aws/tracker-boot/mcp-server:latest |
- Click
Save Changes