@project-tracker/mcp

MCP server for Project Tracker. Plugs into any MCP-aware AI client — Cursor, Claude Code, Continue, Aider, Codex, and others — to let it read and update your tracker via tool calls (list_projects, create_item, move_item, update_item, etc.) instead of curl wrangling.

If your AI client doesn't support MCP, use the curl path instead — same data, different shape.

Install

Full setup guide with troubleshooting: https://app.project-tracker.ai/docs/mcp-setup.md

Short version — add to your AI client's MCP config. The location varies (Cursor: Settings → MCP; Claude Code: ~/.claude.json; Continue: its config.json; others have an equivalent), but the JSON shape is the same:

{
  "mcpServers": {
    "project-tracker": {
      "command": "npx",
      "args": ["-y", "@project-tracker/mcp"],
      "env": {
        "API_BASE": "https://app.project-tracker.ai",
        "API_KEY": "pt_your_token_here"
      }
    }
  }
}

Restart your client (or reload its MCP panel). The project-tracker server will appear with its tool catalogue.

Where the API key comes from

Log in to https://app.project-tracker.ai → Integrations (top right) → Generate key → name it (e.g. Cursor on my laptop, Claude Code work machine) → copy the pt_... token. Keys are shown once; store it in a password manager.

The key inherits your user's permissions — owner / team-member / collaborator access to each project. If a tool call returns Permission denied: requires X on project Y, it's not a bug, it's your project role.

Configuration

| Env var | Required | Default | Meaning | |---|---|---|---| | API_KEY | yes (in practice) | — | Your pt_... API key. Calls go through unauthenticated if unset, which means most operations 401. | | API_BASE | no | https://app.project-tracker.ai | Origin of the Project Tracker API. Default points at the public hosted service — leave it alone unless you're self-hosting or developing locally (in which case set it to your own host, e.g. http://127.0.0.1:3001). Origin only — the server appends /api/... internally. |

Tools

• Projects: list_projects, create_project, update_project
• Items: list_items, get_item, get_item_context, create_item, update_item, delete_item, restore_item, move_item, bulk_update_items
• Views: get_board, get_matrix

Full schema for each tool surfaces in your MCP client. Argument shapes mirror the underlying REST API — full reference at https://app.project-tracker.ai/api/docs.

AI behaviour prompt

Drop the contents of https://app.project-tracker.ai/docs/mcp-prompt.md into your project's system prompt — Claude Code reads CLAUDE.md, Cursor uses .cursorrules or its Rules-for-AI panel, Continue takes a system message in its config, and so on. The prompt tells the AI the conventions — work-claiming, soft-claim safety, when to use changeLog vs description, etc.

The MCP server checks the prompt version on session start and flags via _meta.promptUpdateAvailable if your bundled copy is stale.

Requirements

Node.js ≥ 18. The package ships pre-built JavaScript; npx -y @project-tracker/mcp installs and runs without a separate build step.

Source

This package lives in the mcp-server/ subdirectory of the Project Tracker repo. Issues + PRs welcome at https://github.com/DQ-ProjectTracker/project-tracker.

License

MIT