Float
Float is a resource management and project planning platform for scheduling teams, managing project capacity, tracking time, and reporting on utilization.
Verdict
Common use cases
- Check team capacity before committing to deadlines
- Draft project schedules from standup notes
- Pull utilization reports for client billing reviews
- Find who's available next sprint without opening Float
- Log allocations while triaging feature requests
Integration
- Vendor
- Float
- Category
- productivity
- Auth
- API_KEY
- Tools
- 10
- Composio slug
float
Tools
- Create Allocation
Schedule work on a Float project for one or more people, or leave it unassigned, with optional phase, status, notes, and recurrence. Supplying a project-task name may create that project-task definition when none matches.
- Create Project
Create a Float project with core scheduling and classification fields. This tool intentionally excludes rates, currencies, budgets, and project-team replacement operations.
- Get People Capacity Report
Return person-level capacity, scheduled, unscheduled, time-off, billable, and non-billable totals for a required date range.
- Get Project
Retrieve one Float project by ID, optionally including its phases, project tasks, team, expenses, or currency details.
- Get Project Utilization Report
Return project-level scheduled, logged, billable, non-billable, budget, and utilization totals for a required date range, optionally for one project.
- List Allocations
Find scheduled allocations in Float by project, person, client, phase, project task, date range, billing state, status, or recurrence.
- List People
Find active people on the Float schedule by default, or filter for archived or all people, employee type, department, tags, and related account details.
- List Projects
Find Float projects by code, client, lifecycle state, billing state, status, or tags, optionally including planning details such as phases, tasks, team, and currency.
- Update Allocation
Reschedule or revise selected fields of a Float allocation. Sends only fields explicitly supplied by the caller and preserves Float task IDs in the result. Supplying a project-task name may create that project-task definition when none matc
- Update Project
Update selected core identity, schedule, lifecycle, and tag fields on a Float project. This tool does not expose financial configuration or project-team replacement and removal operations.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations and click Connect next to Float. 2. You'll be prompted for a Float API key — generate one by logging into Float, navigating to Settings → Integrations → API, and clicking Generate New Key. 3. Copy the key and paste it into Switchy's connection dialog. 4. Click Test Connection to verify Switchy can reach Float's API. 5. Once connected, open any Project in Switchy and type '@Float list people' to confirm the integration works. 6. If the command returns your team roster, you're ready — Float will now respond to @mentions in any Project chat. 7. To revoke access later, delete the API key in Float's settings and remove the integration in Switchy.
What teammates see: by default, memories from Float 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
Team Capacity This Month
@Float get people capacity report for the date range from the first day of this month to the last day of this month. Show scheduled hours, unscheduled hours, and time off for each person.
Active Projects Overview
@Float list projects where lifecycle state is active. Include project code, client name, status, and tags for each project.
Create Allocation for Designer
@Float create allocation for [person name] on project [project name] from [start date] to [end date] with 4 hours per day. Mark it as tentative and add a note that this is pending client approval.
Project Utilization Report
@Float get project utilization report for project [project name] covering the last 30 days. Include scheduled hours, logged hours, billable hours, and budget totals.
Who's Free Next Week
@Float list people and then get people capacity report for next Monday through next Friday. Highlight anyone with more than 20 unscheduled hours available.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Float show me team capacity for the next two weeks and flag anyone over 80% scheduled
Capacity report for May 15–29, 2024: • Sarah Chen: 80h capacity, 68h scheduled (85%), 0h time-off — over threshold • Marcus Lee: 80h capacity, 52h scheduled (65%), 8h time-off • Priya Patel: 80h capacity, 72h scheduled (90%), 0h time-off — over threshold • Jordan Kim: 80h capacity, 40h scheduled (50%), 0h time-off Two people exceed 80% utilization. Consider redistributing allocations or flagging new requests.
This example uses the Get People Capacity Report tool to surface over-allocation risk. Float's API returns totals by person; the AI synthesizes the threshold logic. Requires read access to people and allocations. Date ranges must be explicit—Float won't infer "next two weeks" without calculation.
@Float create a two-week allocation for Jordan on the Acme redesign project starting Monday, 20 hours per week, design phase
Allocation created: • Person: Jordan Kim • Project: Acme Website Redesign • Phase: Design • Duration: May 20 – June 2, 2024 (2 weeks) • Hours: 20h/week (40h total) • Status: Confirmed The allocation now appears on Jordan's schedule and the Acme project timeline. Float will block this time unless the allocation is moved or deleted.
This example demonstrates the Create Allocation tool's ability to schedule work with phase granularity. The MCP writes directly to Float's schedule—there's no undo via chat. If the project or person name is ambiguous, the tool may fail; you'll need to supply a Float project ID or clarify which Jordan. Recurrence and task assignment are optional parameters not shown here.
@Float pull all active projects tagged 'Q2-priority' and summarize their utilization against budget for April
Q2-priority projects, April 2024 utilization: • Acme Redesign: 120h scheduled, 95h logged, 80h billable (budget: 150h, 63% consumed) • Beta Launch: 200h scheduled, 180h logged, 160h billable (budget: 180h, 100% consumed—over budget) • Gamma Integration: 80h scheduled, 60h logged, 50h billable (budget: 120h, 42% consumed) Beta Launch has exceeded its April budget by 20 logged hours. Acme and Gamma are under budget but Acme's scheduled hours suggest May may run tight.
This example chains List Projects (filtered by tag) with Get Project Utilization Report, then asks the AI to interpret budget burn. Float's utilization data is historical; scheduled hours are forward-looking. The MCP can't predict future overruns, only report what's logged or allocated. Requires read access to projects, allocations, and time tracking.
Use-case deep-dives
When Float wins for 10-30 person agency resource allocation
A 15-person creative agency planning Q2 capacity uses Float's MCP to pull person-level availability and project allocations into a shared Switchy workspace. The team runs Get People Capacity Report across the quarter, then uses List Allocations filtered by department to spot overcommits before they accept new client work. The MCP shines here because Float's allocation model maps cleanly to billable-hour shops: you're scheduling people to projects, not tracking granular tasks. If your team is under 10 people or you need sub-task time tracking, Float's abstraction level is too high—use Clockify or Harvest instead. For agencies juggling 5-15 active projects and needing a shared view of who's booked when, this MCP turns Float into a real-time capacity dashboard inside Switchy.
When this MCP handles monthly utilization reviews for retainer clients
A 6-person consultancy running monthly retainer reviews uses Float's Get Project Utilization Report to compare scheduled hours against logged time and budget caps. They filter by project ID, pull the last 30 days, and surface overruns in a Switchy thread before the client call. The MCP works because Float tracks billable vs. non-billable at the allocation level, so the report math is already done. The boundary: if you need invoice-ready timesheets or expense reconciliation, Float doesn't export those through the MCP—you'll still export CSVs manually or use a dedicated billing tool. For teams that bill by the hour and need a quick utilization sanity-check without leaving Switchy, this integration delivers the numbers you'd otherwise pull from Float's web UI every month.
When Float's allocation search beats calendar chaos for 4-8 person teams
A 7-person product studio runs daily standups where the PM asks "who's free Thursday to start the rebrand?" Instead of tab-switching to Float, they use List Allocations filtered by date range and person to see who's unbooked. The MCP returns allocation status, phase, and project task in one call, so the team can reassign or create a new allocation on the spot with Create Allocation. This works when your team schedules at the day or half-day level and projects last weeks, not hours. If you're managing hourly task assignments or need real-time calendar sync, Float's granularity isn't fine enough—use Motion or a calendar-native tool. For small teams that plan in blocks and want allocation truth without opening another app, this MCP makes Float the single source of scheduling truth inside Switchy.
Frequently asked
What does the Float MCP let me do in Switchy?
It connects your Float resource schedule to Switchy's AI workspace. You can query capacity reports, create allocations, list projects and people, and pull utilisation data without opening Float. The MCP exposes 10 tools covering scheduling, project management, and reporting — so your team can ask questions like "Who's free next week?" or "Create a two-week allocation for Sarah on Project X" directly in chat.
Do I need admin access to connect Float?
You need a Float API key, which typically requires account-owner or admin permissions to generate. Standard members can't create API keys in most Float plans. Once connected, the MCP inherits the permissions of that key — so if the key has read-only access, you won't be able to create allocations or projects through Switchy.
Can the Float MCP update time entries or log hours?
No. The MCP focuses on scheduling and capacity planning — creating allocations, querying reports, managing projects and people. It doesn't touch time tracking or timesheets. If your team needs to log actual hours, they'll still do that in Float or via Float's separate time-tracking API.
How is this different from just using Float's web app?
The MCP brings Float data into Switchy's shared AI context. Instead of switching tabs to check capacity or create an allocation, your team asks in chat and the AI handles the API calls. You lose Float's visual timeline and drag-drop interface, but you gain speed for repetitive queries and the ability to combine Float data with other tools in a single conversation.
Who on my team should connect the Float integration?
Whoever manages your Float account and has API-key access — usually a project manager, resource planner, or account owner. That person's API key determines what the entire Switchy workspace can read or write in Float, so choose someone whose permissions match your team's needs. You only need one connection per workspace.