Leapd MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEAPD_API_KEY | Yes | Your key from your Leapd dashboard | |
| LEAPD_API_BASE | No | Must be an https:// Leapd host, or localhost for development | https://api.leapd.ai |
| LEAPD_TIMEOUT_MS | No | Per-request timeout, capped at 10 minutes | 120000 |
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 |
|---|---|
| launch_businessA | Turn an idea into a live business on Leapd: positioning, a deployed landing page, and a day-one plan of concrete tasks. Returns the public URL. Call this once — use get_workspace afterwards. |
| get_workspaceA | Current state of your business: live URL, deployment and domain status, plan day, and a summary of what is in flight. |
| list_tasksA | The current plan — what is queued, running, blocked, or done. Blocked tasks include the reason so you know what to unblock. |
| create_taskA | Add work to the plan — a page to build, a piece of research, a fix. The task is executed by Leapd, not by this MCP server. |
| run_taskA | Start a queued task immediately instead of waiting for its scheduled slot. Returns as soon as the task is dispatched — poll list_tasks for the outcome. |
| list_documentsA | Artifacts Leapd has produced — positioning, customer profile, roadmap, research. Returns slugs and titles; use get_document to read one. |
| get_documentA | Full contents of one document Leapd produced for your business. |
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 7 tools
Each tool targets a distinct resource and action: launch_business creates, get_workspace reads business state, list_tasks/create_task/run_task manage tasks, and list_documents/get_document manage documents. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (launch_business, get_workspace, list_tasks, create_task, run_task, list_documents, get_document). The conventions are uniform and predictable.
Seven tools is well within the ideal 3-15 range and appropriately scoped for the server's purpose of launching and managing a small business on Leapd. Each tool earns its place.
The core lifecycle is covered: launch, inspect workspace, manage tasks (list/create/run), and access documents (list/read). Minor gaps include no direct way to update or cancel a task, but the primary workflows are supported and agents can work around this.