Plan your day.
Let your AI run it.
Project management for teams that ship — with a real MCP server, so your assistant creates tasks, moves work and reads dashboards through the same permission checks as the UI.
Free while you evaluate · no card · connected in one command
Drag a card, or focus one and press ← →. Run a tool to watch the assistant do the same thing — through the same authorization pipeline, with the same activity trail.
FIG 0.1
Built on one pipeline
A click, a tool call and an API request take the same path — same permissions, same validation, same activity trail. There is no faster, looser way in.
FIG 0.2
Open to your agents
The Model Context Protocol is a standard, not our integration. Any client that speaks it gets the same 32 tools, filtered to what your token actually allows.
FIG 0.3
Answers the people who ask
A report that arrives from your product comes back as an email saying it shipped — including everyone whose duplicate got merged into it.
Give the day a shape
Spaces, lists and boards that page as they grow — a list with ten thousand tasks opens as fast as an empty one.
1.0 Plan- Deliveryws
- Platformspace
- Q3 hardeningfolder
- Export pipeline18
- Notifications11
- Backlogfolder
- Growthspace
- 1.1Board and list views
- 1.2Subtasks, five deep
- 1.3Custom fields
- 1.4Calendar and roadmap
Plan the year, not just the week
Initiatives across quarters, with milestones, health and the progress rolled up from the spaces underneath them.
2.0 Roadmapprogress rolled up from the spaces underneath milestone planned, not started Drag a bar to reschedule it
- 2.1Initiatives
- 2.2Quarter timeline
- 2.3Milestones and targets
- 2.4Health and drift
Hand your assistant the keyboard
32 MCP tools over the same pipeline as the interface, bounded by scopes you choose and workspaces you name.
3.0 AutomateTools this token can see 28
whoamilist_tasksget_tasksearch_taskslist_statusesget_my_assigned_tasksget_workspace_treecreate_taskupdate_taskchange_task_statuschange_assigneeschange_task_tagsset_task_estimatecreate_subtaskcreate_statuscreate_listcreate_spacecreate_tagdelete_taskget_commentsget_activityadd_commentget_metricget_dashboardlist_dashboardsget_workspace_statsget_person_analyticsget_team_availabilitylist_membersinvite_memberchange_member_rolelist_workspaces $ claude mcp add --transport http planner \
https://api.planner.day/api/mcp \
--header "Authorization: Bearer tvmcp_…"Preset
pm_bot
Scopes tick one to see the effect
Workspaces
Authority is the intersection. Nothing widens it at runtime, and no token can perform a super-admin action.
- 3.1MCP server
- 3.2Scoped tokens
- 3.3REST API
- 3.4GitHub integration
Close the loop you keep dropping
One script tag in your product turns a bug report into a task — and tells the person who reported it when it ships.
4.0 ListenWhat your customer sees
Powered by Planner.dayWhat your team sees, at the same moment
- 01
It lands in triage
Every submission arrives in one queue, searchable by that reference.
- 02
Approve, or merge into a duplicate
Approving creates the task. Merging attaches this reporter to an existing one, so five duplicates still mean five people get told.
- 03
Completion is an event, not a glance
Nobody has to remember to tell anyone. That is the step every other setup drops.
- 4.1Embeddable widget
- 4.2Triage portal
- 4.3Public roadmap
- 4.4Reporter emails
Measure the flow, not the feelings
Every status change is recorded as it happens, so cycle time is a measurement rather than an estimate.
5.0 MeasureDrawn from recorded status transitions — not from anyone remembering to update a spreadsheet.
- 5.1Dashboards
- 5.2Person analytics
- 5.3Drilldowns
- 5.4Status transitions
Where we win, and where we don’t
Two things the established tools do not bundle. One thing they do better, said plainly rather than left for you to discover.
| Planner.day | Jira | Linear | ClickUp | |
|---|---|---|---|---|
| Built-in MCP server | 32 tools | — | — | — |
| Embeddable feedback widget | Included | Add-on | — | — |
| Automatic “it shipped” email | Included | — | — | — |
| Public roadmap + voting | Included | Add-on | Add-on | Included |
| Breadth of features | Focused | Vast | Focused | Vast |
| SOC 2 report | Not yet | Yes | Yes | Yes |
Questions
Straight answers.
Does Planner.day work with AI assistants?
Planner.day ships a built-in MCP (Model Context Protocol) server exposing 32 tools over streamable HTTP. Any MCP client — Claude, or another assistant — can create tasks, change status, assign work, search and read dashboards. Every call runs through the same permission checks as the web UI, and a token is limited to its scopes and its allowed workspaces.
How do I collect bug reports and feature requests from my users?
Planner.day gives you an embeddable widget: one script tag in your own product. Users report a bug or request a feature without leaving it and without creating an account. Each submission arrives in a triage queue where approving it creates a task, and the reporter is emailed automatically when that task is done.
Can Planner.day publish a public roadmap?
Yes. Feature requests can be published to a public roadmap with anonymous voting, shown both inside the widget and on a standalone page. It is the same submission data, published — not a separate tool kept in sync.
How is Planner.day different from Jira, Linear or ClickUp?
Two things those tools do not bundle: a built-in MCP server so an AI assistant can operate the board directly, and a customer feedback loop that runs from an embeddable widget through triage to an automatic email telling the reporter their issue shipped. Planner.day does not match ClickUp on breadth of features.
Does Planner.day integrate with GitHub?
Yes. Tasks link to GitHub issues, branches and pull requests with commit and PR tracking. Reads use a business-level token while writes use each member’s own token, so actions are attributed to the person who took them rather than a shared bot account.
Get started
Plan tomorrow.
Let your AI get on with it.
Free while you evaluate. Connect an MCP client in one command, drop the widget into your product, watch the first report become a task.