MCP
MCP is an open protocol: it describes how an agent discovers a service's tools and calls them. PalmaPlan is a complete server for it, served over HTTP, in the same process as the application.
Install
With a client that speaks MCP over HTTP:
claude mcp add --transport http palmaplan https://palmaplan.com/mcp
That's it. No package to install, no key to paste. Claude Code registers itself with PalmaPlan, opens your browser on a page that asks for your consent, and comes back with a named token — visible in your preferences, revocable with one click, valid for thirty days.
If you'd rather supply the token yourself (created under Settings › Connections and agents › Advanced access):
claude mcp add --transport http --header "Authorization: Bearer pp_…" palmaplan https://palmaplan.com/mcp
Text is selectable (triple-click, then Ctrl+C / Cmd+C) — no script is needed to
copy it. You need an account on palmaplan.com — by invitation
during the beta: the consent page asks you to sign in if you aren't already.
Security note: the MCP server only accepts the address it registered under — an instance reached by another name refuses the connection.
What an agent can do
The shipped MCP server exposes 101 tools — one per engine
command, named and shaped in scheduling terms (create and edit rows and blocks,
manage dependencies, templates, sharing, actions, analyses, printing,
attachments, undo…). The count is verifiable via tools/list; the
written proof is packages/mcp/src/tools/tools.test.ts:3260 (see the
claim → proof table).
- Build
- "Build me the schedule for the redesign: scoping in October, development over six weeks, testing before Christmas." A whole schedule is born in one call, with its phases, rows, blocks and links.
- Understand
- "What's late? What's the critical path? What's changed since Monday?"
- Try without breaking
- "What if testing slipped by two weeks?" — the answer arrives without a single date moving; you apply it afterward, or not.
- Track
- It breaks a task into actions, assigns them to whoever you want, checks them off as it goes — and the block's progress is computed on its own.
While it works, your screen follows over an open channel, with no reload — the
broadcast itself stays under a millisecond. And when it's done, Ctrl+Z
is still yours.
The embedded view
A schedule can render in an embedded view: the content alone, with no toolbar, configurable by its address — built for an MCP Apps host that knows how to load it.