Planner

Connect the schedule to the tools around it.

Planner keeps the production schedule live. Integrations let the rest of your workflow read from it, ask useful questions of it, or build around it without someone copying updates by hand.

Talk to SalesView Pricing

Placeholder: integrations hero diagram showing Planner schedule in the centre, with three labelled paths out: API for systems, MCP for AI tools, exports for handoff

Three ways the schedule can leave the screen

Start with the live plan. Then choose the connection style that matches the job.

MCP: let AI tools work from the real schedule

MCP is the route for AI tools that support it. Instead of pasting an old export into a chat, the assistant can connect to Planner, read the current plan, and suggest changes against the live schedule.

  • Useful for schedule questions, context checks, and proposed updates
  • Works with Claude and other MCP-capable tools depending on client support
  • The schedule only changes when you are ready

Screenshot needed: Planner Settings -> MCP setup panel, ideally showing the quick-connect client selector and MCP URL/token guidance

API: build the workflows your team already needs

API access is for systems work. Pull schedule data into reporting, connect internal tools, create blocks from another workflow, or build a small bridge for the way your company runs production.

  • Good for custom dashboards, ops reports, and internal automation
  • Access keys use scoped permissions, so a workflow only gets what it needs
  • Best handled with a clear owner and a specific use case

Screenshot needed: API & Integrations settings showing access key creation, scopes, and usage summary

Exports and handoff: still useful when a file is the right answer

Not every connection needs to be live. Some clients, finance teams, and delivery workflows still need a static file. Planner should make that handoff intentional, not turn it into the working process.

  • Use exports for one-off review, sign-off, or archive
  • Keep the live schedule as the working source
  • Avoid running the production from yesterday’s file

Screenshot needed: export modal beside a live schedule, showing that exports are a handoff option rather than the main workflow

What changes when the schedule is connectable

The point is not integration for its own sake. The point is fewer stale copies and clearer handoff between planning and everything that depends on it.

Moment
Disconnected workflow
Connected Planner workflow

Someone asks an AI tool about the schedule

They paste a screenshot, spreadsheet, or notes into a chat and hope the context is still current.
The AI tool connects through MCP and works from the live Planner schedule.

Operations needs a weekly report

A coordinator re-enters dates into another sheet or dashboard every time the plan changes.
A small API workflow can read the schedule from Planner and feed the report.

A stakeholder still needs a file

The exported file becomes the schedule people work from, then immediately starts drifting.
Planner stays live. The export is a handoff, not the source of truth.

What to connect first

The best integration is usually the one that removes a recurring manual handoff. Start there.

AI schedule support

Connect Claude or another MCP-capable tool when people keep asking schedule questions outside Planner.

Internal reporting

Use the API when production, operations, or finance needs the same schedule data in another internal view.

Client or delivery handoff

Use exports or shared views when the other side needs to review, sign off, or archive rather than work live.

A sensible rollout path

No one needs to connect everything on day one. The clean route is live schedule first, then the handoffs that keep repeating.

Make Planner the current schedule

Integrations only help if the source is trusted. Start by keeping the working plan live in Planner.

Pick one recurring handoff

Choose the report, AI workflow, dashboard, or export that currently creates the most re-entry. Solve that first.

Add the right connection method

Use MCP for AI context, API for custom systems, and exports for static handoff. Different jobs, different routes.

Keep a human owner for changes

Connected workflows should support the schedule owner. They should not quietly rewrite the plan behind them.

Why this matters in production

Production schedules change quickly. Integrations are only useful if they reduce confusion rather than adding another place to check.

AI and systems work from the live plan

The connected workflow should read the schedule as it is now, not a file sent earlier in the week.

Access can be scoped to the job

API keys and MCP connections should only get the permissions the workflow needs.

Not every handoff needs live sync

Some teams still need a file. That is fine. The important part is knowing which version is the working schedule.

Where to go next

Use the right route for the kind of connection you are thinking about.

Live Planner

See how AI support stays grounded in the live schedule.

API and MCP help

Open the app help guide for setup details and access-key guidance.

Enterprise Overview

Review SSO, rollout, governance, and technical buying requirements.

Questions about integrations

Straight answers on setup, fit, and workflow.

What is MCP in plain English?+

MCP is a way for an AI tool to connect to a live system. For Planner, that means an MCP-capable AI tool can work from the current schedule instead of whatever someone pasted into a chat.

Is MCP the same thing as the API?+

No. MCP is mainly for AI tools that need context and tool access. The API is for custom software, reporting, dashboards, and internal systems.

Which AI tools can connect?+

Planner has setup guidance for Claude, ChatGPT, Cursor, and similar MCP-capable tools. Actual support depends on the AI client and how your account is configured.

Can Planner import from Excel or Google Sheets through MCP?+

Not directly through MCP. Import or build the schedule in Planner first, then MCP-capable tools can work from the live Planner schedule.

Do integrations change the schedule automatically?+

Connected workflows should not quietly rewrite the plan behind the schedule owner. Whether an AI client asks you to approve each step depends on that client, but Planner should remain the live plan you control.

Do I need integrations to start using Planner?+

No. Start with the live schedule. Add MCP, API, or other connected workflows when a repeated handoff is costing the team time.

Connect Planner when the schedule is ready to power more of the workflow.

Tell us what you want Planner to connect to. We can help work out whether that should be MCP, API, export, or something simpler.

Talk to SalesView Pricing