Resource Planner
Resource Planner helps teams schedule people, manage projects and assignments, and review workspace time entries.
Verdict
Common use cases
- Draft sprint staffing plans in chat
- Allocate designers to Q2 roadmap projects
- Check who's assigned to a launch next week
- Delete outdated placeholder assignments in bulk
- Spin up a new project and assign the team
Integration
- Vendor
- Resource Planner
- Category
- productivity
- Auth
- API_KEY
- Tools
- 16
- Composio slug
resource_planner
Tools
- Create Assignment
Assign one resource to one project for a date range and return the created assignment ID.
- Create Project
Create a project with a title and optional note, color, and visibility, then return its project ID.
- Create Resource
Create a workspace resource with optional capacity, workdays, note, and visibility, then return its resource ID.
- Delete Assignmentdestructive
Permanently delete one assignment by its assignment ID.
- Delete Assignmentsdestructive
Permanently delete 1-25 assignments sequentially. The operation is not atomic: each ID has its own outcome, successful deletions are not rolled back, and processing stops after an unsafe or ambiguous failure.
- Delete Projectdestructive
Permanently delete a project and all of its assignments. This cascading deletion cannot be undone.
- Delete Resourcedestructive
Permanently delete a resource and all of its assignments. This cascading deletion cannot be undone.
- Get Project
Retrieve one current workspace project by its project ID.
- Get Resource
Retrieve one current workspace resource by its resource ID.
- List Assignments
Return all assignments, optionally narrowed to a project, a resource, or both.
- List Projects
Return every project in the connected Resource Planner workspace, including project IDs and editable planning fields.
- List Resources
Return every resource in the connected Resource Planner workspace, including resource IDs needed for assignment workflows.
- List Time Entries
Return one page of workspace time entries, with an optional total-duration summary and a cursor for the next page.
- Update Assignment
Replace an assignment's internal note and return all affected assignment IDs.
- Update Project
Update at least one of a project's title, note, color, or visibility. Omitted fields are preserved by reading the project before updating it.
- Update Resource
Replace a resource's internal note without changing its scheduling fields, then return the current resource.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations and click Connect next to Resource Planner. 2. You'll be prompted to paste an API key; generate one in your Resource Planner workspace under Account → API Keys. 3. Copy the key and paste it into Switchy, then click Authorize. 4. Switchy confirms the connection and shows Resource Planner in your active integrations list. 5. Open any Project and type '@Resource Planner create a project called Q2 Launch with a blue color' to test the connection. 6. The MCP replies with the new project ID, confirming the integration works. 7. From now on, @mention Resource Planner in any thread to create resources, assign them to projects, or query existing allocations.
What teammates see: by default, memories from Resource Planner are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Project and Assign Team
@Resource Planner create a project called 'Mobile Redesign' with a green color, then assign Alice, Bob, and Carol to it from May 1 to May 14.
Check Current Assignments
@Resource Planner show me all current assignments for the project ID 12345 and summarize who's allocated when.
Add Resource with Capacity
@Resource Planner create a resource named 'Jordan Lee' with 32 hours per week capacity, working Monday through Thursday.
Bulk Delete Old Assignments
@Resource Planner delete assignments with IDs 101, 102, 103, 104, and 105, then confirm how many were removed.
Delete Project and Cascade
@Resource Planner delete the project with ID 67890 and all its assignments, then list the resources that are now unassigned.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Resource Planner show me all assignments for the design team in March and which projects are overallocated
Based on current workspace data, the design team has 47 assignments across 8 projects in March. Three projects show overallocation: Brand Refresh (3 designers, 120% capacity), Mobile Redesign (2 designers, 140% capacity), and Marketing Assets (4 designers, 105% capacity). The remaining 5 projects are within normal capacity ranges. This analysis assumes standard workday configurations for each resource.
This read-heavy example demonstrates the MCP's ability to aggregate assignment data and surface capacity issues. Requires API_KEY with read access to assignments, projects, and resources. The overallocation calculation depends on how capacity and workdays are configured per resource in your workspace.
@Resource Planner create a new project called Q2 Website Refresh and assign Sarah Chen and Marcus Liu to it from April 1 to June 30
Created project 'Q2 Website Refresh' (ID: proj_8x4k2m). Successfully created two assignments: Sarah Chen assigned April 1 – June 30 (assignment ID: asn_9p3j1q), Marcus Liu assigned April 1 – June 30 (assignment ID: asn_7r2n5t). Both resources are now allocated to this project for the full quarter. Note that existing assignments for these resources during this period remain unchanged.
This write example shows the MCP creating a project and multiple assignments in sequence. Each operation returns an ID for future reference. Be aware this does NOT check for conflicts — if Sarah or Marcus already have assignments in Q2, you'll now have overlapping allocations. Review capacity before committing.
@Resource Planner review all my projects ending this month and draft a brief status summary noting which ones have unassigned capacity
You have 4 projects ending in March: (1) Dashboard Redesign has 2 designers assigned through March 31, fully allocated. (2) API Documentation has 1 technical writer assigned but shows 40% unused capacity based on workday settings. (3) Customer Onboarding has 3 support specialists, fully allocated. (4) Analytics Integration has no current assignments — this project appears to be unresourced for its final two weeks. Consider reassigning available capacity from API Documentation or confirming whether Analytics Integration is on hold.
This synthesis example pairs the MCP's data retrieval with AI reasoning to identify resource gaps. The AI interprets capacity percentages and flags risks, but the underlying data quality depends on your team keeping assignments and project dates current. Useful for weekly planning reviews or handoff preparation.
Use-case deep-dives
When Resource Planner MCP beats spreadsheets for client staffing
A 10-person creative agency juggling 6-8 concurrent client projects hits the spreadsheet wall when the founder needs to see who's available next week while a project manager is simultaneously updating assignments. The Resource Planner MCP wins here because it gives the team a single source of truth with atomic create/delete operations—no merge conflicts, no version-control nightmares. The 16-tool scope covers the full lifecycle: spin up projects, assign people to date ranges, pull current state for standup. The trade-off threshold is around 15-20 people: below that, the MCP's simplicity is the feature; above that, you're probably already in a dedicated resource-management platform with richer forecasting. If your agency is still emailing Excel files to coordinate staffing, this MCP closes that loop in a week.
Resource Planner MCP for roadmap-to-headcount mapping
A 25-person product org planning Q3 initiatives needs to translate a roadmap of 12 epics into engineer-weeks and flag capacity gaps before committing to stakeholders. The Resource Planner MCP handles this if the planning cycle is quarterly or slower—create projects for each epic, assign engineers to date ranges, then query assignments to surface overlaps or gaps. The API-key auth means the VP of Product can delegate the MCP to a planning lead without opening up the entire workspace. The weakness is real-time replanning: if priorities shift mid-sprint and you're reassigning 30 people across 8 projects, the sequential delete-assignments tool gets tedious. This MCP is the right call when planning happens in big batches (quarterly reviews, annual budgeting) and the team is under 40 people. Beyond that, you need bulk-update primitives this MCP doesn't expose.
When Resource Planner MCP simplifies multi-event crew scheduling
A nonprofit running 4 regional conferences per year with a rotating crew of 15 volunteers and 3 paid coordinators needs to track who's committed to which event without double-booking anyone. The Resource Planner MCP fits because each conference is a discrete project, each person is a resource, and assignments map cleanly to event dates. The create-assignment and get-project tools let the coordinator check availability in Slack during a planning call, and the cascading delete-project operation cleans up canceled events without orphaning assignments. The boundary case is frequency: if you're staffing weekly events or managing shift-level granularity (morning vs. afternoon slots), the MCP's date-range model is too coarse. This works for quarterly-or-longer event cycles where the planning overhead justifies API integration. If your crew is under 20 and your events are under 10 per year, this MCP replaces the Google Sheet without adding enterprise bloat.
Frequently asked
What does the Resource Planner MCP do in Switchy?
It lets AI agents create, read, update, and delete resources, projects, and assignments in your Resource Planner workspace. Agents can build project plans, assign people to tasks with date ranges, and query current allocations — all without leaving the chat. Useful for teams that want AI to draft schedules or answer "who's free next week" questions directly.
Do I need admin access to connect Resource Planner?
You need an API key from Resource Planner, which typically requires workspace admin or owner permissions to generate. Once connected in Switchy, the MCP inherits the permissions of that API key — so if the key can delete projects, the AI can too. Treat the connection like you would a power-user account.
Can the MCP bulk-delete assignments or roll back mistakes?
It can delete up to 25 assignments in one call, but the operation is not atomic. If one ID fails midway, successful deletions stay deleted — there's no automatic rollback. Deleting a project or resource also cascades to all its assignments permanently. Ask the AI to confirm destructive actions before executing them.
How does this compare to using Resource Planner's web UI?
The MCP is faster for repetitive tasks — creating ten assignments or checking availability across projects takes one prompt instead of ten clicks. You lose the visual timeline and drag-and-drop convenience of the UI, so use Switchy for data entry and queries, then review the plan in Resource Planner's interface.
Who on the team should connect this MCP?
Whoever manages resource allocation and has API key access. Since the MCP can delete projects and resources, don't connect it to a shared Switchy workspace unless everyone understands the AI has write permissions. One person connecting it and sharing read-only reports in chat is usually safer than giving the whole team destructive access.