Project Paced MCP Server

An MCP (Model Context Protocol) server that lets AI assistants generate and manage project timelines via the Project Paced API.

Prerequisites

1. A Project Paced account at app.projectpaced.com
2. An API key — go to Profile → API Access and click Generate API Key

Option A: Remote HTTP (Recommended — no install required)

Connect directly to the hosted server via HTTP. Works with Claude Code, Claude Desktop, and any MCP-compatible client.

Claude Code (CLI)

claude mcp add --transport http projectpaced \
  https://mcp.projectpaced.com/mcp \
  --header "Authorization: Bearer pp_your_key_here"

Claude Desktop

Add to your Claude Desktop config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "projectpaced": {
      "type": "http",
      "url": "https://mcp.projectpaced.com/mcp",
      "headers": {
        "Authorization": "Bearer pp_your_key_here"
      }
    }
  }
}

Option B: Local stdio (self-hosted)

Install and run the server locally as a stdio process.

npm install -g @projectpaced/mcp-server

Or run from source:

cd mcp-server
npm install
npm run build

Claude Desktop Setup (stdio)

Add to your Claude Desktop config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "projectpaced": {
      "command": "projectpaced-mcp",
      "env": {
        "PROJECTPACED_API_KEY": "pp_your_key_here"
      }
    }
  }
}

If running from source:

{
  "mcpServers": {
    "projectpaced": {
      "command": "node",
      "args": ["path/to/mcp-server/dist/index.js"],
      "env": {
        "PROJECTPACED_API_KEY": "pp_your_key_here"
      }
    }
  }
}

Available Tools

generate_timeline

Generate an AI-powered project timeline from a text description. Creates a new project by default; if projectId is supplied, replaces all milestones in that existing project.

Input:

• description (required) — Description of the project (max 2000 chars)
• projectTitle (optional) — Title for the project
• projectId (optional) — Existing project ID to regenerate milestones for

Output: Project ID, generated milestones with dates/categories/descriptions, remaining generation count.

get_projects

List all projects in your Project Paced account.

Output: List of projects with IDs, titles, and timestamps.

get_timeline

Get a specific project and its milestones.

Input:

• projectId (required) — The project ID to retrieve

Output: Project details and all milestones with dates, categories, and descriptions.

update_milestone_dates

Update the start and/or end date of a single milestone. Does not consume an AI generation.

Input:

• projectId (required) — The project containing the milestone
• milestoneId (required) — The milestone to update
• date (optional) — New start date (ISO 8601, e.g. 2026-06-01)
• endDate (optional) — New end date for Timeline+ duration bars (null to clear)

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | PROJECTPACED_API_KEY | Yes | Your Project Paced API key (starts with pp_) | | PROJECTPACED_API_URL | No | Override the API base URL (for staging/development) |

Rate Limits

• Trial: 3 lifetime API calls
• Pro: 50 generations/month (shared with in-app usage)

When limits are reached, generate_timeline returns an error with a link to upgrade.

Privacy Policy

Project Paced's privacy policy is available at https://projectpaced.com/privacy.

The MCP server transmits only the data you explicitly pass to each tool call (project descriptions, project IDs, milestone IDs, and dates). No additional data is collected or stored beyond your Project Paced account.