Tick off tasks
From status reports, meeting notes or commits: the agent finds the matching tasks and marks them done.
PathHub has its own MCP server. Once connected, Claude, ChatGPT, Gemini, Copilot and other AI assistants plan, update and review your projects right in the chat, with your permissions and in your language. No API key: add the address, sign in to PathHub, done.
Works with
Path “ERP rollout” is ready: 7 phases, 36 weeks, 2 new risks.
Example flow, simplified
PathHub speaks MCP, the open standard for AI tools. So you work with the assistant you or your company already use, right up to your own self-hosted AI.
Works with, among others,
Including
Including
Including
Including
Based on vendor information, as of October 2026. Whether custom connectors are available depends on the plan and settings of each provider. Any client that supports MCP with sign-in (OAuth) or an API key works.
Three steps, no coding.
In Claude or ChatGPT, add a custom connector with app.pathhub.ai/mcp. In Claude Code, Cursor or VS Code a short entry is enough.
Pick a workspace and access level, click “Allow”. No API key, nothing to copy. Already on the Free plan.
Your agent picks the right PathHub tools, looks things up, writes changes and reports back.
Six examples out of 74 tools. Everything you maintain in the app, your agent can maintain too.
From status reports, meeting notes or commits: the agent finds the matching tasks and marks them done.
Invoices and orders land on the right budget line. PathHub computes actuals and commitments itself.
Add and assess new risks from conversations or documents, with impact and mitigation.
One sentence becomes a complete plan with phases, tasks, budget, risks and a compliance check.
Find open mandatory items, update their status and document evidence across all Paths.
Run the built-in PathHub agents for status reports, weekly plans or steering committee briefs.
Your agent can combine PathHub with everything else it has access to, such as files, code or other MCP servers.
“Read this week's commits and tick off what's done in the Path Release 3.2. Create tasks for open bugs.”
“Here are the steering committee minutes. Add the decisions as next steps and the new risks to the risk register.”
“What's due in my Paths this week, what's stuck, and which mandatory compliance items are still open?”
Paths, sections, tasks, export, document search, compliance library, templates, quotas
Create and update Paths, add tasks, tick off (up to 50 at once), comment, delete
Phases, risks, stakeholders, milestones, budget items, cost entries, compliance items, next steps
Generate plans in the background, run agents and planning tools, recommendations, ask a Path, webhooks
Your agent sees these tools as soon as it is connected. It picks the right one itself, you don't need to know the names.
| Phases | add_phaseupdate_phasedelete_phase |
| Risks | add_riskupdate_riskdelete_risk |
| Stakeholders | add_stakeholderupdate_stakeholderdelete_stakeholder |
| Milestones | add_milestoneupdate_milestonedelete_milestone |
| Budget items | add_budget_itemupdate_budget_itemdelete_budget_item |
| Compliance items | add_compliance_itemupdate_compliance_itemdelete_compliance_item |
| Next steps | add_next_stepupdate_next_stepdelete_next_step |
| Checklist | add_checklist_itemupdate_checklist_itemdelete_checklist_item |
| Cost entries | add_cost_entryupdate_cost_entrydelete_cost_entry |
| Compliance evidence (link, note) | add_compliance_evidence |
Plus 4 ready-made prompts you can pick directly in Claude & co.: plan_initiative (Plan an initiative), weekly_status (Weekly status), sync_status_update (Apply a status update), compliance_check (Compliance check)
The MCP server is not a back door. It uses exactly the rules of the app.
The assistant only sees the workspace you pick at sign-in and has at most your permissions. It never gets your password.
At sign-in you decide: read only, edit, or additionally AI actions. With read access it cannot change anything.
Quotas per plan, 120 calls per minute, limits per Path and a lockout after repeated invalid credentials.
Disconnect in one click under Developers. An agent only deletes phases that contain tasks with explicit confirmation.
Every call is logged. Changes trigger the same webhooks as in the app.
PathHub runs on servers in Germany. What your agent reads is processed by your AI provider (e.g. Anthropic or OpenAI) under their terms.
The address is all you need: on first use you sign in to PathHub and confirm access. For scripts and automations an API key works too.
Settings → Connectors → “Add custom connector”, enter the name PathHub and this address, then “Connect”. Also applies in Claude Desktop and the app.
https://app.pathhub.ai/mcp
Settings → Apps & Connectors → create a custom connector (developer mode, depending on your plan), enter this address, authentication OAuth.
https://app.pathhub.ai/mcp
Run in your terminal, then open /mcp in Claude Code and sign in.
claude mcp add --transport http pathhub https://app.pathhub.ai/mcp
Add to ~/.cursor/mcp.json or .cursor/mcp.json. Sign-in opens on first use.
{
"mcpServers": {
"pathhub": { "url": "https://app.pathhub.ai/mcp" }
}
}Add to .vscode/mcp.json. Sign-in opens on start.
{
"servers": {
"pathhub": { "type": "http", "url": "https://app.pathhub.ai/mcp" }
}
}For scripts, n8n or clients without a sign-in window: create an API key under Developers and send it as a header.
claude mcp add --transport http pathhub https://app.pathhub.ai/mcp \ --header "Authorization: Bearer phk_live_..."
Detailed guide with all endpoints:API & developersDocumentation
The Model Context Protocol is an open standard that lets AI assistants use external tools. Claude, ChatGPT, Gemini, Microsoft Copilot Studio, Cursor and many other apps support it. PathHub provides 74 tools through it.
Any that support MCP: in the browser and as apps, for example Claude, ChatGPT, Gemini, Grok, Perplexity and Mistral Le Chat; in companies Microsoft Copilot Studio, Gemini Enterprise, Open WebUI or LibreChat; for development Claude Code, Cursor, VS Code with GitHub Copilot and more. Whether custom connectors are available depends on each provider's plan.
Yes. Platforms such as Microsoft Copilot Studio, Open WebUI or LibreChat add PathHub as an MCP server, even when they run self-hosted models. An admin sets up the connection once, everyone signs in with their own PathHub account and keeps their permissions.
All of them. On the Free plan you connect your AI assistant with 200 calls per month, Pro includes 2,000, Max 20,000. AI actions such as plan generation additionally count against your workspace's AI quota. API keys and webhooks for your own integrations are available from Pro.
No. In Claude or ChatGPT you just add the address and sign in to PathHub. After that you talk to your assistant like to a colleague.
No. Once connected, PathHub is available in your chats, in Claude also in the desktop and mobile apps. Depending on the app you switch the connector on or off per chat.
Reading and editing don't, they only count as API calls. AI actions such as plan generation or PathHub agents count against your workspace's AI quota. The conversation itself runs on your Claude or ChatGPT account.
It can only do what you allow at sign-in. Read access is enough for analysis. Phases with tasks are only deleted with explicit confirmation, and every connection can be disconnected instantly.
Yes. ChatGPT connects directly to the MCP server as a custom connector, in developer mode depending on your plan. Alternatively, a GPT action with PathHub's OpenAPI description works too.
PathHub itself runs on servers in Germany. Content your agent retrieves is processed by your AI provider under their terms. Details are in the Trust Center.
Sign up for free, add the address in your AI assistant, sign in. Within minutes it works with real plans.