MCP

​

What you can do

​

Prerequisites

• A Pike workspace you can sign into at app.usepike.com
• Access to an MCP client such as Claude, ChatGPT (paid plan with custom connectors), Cursor, or Claude Code
• Permission in that workspace to see the projects, tasks, customers, or members you will ask about

​

Connect Pike MCP end to end

https://mcp.usepike.com

curl -sS \
  -H "Authorization: Bearer $PIKE_API_SECRET" \
  -H "Accept: application/json" \
  "https://api.usepike.com/projects?limit=20"

​

Connect other MCP clients

​

ChatGPT

1. Enable Developer mode in ChatGPT settings (often under Settings → Connectors → Advanced, or Security and login, depending on your account UI).
2. Add a custom connector / developer app.
3. Name it Pike and set the MCP server URL to https://mcp.usepike.com.
4. Complete authentication when prompted.
5. Enable the connector in a new chat and ask a workspace question.

​

Claude Code

claude mcp add --transport http pike https://mcp.usepike.com

​

Cursor

1. Open the command palette (Command + Shift + P on macOS, Ctrl + Shift + P on Windows/Linux).
2. Search for Open MCP settings.
3. Click Add custom MCP.
4. Add:

{
  "mcpServers": {
    "pike": {
      "url": "https://mcp.usepike.com"
    }
  }
}

​

Use cases: pull data and see insights

​

Delivery status

1. Enable Pike MCP in Claude or ChatGPT.
2. Ask: “List in-progress projects and flag anything with tasks stuck in review.”
3. Follow up with: “Drill into [project name] and summarise blockers.”
4. Cross-check in the app under Projects and Task properties when you need to act.

​

Margin and profitability

1. Ask: “What does Pike show for profitability on [project name], and which cost or earnings inputs matter most?”
2. Follow up on cost profiles, billable time, and revenue booked using Project finance, Profitability, and Cost profile.
3. Use the answer to decide whether the issue is staffing, rates, unlogged time, or scope.

​

Capacity and allocation

1. Ask: “Who has capacity for discovery work next week?” or “Where is [person] allocated over the next two weeks?”
2. Compare the answer with Workspace capacity and How to allocate before you commit someone.

​

Customer and pipeline handoffs

1. Ask: “Summarise the Acme customer record and related open work.”
2. Ask: “What should delivery lock before we convert a won deal into a project?”
3. Keep CRM vs PSA roles clear with Deals and HubSpot when those apply.

​

Weekly operating review

1. Ask for a short briefing: active projects, overdue tasks, customers with risk, and people who look over-allocated.
2. Paste or refine the briefing for your leadership sync.
3. Open the linked records in Pike to assign owners and dates.

​

Pilot and onboarding

1. Enable Pike MCP for a new teammate.
2. Ask it to walk them through Run a pilot project while looking at the real pilot project in the workspace.
3. Keep time, tasks, and finance on one client engagement so the insights stay connected.

​

Example prompts

List active projects and group them by status. Call out anything that looks stalled.

For project Acme Phase 2, summarise open tasks, assignees, and anything past due.

Explain the profitability picture for Acme Phase 2 using Pike’s earnings and cost model.

Who on the delivery team looks over-allocated in the next two weeks, and on which projects?

Draft a Monday briefing: delivery risks, capacity pressure, and customers that need attention.

​

Security and access

• Pike MCP uses your Pike authentication and workspace permissions. You only see data you can already access in the app.
• Disconnect the connector in Claude or ChatGPT when someone should no longer use Pike from that client.
• Open API secrets are separate workspace credentials. Issue least-privilege scopes, store them outside git, rotate by creating a new secret then revoking the old one, and never paste secrets into chat logs.
• Only connect custom MCP connectors you trust. Review tool approval prompts before allowing unsupervised actions in any client.

​

Related pages