Planner.day

ClaudeCommunityby Planner Day

Planner.day is project management for teams that need clear ownership: spaces, folders and lists holding tasks and subtasks, with comments, custom fields, time tracking, dashboards and a roadmap. This connector lets an assistant work in it directly rather than describing it. Ask what is blocking a release and it reads the tasks, their statuses and who holds them. Ask what the design team shipped last week and it reads the activity. Dictate a bug and it files one in the right list, with the right type, assigned to the right person. It can search across a workspace, pull analytics for a person or a team, read comment threads and post replies, and open a dashboard. Access is scoped twice over. Every permission is separate, so an assistant that reads your work cannot change it unless you said so, and one that creates and updates tasks cannot delete them: deletion sits behind its own permission and is never included by default. Access is also bounded by workspace. You pick which workspaces the assistant may reach when you connect, and it is refused anywhere else before a request reaches a handler. Every call goes through the same checks as the web interface, so the assistant sees what you would see and nothing more. Actions it takes appear in the activity trail attributed to it, not silently as you. You approve the permissions and the workspaces on a Planner.day screen when you connect, and can disconnect at any time from Settings, Account, Tokens and connected apps, which revokes its access immediately. A workspace admin enables MCP per workspace and chooses which permissions that workspace is willing to grant, so the set you are offered is already bounded by what your organisation allows.