Rocketlane
Collaborative customer onboarding and implementation platform for professional services teams.
Verdict
Common use cases
- Surface at-risk projects during team standups
- Log billable hours from Slack threads
- Archive completed onboardings in bulk
- Create follow-up tasks from support escalations
- Pull project status before client calls
Integration
- Vendor
- Rocketlane
- Category
- productivity
- Auth
- API_KEY
- Tools
- 33
- Composio slug
rocketlane
Tools
- Archive Project by ID
Archives a specific project based on its unique identifier.
- Create Company
Creates a new company (account) in rocketlane. this action allows you to create a new company/account in your rocketlane workspace. it complements existing company-related actions by providing the ability to register new accounts using the
- Create Task
Creates a new task.
- Create Time Entry
Tool to create a new time entry in rocketlane. this endpoint allows users to log time spent on tasks or projects. it complements the existing rocketlane get time entries action and enables complete time tracking functionality within the roc
- Delete Projectdestructive
This tool allows users to permanently delete a project in rocketlane. it requires a valid project id and appropriate permissions (admins, super users, and project owners). note that deletion is irreversible; therefore, consider using archiv
- Delete Task By IDdestructive
Delete a specific task using its unique identifier (taskid).
- Delete Time Entry by IDdestructive
Delete a specific time entry using its unique identifier (timeentryid).
- Get All Fields
Retrieve all custom fields available in the system.
- Get Company
This tool retrieves detailed information about a specific company/account in rocketlane by its id. it provides comprehensive information about the company including its status, address, currency, created date, updated date, custom fields, a
- Get Field By ID
Retrieve detailed information about a specific custom field using its unique identifier (fieldid).
- Get Project by ID
Retrieves detailed information about a specific project using its unique identifier.
- Get Task By Id
Retrieve extensive information about a specific task using the task's unique identifier (taskid).
- Get Template By ID
Retrieve detailed information about a specific template using its unique identifier (templateid). note: the exact api endpoint and response structure need to be verified from the official rocketlane api documentation.
- Get Time Entries
Tool to retrieve all time entries from rocketlane. it provides endpoints to get time entries with support for pagination, filtering by project id, user id, start and end dates. this allows tracking of time spent on various tasks, generating
- Get Time Entry By ID
Retrieve detailed information about a specific time entry using its unique identifier (timeentryid).
- Get User By ID
Retrieve detailed information about a specific user using their unique identifier (userid).
- List Companies
This tool retrieves a list of all companies/accounts in rocketlane. it's a basic get endpoint that returns all companies without requiring any specific resource ids or additional parameters. the endpoint is independent and can be executed w
- List Company Fields
This tool retrieves a list of all available company/account fields in rocketlane. these fields represent the various attributes and properties that can be associated with companies/accounts in the rocketlane system.
- List Company Note Fields
This tool retrieves a list of all available note fields for companies in rocketlane. company note fields are custom fields that can be added to company/account notes for better organization and data collection. it provides details such as f
- List Currencies
Returns a predefined list of commonly used currencies since rocketlane api doesn't provide a dedicated currencies endpoint. this list includes major global currencies with their codes, names, and symbols.
- List Customer Users
List customer users.
- List Project Fields
This tool retrieves a list of all project fields in rocketlane, including both default and custom fields. it provides definitions, metadata, and configuration details for each field, which is essential for understanding project structure, m
- List Project Phases
This tool retrieves a list of project phases from rocketlane. it allows users to fetch and filter phases based on various parameters including projectid, startdate, duedate, startdateactual, duedateactual, phasename, sortby, sortorder, limi
- List Projects
This tool retrieves a list of all projects in the rocketlane instance. it provides project details including project id, project name, project status, created date, owner information, customer information, and other metadata.
- List Task Fields
This tool retrieves a list of all task fields in rocketlane. it allows users to get comprehensive field data and details for tasks, and supports various query parameters for filtering, pagination, and sorting.
- List Templates
This tool retrieves a list of all available templates in rocketlane. it fetches all available templates in the account and returns a list of template objects containing details like template id, name, description, created at, updated at, is
- List Users
This tool retrieves all users in the rocketlane instance. it is an independent action that does not require any resource ids or external dependencies. the endpoint returns detailed user information including user ids, emails, names, roles,
- List Vendor Users
List vendor users by filtering users with type 'partner'. this action retrieves users from the /api/1.0/users endpoint and applies a filter. the filter used is "type:equal:partner".
- Retrieve Subscription Details
Retrieves detailed information about the current subscription.
- Search User By Email
Search user by email id.
- Update Company
This tool updates an existing company/account in rocketlane. it uses the put endpoint to update the company details identified by companyid. the action complements the existing create company action and is essential for maintaining up-to-da
- Update Project By Id
Updates an existing project's details using its unique identifier.
- Update Time Entry by ID
Update existing time entry details using its unique identifier (timeentryid).
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP integrations panel. 2. Click 'Add Integration' and select Rocketlane from the productivity category. 3. In a separate browser tab, log into your Rocketlane workspace and go to Settings > API Keys. 4. Generate a new API key with read and write permissions for projects, tasks, and time entries. 5. Copy the key and paste it into the Switchy connection dialog, then click 'Connect'. 6. Switchy will verify the key and confirm the connection within a few seconds. 7. Open any Space and type '@Rocketlane list my active projects' to test — you should see a response with current project data. 8. To invoke tools during conversations, @mention Rocketlane followed by your request (e.g. '@Rocketlane create a task for the Q1 kickoff call'). 9. If a command fails, check that your API key has the necessary permissions in Rocketlane's settings.
What teammates see: by default, memories from Rocketlane are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Projects
@Rocketlane show me all active projects sorted by due date. Include project name, owner, and current status.Open in a Space →
Log Time Entry
@Rocketlane create a time entry for 2 hours on the Acme Corp onboarding project. Task: kickoff call and requirements gathering.Open in a Space →
Create Onboarding Task
@Rocketlane create a task titled 'Send API credentials to client' in the Acme Corp project. Assign it to Sarah and set the due date for Friday.Open in a Space →
Archive Completed Project
@Rocketlane archive the project with ID 12345. Confirm it's marked complete and all deliverables are uploaded.Open in a Space →
Check Custom Fields
@Rocketlane list all custom fields configured in our workspace. Show field names, types, and which object they apply to.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Rocketlane show me all active projects with overdue tasks and their current owners
Based on your Rocketlane workspace, here are 4 active projects with overdue tasks: 'Q1 Enterprise Onboarding' (owner: Sarah Chen) has 3 tasks overdue by 5-12 days, primarily in the technical setup phase. 'Acme Corp Implementation' (owner: Mike Torres) shows 2 overdue deliverables from last week's sprint. 'Beta Customer Migration' (owner: Jordan Lee) has 1 critical task 8 days past due. 'Platform Integration - TechStart' (owner: Sarah Chen) has 4 overdue items clustered in documentation review. This is an illustrative example showing how the MCP aggregates project status across your workspace.
This example combines project listing with task filtering to surface at-risk work. Requires read access to projects and tasks via your API key. The MCP returns structured data that the AI synthesizes into prioritized insights. Actual response shape depends on your workspace's project count and custom field configuration.
@Rocketlane create a task in the 'Q2 Product Launch' project: finalize go-to-market deck, assign to Emma, due Friday, high priority
Task created successfully in 'Q2 Product Launch' project. Task ID: TSK-4782. Title: 'Finalize go-to-market deck'. Assigned to: Emma Rodriguez. Due date: Friday, January 17, 2025. Priority: High. The task appears in Emma's queue and the project timeline. You can view it at rocketlane.com/projects/q2-launch/tasks/4782. This illustrative example shows the MCP's task creation response including the generated task identifier and confirmation of assignment.
This demonstrates the MCP's write capability for task management. The create action requires project ID resolution (the MCP handles project name lookup) and valid assignee email/ID. Side-effect: Emma receives a notification. If the project uses custom workflows, the task enters the default 'To Do' status unless you specify otherwise in the prompt.
@Rocketlane log 3.5 hours today on task TSK-4201 with note 'API integration testing and documentation', then summarize my total logged time this week
Time entry created: 3.5 hours logged on January 13, 2025 for task TSK-4201 ('API Integration - Phase 2') with your note attached. Entry ID: TE-9384. Your total logged time this week: 18.5 hours across 12 tasks. Breakdown: 8 hours on integration work (TSK-4201, TSK-4156), 6 hours on customer onboarding tasks, 4.5 hours on internal documentation. You're tracking 3.5 hours above your 15-hour weekly target. This illustrative example shows how the MCP records time and synthesizes weekly activity from multiple entries.
This pairs a write action (create time entry) with read synthesis (weekly summary). Useful for end-of-day logging and workload visibility. The MCP requires valid task IDs and respects your workspace's time-tracking settings (billable/non-billable flags, approval workflows). Rate limit: Rocketlane's API allows ~100 requests/minute, sufficient for typical team usage but consider batching if logging time for multiple tasks.
Use-case deep-dives
When Rocketlane beats spreadsheets for customer handoffs
An 8-person agency onboards 3-5 clients a month, each with a 6-week kickoff checklist. The team used to track tasks in Google Sheets, but handoffs between sales and delivery broke down when someone forgot to update a cell. Rocketlane's Create Company and Create Task tools let the account manager spin up a new project workspace in 90 seconds, pre-loaded with the standard checklist. Time Entry logging shows which clients are eating hours, so the founder can reprice packages mid-quarter. The threshold: if your onboarding is under 10 tasks or you onboard fewer than 2 clients a month, the MCP overhead isn't worth it—stick with a shared doc. But once you're juggling parallel customer projects with overlapping deadlines, Rocketlane's project archival and task deletion keep the workspace clean without losing history. If your team bills by the hour and needs audit trails, this MCP closes the loop.
Why this MCP is overkill for internal dev sprints
A 12-person product team runs two-week sprints and uses Linear for engineering tasks. Someone floats the idea of adding Rocketlane via MCP to track cross-functional dependencies—design handoffs, QA gates, stakeholder reviews. The problem: Rocketlane's 33 tools are built for client-facing project delivery, not internal velocity tracking. The Create Task and Delete Task actions work, but the MCP doesn't surface sprint burndown or story points, and the Time Entry model assumes billable hours, not story estimates. The team ends up with duplicate task lists in two systems. The honest call: if your work is internal and you already have a dev-focused tool, this MCP adds friction. Rocketlane shines when the project has an external customer who needs a shared portal, status updates, and a paper trail. For pure internal sprints, skip it and keep your existing stack.
When time-entry rollups justify the API key setup
A 5-person customer success team manages 40 enterprise accounts, each with quarterly business reviews. The VP needs to show each customer how many hours the team invested in their success plan, broken out by activity type. Rocketlane's Get All Fields and Create Time Entry tools let the CS reps log time against custom categories—onboarding calls, feature training, escalation firefighting—then roll it up by company for the QBR deck. The MCP's Archive Project action keeps closed accounts out of the active list without deleting the time data, so the finance team can still audit last year's utilization. The trade-off: if your CS team doesn't bill by the hour or your QBRs are qualitative (no time breakdowns), the time-entry overhead is busywork. But if you sell professional services or need to justify headcount with utilization metrics, this MCP turns logged hours into a retention story.
Frequently asked
What does the Rocketlane MCP do in Switchy?
It connects your Rocketlane workspace so AI agents can create and manage projects, tasks, companies, and time entries without leaving Switchy. The MCP exposes 33 tools covering project lifecycle operations — from creating new accounts and tasks to archiving completed projects and logging billable hours. Useful for teams running client onboarding or professional services workflows who want AI to handle Rocketlane admin work.
Do I need admin access to connect Rocketlane MCP?
You need a Rocketlane API key, which typically requires admin or super user permissions to generate. The MCP uses API_KEY authentication, so you'll paste the key into Switchy once during setup. Some destructive operations — like deleting projects or tasks — require project owner or admin rights in Rocketlane itself, even after the MCP is connected.
Can the MCP retrieve custom field data from Rocketlane?
Yes. The Get All Fields tool pulls every custom field defined in your Rocketlane workspace, so AI agents can read and reference them when creating or updating projects and tasks. However, the MCP doesn't currently expose a dedicated tool to update custom field values — you'll need to handle that through Rocketlane's UI or a separate API call.
How does this compare to using Rocketlane's native automations?
Rocketlane's built-in automations trigger on fixed events (project status change, task completion). The MCP lets AI agents decide when to act based on conversation context or data from other tools in Switchy. If your workflow is predictable, use Rocketlane automations. If you need AI to juggle Rocketlane alongside Slack, Notion, and GitHub in one workspace, use the MCP.
Who on the team should connect the Rocketlane MCP?
Whoever owns your Rocketlane API keys — usually a workspace admin or the person managing integrations. Once connected, any Switchy team member can invoke the MCP's tools through AI agents, but the actions execute with the permissions of the connected API key. If you want audit trails tied to individual users, connect separate API keys per person.