@launchlint/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| prepare_workspace_scanA | Inspect the approved workspace without uploading it. Returns counts, exclusions, size, and a one-time confirmation token. |
| start_workspace_scanA | Upload the previously prepared workspace snapshot directly to LaunchLint. Requires explicit confirmation and consumes one app check. |
| list_projectsC | Use the authenticated LaunchLint cloud tool list_projects. |
| get_project_statusD | Use the authenticated LaunchLint cloud tool get_project_status. |
| list_findingsD | Use the authenticated LaunchLint cloud tool list_findings. |
| get_fix_taskD | Use the authenticated LaunchLint cloud tool get_fix_task. |
| start_rescan | Use the authenticated LaunchLint cloud tool start_rescan. |
| get_scan_status | Use the authenticated LaunchLint cloud tool get_scan_status. |
| get_submission_checklist | Use the authenticated LaunchLint cloud tool get_submission_checklist. |
| get_usage | Use the authenticated LaunchLint cloud tool get_usage. |
| update_finding_status | Use the authenticated LaunchLint cloud tool update_finding_status. |
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 6 tools
Each tool targets a distinct action: project listing/status, scan preparation/execution, finding listing, and fix task retrieval. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern with snake_case (list_projects, get_project_status, etc.), making predictions easy.
Six tools cover the scanning workflow efficiently: 2 for projects, 2 for scan lifecycle, and 2 for results. Not excessive or sparse.
Covers the core scanning workflow well, but lacks project creation/deletion tools. Minor gap, but agents can still execute scans on existing projects.