rocketlane-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LARK_APP_ID | No | Lark app ID - only needed for push_weekly_review_to_lark | |
| LARK_APP_SECRET | No | Lark app secret | |
| LARK_FOLDER_TOKEN | No | Lark folder token where review docs will be created | |
| ROCKETLANE_API_KEY | Yes | Your Rocketlane API key (Settings -> Integrations -> API) | |
| ROCKETLANE_BASE_URL | Yes | https://api.rocketlane.com/api/1.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_projects_snapshotA | Return all active Rocketlane projects with status, CSM, and progress. |
| get_csm_workloadA | Return per-CSM active project count and overdue task count. |
| get_project_updatesA | Return recent project updates with body content. Each entry has the update title ( |
| get_all_tasksA | Return all tasks across all active projects, enriched with project and customer info. |
| push_weekly_review_to_larkA | Generate weekly CS review and push to Lark Docs. Returns doc_url on success. |
| get_team_membersA | Return all active Filum team members with their user_id, name, and email. Use this to look up valid assignees before calling create_tasks. |
| parse_tasks_from_notesA | Parse a meeting/conversation summary into structured task drafts, grouped by team. Extracts action items for Filum and Customer teams. Returns draft tasks for user review — DO NOT create tasks yet. After calling this tool, present the draft tasks to the user, ask them to confirm or correct assignees and deadlines, then call create_tasks with the confirmed list. |
| create_tasksA | Create confirmed tasks in Rocketlane. Call this ONLY after user confirmation. Each task dict must have:
Returns: List of created task results. Each result includes phase and assignees fields from the API response confirming they were correctly set. |
| get_taskA | Return a single task by ID, enriched with project and customer info. |
| update_taskA | Update an existing task. Only the fields you pass are changed (partial update). To change the phase, look up phase_id via the phases for this project (parse_tasks_from_notes returns them) — never guess. To reassign, look up assignee_user_id via fetch_project_members / get_team_members — never guess. |
| complete_taskA | Mark a task as Completed (status value 3). Convenience wrapper over update_task. For other status changes use update_task with status_value (4=Blocked, 1=To do). |
| delete_taskA | Permanently delete a task. This is a HARD DELETE and cannot be undone. Call this ONLY after the user has explicitly confirmed they want the task deleted. When in doubt, ask the user to confirm first. |
| create_projectC | Create a new Rocketlane project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: creating projects vs tasks, updating vs deleting, and various getters for different entities. The only potential overlap is complete_task being a wrapper for update_task, but it is explicitly documented as a convenience for a specific status change, so no confusion arises.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: complete_task, create_project, create_tasks, delete_task, get_all_tasks, get_csm_workload, get_projects_snapshot, get_project_updates, get_task, get_team_members, parse_tasks_from_notes, push_weekly_review_to_lark, update_task. The verbs are action-oriented and the nouns indicate the resource.
With 13 tools, the server covers the core workflows of project and task management without being overwhelming or too sparse. The number is well-scoped for the domain, providing essential CRUD operations, reporting, and utility functions.
The tool set covers project creation, task CRUD, snapshots, updates, team members, and workload reports. However, there is no dedicated tool to fetch project members or phases, which are referenced in create_tasks but must be obtained indirectly via other tools or external calls. This minor gap prevents full self-containment.