Connect AI (MCP)

Endpoint and administration

Tokens and client setup: /einstellungen/mcp (after sign-in)
MCP URL of your instance (shown on the token page)
Auth: Bearer token, planchi OAuth (PKCE), or Entra JWT (M365 Copilot)

https://<your-domain>/mcp

What MCP can do

The agent reads and writes planning data through named tools — planchi stays the source of truth. Below is the map by domain. The full catalog (all tools, guides, prompts, and what MCP does not do) is the Markdown download — read it or drop it into Cursor/ChatGPT.

Download MCP reference

Projects & team: Create projects and change settings (budget, hourly rate, cost cap, reserves). Methodology packs (e.g. HermesLite). Member list for assignees.
Specification: Maintain sections, requirements (REQ) and acceptance criteria (KRIT); extract PDF to Markdown and import. Release PDF stays in the app.
Milestones & acceptance: Scope from the specification, link criteria to tasks, implementation texts, start review. Signed sign-off PDF in the UI.
Tasks, Gantt, Kanban: Create tasks (one or batch), dependencies, schedule, Complete+Accepted status, comments. Soft-reset via batch delete, not a loop.
Time: Start, switch and stop the timer; log time; timesheet and weekly report.
Meetings: Notes, decisions, action items; create tasks from actions.
Wiki: Living project knowledge. Read project context before planning. Do not copy formal requirements into the wiki.
Change requests: Draft, submit, materialize after the customer PDF. No MCP upload of the signature.
Budget & EVM: Budget lines, procurement costs, earned value. Personnel cost comes from time × rate — do not record it twice.
Risks: Risk register probability × impact. Unmanaged high risks make the cockpit critical.
Stakeholders: Stakeholder register (not org members) — Power/Interest.
Capacity & reports: Availability, absences, Gantt, blocker dashboard, acceptance matrix, effort and schedule variance.

After connecting, tools/list is the live contract (JSON Schema, token permissions). Parameters are not on this page. Visible tools follow role and context (personal vs organization).

Bearer token (Cursor, Claude, VS Code)

Best for developer tools with a local MCP configuration.

Create a token under /einstellungen/mcp (name, optional expiry).
Choose context: personal or organization (see note below).
Copy the token once and store it securely — it is not shown again.
Under «Connect your MCP client», pick the matching tab and apply the configuration.

Note Personal vs organization

Personal: Time tracking, your own tasks, personal view — recommended default.
Organization: Team planning, specification, milestones, change requests — only if the agent must change team data and org permissions allow it.

OAuth (ChatGPT, Copilot Studio)

No manual token; sign-in and consent in the browser.

In the client, add an MCP / custom connector with the MCP URL.
Choose auth type OAuth.
Sign in to planchi, pick context, and allow.
Revoke grants later under /einstellungen/mcp.

Client notes

Claude Code: CLI command from the token page (claude mcp add …)
Cursor: entry in ~/.cursor/mcp.json
VS Code: entry in .vscode/mcp.json
Other clients: server URL plus Authorization: Bearer <token>
Copilot Studio / M365 Copilot: https://<host>/mcp?catalog=copilot (70 planning tools, no timer/booking) with OAuth Dynamic discovery or Entra SSO

Note Agent rule / briefing

/einstellungen/mcp provides a copy-ready agent rule (English, for persistent Cursor/Claude rules), a shorter briefing for the first chat, and Copilot instructions (intent→tool for the 70 Studio tools). Recommended so the agent maintains comments, Complete+Accepted status and implementation texts correctly.

Operational notes

«Access denied» from the agent usually means the wrong context (org vs personal).
Issue org tokens only when team write access is really required.
Customer sign-off (signed PDFs) stays in the UI — the agent does not replace approval.
For self-host: keep /mcp and OAuth callbacks reachable from the internet over HTTPS (Copilot runs in the Microsoft cloud).