Build: EPS nodes, projects, WBS, activities, relationships, calendars, activity codes and resources. WBS, activities and relationships go in batches of up to 500.
MCP connector
An MCP server for construction schedules, running on your own computer
The P7 connector is a local MCP server. Claude Desktop, Claude Code and Codex use its tools to build, query, change, filter, print and save the schedule open in your P7 tab. Sign in to Pathizer through it, and the same connector also offers your Pathizer projects' tools, under your own permissions.
MCP is the standard AI apps use to call outside tools. P7's connector runs on your computer, listens only on 127.0.0.1 and gives your AI app P7's scheduling tools. With an optional Pathizer sign-in it lists Pathizer's own tools too, and every Pathizer call runs under your account's permissions.
Use P7 from Claude or Codex
Your AI app on your computer, your schedule in your browser.
Claude Desktop and Claude Code
Claude Desktop installs the connector from one downloaded file. Claude Code adds it with one terminal command.
Codex
Add the connector with one terminal command, or in ~/.codex/config.toml. Needs Node.js 20 or newer.
How a call travels
From your request to the change in your P7 tab
Install once
Add the connector to Claude Desktop, Claude Code or Codex from P7's Connect to AI dialog. From version 0.7.4 it updates itself.
Pair once
Your AI gives you a code or a link. Type the code into P7. With Remember this computer ticked, later visits connect with no code.
Ask
Ask in plain language. The AI picks the tools and sends the calls to the connector on 127.0.0.1.
P7 checks the project
Changes go to the project the AI is working on, which starts as the one open in P7. A change to any other project is refused unless you asked for that project by name.
P7 makes the change
Your tab applies it and lists it under AI changes. The newest AI change can be undone.
You decide when to schedule
Single edits never reschedule. The AI runs F9 when you ask, or after every edit if you tell it to. A change set schedules once when it is applied, unless the AI turns that off.
Optional: Pathizer
Ask the AI to sign you in to Pathizer and open the link it gives. After you sign in, Pathizer's tools appear in the AI's list and run under your permissions.
Who It Is For
For teams who want their AI app to work on schedules through tools, not pasted files
SchedulersProject controllersClaude and Codex usersIT reviewers
What the connector's tools cover
Change in bulk: one change set of up to 50,000 creates, updates and deletes, checked first, so a set with any problem changes nothing. It is one undo step.
Query: find activities, relationships or WBS rows by criteria, pick the fields, sort and page, or only count them.
Schedule and check: run F9, read the critical path and the scheduling log, and run the schedule check.
View: filters, group and sort, columns, layouts, timescale and the curtain change only what you see, never the schedule.
Files: import a .xer or .xml from a path on your computer, export or save .XER, save any layout as a PDF, and set the folder P7 saves in.
Pathizer, after an optional sign-in: read a project's Health Score, narrative, delay findings and documents, and use Pathizer's other connector tools, which check your role on every call as the app does.
Definitions
Terms used on this page.
Local MCP server
An MCP server that runs on your own computer. Your AI app starts it and calls its tools. P7's connector is one.
Change set
One call that carries many creates, updates and deletes. P7 checks all of them first and applies them as one step you can undo.
More in the glossary: MCP (Model Context Protocol), P7 Free Scheduling, XER file, Schedule log, Critical path.
Practical Outputs
What you get.
Schedule changes listed in P7's AI changes panel, with the newest one undoable
Answers built from the dates and float P7 computed
.XER and PDF files saved where you say
Pathizer results read under your own account
Related Workflows
Related pages.
FAQ
Questions about the MCP connector
No. It runs on your computer and listens only on 127.0.0.1. Pathizer's Talk to your schedule connector is the remote one, for AI apps in a web browser, and it reads project results.
Not on its own. The connector talks to your P7 tab on your computer. If you sign in to Pathizer and ask your AI to send P7 results to a Pathizer tool, that request goes to Pathizer under your account.
Only when you ask for that project by name. Calls that name no project go to the project the AI is working on, which starts as the one open in P7. Any other project, and a change that reaches projects not open, such as a calendar they share, needs that request.
A change set carries up to 50,000 creates, updates and deletes, and the batch tools take up to 500 items. A change set with any problem is refused whole.
No. P7 and its tools need no account. Sign in only to reach your Pathizer projects.
Only what its tools offer and your role allows. The connector passes each call through with your sign-in, and Pathizer checks your role on every call, as it does in the app. Some app actions, such as payments, are not offered through the connector. Sign out in P7's Connect to AI dialog deletes the token from your computer.
P7 runs in your browser with no account, and your schedule stays on your device.
Open P7 Free Scheduling