Planera Public MCP Read-Only Connector Guide

Latest Update 10-13-2026

What this connection does

The read-only connection lets an AI assistant (Claude or ChatGPT) look at your Planera schedules and answer questions about them. It can read, analyze and report. It cannot change anything.

There are 30 tools currently available. You never call them by name, you ask a question, and the assistant picks the right ones. This guide explains these tools.

Three things worth knowing up front:

Nothing can be written. No activity edits, no new versions, no progress updates, no comments posted, no settings changed. The tools to do those things are not yet available.
Your permissions still apply. The assistant sees exactly what your Planera login (Oauth) sees, and no more. If you cannot open a project in Planera, the assistant cannot open it either.
It works across versions. Because Planera keeps every version of a schedule, the assistant can compare the current plan against a baseline or any earlier update.

Finding the right project

Before it can answer anything, the assistant has to work out which schedule you mean. Three tools handle that, and they most often run without you noticing.

Tool	What it does for you
`get_all_organizations`	Lists the Planera organizations and workspaces you belong to. Used at the start of a conversation, or when you work across more than one company or region.
`get_all_projects`	Lists the projects in an organization and matches a name you mention to the right one. Searches project names, descriptions, locations and schedule requirements, so "the terminal job" is usually enough.
`get_current_capabilities`	Checks what your role actually permits on a given project or organization before the assistant tries anything. This is the guardrail that keeps it inside your permissions.

Reading the schedule

These nine tools are how the assistant reads your plan, the activities, the dates, the resources, the working calendars and the codes on everything.

Tool	What it does for you
`get_project_details`	The project header: name, project type, brief, location, data date, start and finish dates, percent complete, and schedule requirements. This is what the assistant reads first for any "where does this job stand" question.
`get_project_elements`	The schedule breakdown - every activity, task, milestone and WBS group, with dates, durations and progress. It can be filtered to just what you asked about: work in a date range, work not started, a single crew's activities, or one work type.
`get_project_calendars`	The working calendars actually used on a project: which weekdays are worked, the hours per day, holidays and date overrides. This is how the assistant knows a four-day duration does not mean four calendar days.
`get_all_calendars`	The same calendar detail, but for the whole organization rather than one job. Useful for "which calendars do we have, and what does each one assume?"
`get_project_resources`	The labour, equipment and crews assigned on this project.
`get_all_resources`	Your organization's full resource library — everything that could be assigned, not just what is in use.
`get_all_codes`	Your activity code structure: the categories you classify work by (work type, zone, area, phase, risk level, responsible party) and the values available in each. This is what lets you ask about "all the electrical work" or "everything in Zone 2" and get a real answer.
`get_variance_codes`	Your organization's list of variance reasons - Weather, RFI Delay, Permit Delay and so on. Combined with the activities, it answers "what has been slowing us down, and how often?"
`get_all_stubs`	The cross-boundary connector nodes on the plan canvas. This is layout information, not scheduling data; it is used when the assistant needs to understand how a plan is drawn.

Analysis and scheduling intelligence

This is the part that goes beyond reading. These tools run Planera's own scheduling engine, so the answers match what you would get inside the product.

Tool	What it does for you
`get_critical_paths`	Returns the critical path and the near-critical paths behind it, grouped by float. It tells you what is actually driving your finish date, and what is one bad week away from driving it.
`run_what_if_scenario`	Simulates a change and reports the effect on the finish date and the critical path. Ask "what happens if steel erection slips ten days?" and you get the answer without touching the live schedule.
`validate_plan`	Checks a proposed change for errors before anyone runs it, and explains what would break.
`get_compliance_report`	A schedule quality assessment with a pass/fail on each rule, a grade, an overall quality index and the specific activities that failed. It covers the best-practice checks schedules get audited against — missing logic, negative float, excessive float, over-long durations — plus Planera's own rules.
`get_cpm_reference`	Planera's reference on how critical path method calculations and Planera's scheduling rules work. The assistant reads this so its explanations match Planera's behaviour rather than a generic textbook.
`get_mutation_schema`	The technical description of how a change would be expressed. On this connection it is only used to set up a what-if or a validation — there is no tool here that can apply one.

Note: The what-if simulations never touch your data. They run in memory, return a result, and are discarded. Applying a change requires a different, write-enabled connection and a deliberate action in Planera.

Tracking change

Six tools cover the two questions that come up most in a progress meeting: what changed since last time, and does the field schedule still match the master.

What changed, and who changed it

Tool	What it does for you
`get_project_collection_by_project_id`	The full version history of a schedule — every update, when it was created, and how the versions relate. This is what lets the assistant find your baseline and compare today's plan against it.
`get_project_history`	The audit trail: individual creates, edits and deletions, each with the person, the timestamp and what changed. Filter it by date range, by person, or by the type of thing changed. Useful for "when did that milestone move, and who moved it?"

Master schedule and field schedule

Tool	What it does for you
`get_linked_field_schedule_project_ids`	Lists the field schedules attached to a master schedule. The starting point for any reconciliation.
`compare_ms_fs_progress_discrepancies`	Compares live progress between a master schedule and a linked field schedule — status, percent complete, actual and forecast dates, durations, and out-of-sequence work. It also compares two field schedules under the same master. This is the "is the field telling the same story as the master?" check.
`get_element_discrepancies`	Compares the content of the two schedules rather than the progress: activities added or removed in the field, and per-activity differences in name, type, crew and equipment assignments, codes, variance reasons, logic links and planned durations.
`get_library_bookmark_discrepancies`	Compares the code libraries and saved views between master and field, catching the quiet drift where one side has added a code category or changed an option the other does not have.

Comments, and Planera's reference material

The last group covers what your team has said on the schedule, and the internal references the assistant reads so its answers match how Planera actually works.

Tool	What it does for you
`get_project_element_comments`	Pulls every comment thread across a project in one go. Good for "summarise what the team has flagged this week" or "which activities have open questions on them".
`get_element_comments`	Pulls the comment thread on one specific activity, when you are already looking at it.
`get_dashboards_reference`	How Planera calculates the dashboard metrics: the progress S-curve, percent complete and baseline percent complete, tracking variance, the stats panel, the progress delta grid, planned percent complete, variance reason codes and the quality score. This is why the assistant's numbers reconcile with your dashboard instead of contradicting it.
`get_resources_guide`	What each trade can and cannot do. Used to spot mismatches between the labour assigned and the work scheduled.
`get_canvas_layout_guide`	How the Planera canvas is laid out and how elements are positioned on it.
`get_html_design_guide`	Planera's formatting standards for generated reports, so an exported report looks like a Planera document rather than a generic one.

Comments are read-only here too. The assistant can summarize a thread; it cannot post to it.

A to Z index

All 30 tools in alphabetical order, for looking one up.

Tool	In short
`compare_ms_fs_progress_discrepancies`	Progress differences, master against field
`get_all_calendars`	Every working calendar in the organization
`get_all_codes`	Your activity code categories and values
`get_all_organizations`	Organizations and workspaces you belong to
`get_all_projects`	Project list, and name-to-project matching
`get_all_resources`	Full resource library for the organization
`get_all_stubs`	Cross-boundary connector nodes on the canvas
`get_canvas_layout_guide`	How the Planera canvas is laid out
`get_compliance_report`	Schedule quality score, rule by rule
`get_cpm_reference`	How Planera calculates the critical path
`get_critical_paths`	Critical and near-critical paths by float
`get_current_capabilities`	What your role permits on this project
`get_dashboards_reference`	How each dashboard metric is calculated
`get_element_comments`	Comment thread on one activity
`get_element_discrepancies`	Content differences, master against field
`get_html_design_guide`	Planera's formatting standards for reports
`get_library_bookmark_discrepancies`	Code library and saved-view drift between schedules
`get_linked_field_schedule_project_ids`	Field schedules attached to a master
`get_mutation_schema`	Change format, used to set up what-ifs
`get_project_calendars`	Working calendars used on this project
`get_project_collection_by_project_id`	Version history, including the baseline
`get_project_details`	Project header, dates, data date, percent complete
`get_project_element_comments`	Every comment thread on the project
`get_project_elements`	The activities, milestones and WBS, filterable
`get_project_history`	Audit trail of edits, with who and when
`get_project_resources`	Crews and equipment in use on this project
`get_resources_guide`	What each trade can and cannot do
`get_variance_codes`	Your catalogue of delay and variance reasons
`run_what_if_scenario`	Simulate a change without saving it
`validate_plan`	Check a proposed change for errors

What it cannot do

The read-only connection has no ability to change your data. The tools that would do so are not available to it, so this is a structural limit rather than a setting.

Specifically, on this connection nothing can:

Create, edit or delete an activity, milestone, relationship or WBS group
Save a new version of a schedule, or overwrite an existing one
Update progress, actual dates or percent complete
Assign or remove a crew, a piece of equipment or a resource
Add, edit or delete a code, calendar or variance reason
Post or reply to a comment
Change project settings, user roles, or send invitations
Delete anything at all

On top of that, your existing Planera permissions still apply in full. The assistant checks your role before it acts, reads only the projects your account can open, and is refused by Planera itself if it tries to go further. A project you cannot see stays invisible to it.