MCP Server

Last updated: June 15, 2026

Project Paced exposes a Model Context Protocol (MCP) server so AI assistants can create timelines, read Command Centre dashboards, and update project milestones without copy-pasting between tools.

• A Project Paced account at app.projectpaced.com or eu.projectpaced.com
• For OAuth setup, an API key is not needed; you will sign in with your Project Paced account
• When connecting to MCP and before authentication, you can select your Project Paced instance: Global or EU
• For manual setup, create an API key in Profile -> API Access

These options use OAuth. Your AI tool opens a Project Paced sign-in page and connects automatically.

Claude Web, Desktop, and Cowork

Custom connectors using remote MCP are available across Claude, Cowork, and Claude Desktop. Claude Free users may be limited to one custom connector, while Pro, Max, Team, and Enterprise users can use more.

Pro or Max plan:

1. Open Customise -> Connectors
2. Click + then Add custom connector
3. Enter https://mcp.projectpaced.com/mcp
4. Click Add
5. Sign in to Project Paced and authorise the connection

Team or Enterprise plan:

1. An owner opens Organisation settings -> Connectors
2. Click Add -> Custom -> Web
3. Enter https://mcp.projectpaced.com/mcp
4. Team members open Customise -> Connectors and click Connect

Enable Project Paced per conversation from Claude's + menu.

ChatGPT Apps and Connectors

OpenAI renamed connectors to apps in December 2025, but the setup still lives under Apps & Connectors and existing connector behaviour remains. ChatGPT can connect to remote MCP servers as custom apps.

1. Open Settings -> Apps & Connectors
2. Turn on Developer Mode if required for your workspace
3. Create or import a custom app from the remote MCP server
4. Enter https://mcp.projectpaced.com/mcp
5. Choose OAuth authentication
6. Complete the Project Paced sign-in flow

Once connected, enable Project Paced from the tools/apps menu in a chat.

Microsoft Copilot Studio

Yes, Project Paced MCP can be connected to Microsoft Copilot through Copilot Studio agents. Microsoft documents MCP as an extension option for Copilot Studio, with support for MCP tools and resources.

Important limits:

• This is for Copilot Studio agents, not a simple consumer Microsoft 365 Copilot chat setting.
• Copilot Studio requires generative orchestration to use MCP.
• Your organisation controls which external MCP servers an agent may use.
• Use the hosted server URL: https://mcp.projectpaced.com/mcp

Use manual setup for Claude Code, Cursor, Windsurf/Devin Desktop, Antigravity, or any MCP-compatible client that accepts a remote HTTP server and bearer token.

Create an API key in Profile -> API Access at app.projectpaced.com, then keep it in an environment variable where possible.

Claude Code

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

Cursor

Open Cursor Settings -> MCP and add:

{
  "mcpServers": {
    "projectpaced": {
      "url": "https://mcp.projectpaced.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PROJECTPACED_API_KEY}"
      }
    }
  }
}

Then set PROJECTPACED_API_KEY=pp_your_key_here in your environment.

Windsurf or Devin Desktop

Open Settings -> Cascade -> MCP Servers and add:

{
  "mcpServers": {
    "projectpaced": {
      "serverUrl": "https://mcp.projectpaced.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PROJECTPACED_API_KEY}"
      }
    }
  }
}

Then set PROJECTPACED_API_KEY=pp_your_key_here in your environment.

Antigravity and other local stdio clients

If your client prefers local stdio servers, run the published package:

{
  "mcpServers": {
    "projectpaced": {
      "command": "npx",
      "args": ["-y", "@projectpaced/mcp-server"],
      "env": {
        "PROJECTPACED_API_KEY": "pp_your_key_here"
      }
    }
  }
}

Other clients using remote HTTP

• URL: https://mcp.projectpaced.com/mcp
• Auth header: Authorization: Bearer pp_your_key_here

Where supported, use ${env:PROJECTPACED_API_KEY} instead of pasting the key directly into a config file.

Ask your assistant:

"List my Project Paced projects"

If it works, it will return your project list. An empty list is still a successful connection.

• "Create a timeline for a mobile app launch in Q3"
• "Generate a 6-month product roadmap for a SaaS onboarding redesign"
• "Show me all my projects"
• "Get the timeline for project [ID]"
• "Summarise the Command Centre health for project [ID]"
• "What needs attention across my portfolio?"
• "Who is over-allocated in Q3?"
• "Show the latest weekly update for project [ID]"
• "Move the beta launch milestone to 15 July"
• "Mark milestone [ID] in project [ID] as complete"

These tools never write data and do not consume an AI generation. Enterprise tools require an Enterprise account. Report tools require Pro or Enterprise.

get_projects

List all projects in your Project Paced account.

Output: Project IDs, titles, and timestamps.

get_timeline

Get a specific project and all its milestones.

Input:

• projectId (required) - the project to retrieve

Output: Project details and full milestone list.

get_resources (Enterprise)

List the team roster, including each person's department, max capacity, peak concurrent allocation across all projects, and status.

get_project_allocations (Enterprise)

Show who is allocated to a specific project, at what percentage, over which time periods, with each person's project-scoped status.

Input:

• projectId (required)

get_project_health (Enterprise)

Read the Command Centre Project Health dashboard for a project: resource coverage, timeline health, team distribution, key person risk, available capacity, and project notes.

Input:

• projectId (required)

get_attention_items (Enterprise)

Read the Command Centre "Needs attention" strip for over-capacity resources across the next six months.

get_capacity (Enterprise)

Read portfolio capacity over a date window: who is over-allocated, stretched, or has free capacity. This is the data behind the utilisation heatmap.

Input:

• from (required) - window start, YYYY-MM-DD
• to (required) - window end, YYYY-MM-DD
• bucket (optional) - day, week, or month
• detail (optional) - pass grid to include the full per-resource per-bucket grid

get_weekly_update (Pro/Enterprise)

Read the PMO weekly status report for a project: RAG status, trend, current phase, what changed, what is at risk, and decisions needed. Reading does not generate a new report.

Input:

• projectId (required)
• weekId (optional) - ISO week ID such as 2026-W24; omit for latest
• history (optional) - true to return recent RAG/headline history

get_project_history (Pro/Enterprise)

Read the weekly snapshot archive for trend analysis. Snapshots are 52-week rolling frozen copies of milestones and allocations.

Input:

• projectId (required)
• weekId (optional)
• from (optional)
• to (optional)
• limit (optional)

generate_timeline

Generate an AI-powered project timeline from a plain-text description. Creates a new project by default; pass a projectId to replace milestones in an existing project.

Input:

• description (required) - what the project is about, max 2000 characters
• projectTitle (optional) - title for the project
• projectId (optional) - existing project ID to regenerate milestones for

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

update_milestone

Update fields on a single milestone. This does not consume an AI generation.

Input:

• projectId (required) - the project containing the milestone
• milestoneId (required) - the milestone to update
• date (optional) - planned start date, ISO 8601
• endDate (optional) - planned end date for duration bars, or null to clear
• status (optional) - planned, in_progress, or complete
• completedAt (optional) - actual completion date, or null to clear
• actualStartDate (optional) - actual start date, or null to clear

Read-only Command Centre and report tools do not consume AI timeline generations.

The MCP server transmits only the data needed for the tool call you ask it to run, such as project descriptions, project IDs, milestone IDs, dates, resource allocations, project notes, and stored reports. No additional data is collected or stored beyond your Project Paced account. See our Privacy Policy for full details.

Back to nav