warp-drive-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 |
|---|---|
| search_warp_drive_docsA | Search WarpDrive and EmberData documentation for any API, class, function, or concept. Use this tool when you need to know:
Always use this before writing WarpDrive code to avoid hallucinating APIs. |
| get_warp_drive_packageA | Get complete documentation for a specific WarpDrive or EmberData package. Use this when you need full details about a specific package like:
|
| get_warp_drive_overviewA | Get a high-level overview of all WarpDrive packages and what they do. Use this when:
|
| get_warp_drive_guideA | Search WarpDrive guides, tutorials, and cookbook recipes. Use this for "how do I..." questions like:
|
| check_warp_drive_deprecationsA | Check if a WarpDrive or EmberData API is deprecated and find its replacement. Use this when:
Common deprecations to check:
|
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 5 tools
Each tool has a clearly distinct purpose: searching docs, getting package details, getting an overview, finding guides, and checking deprecations. There is no overlap in their target use cases.
All tool names follow a consistent verb_noun pattern with 'warp_drive' in the middle, making the naming style uniform and predictable.
With 5 tools, the server is well-scoped for documentation lookup. Each tool covers a necessary aspect of documentation access without redundancy or bloat.
The tool set covers searching, package details, overviews, guides, and deprecations—covering the full documentation lifecycle for WarpDrive and EmberData. There are no obvious gaps for typical documentation queries.