Dashpilot MCP vs Nahook MCP
A side-by-side look at the Dashpilot MCP and Nahook MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
D
Dashpilot MCPDeveloper Tools · Local subprocess (stdio)DoorDash Drive deliveries over MCP — quote, dispatch, and track deliveries from your POS.52GoodAuth: not declaredVerdict: choose Dashpilot MCP for developer tools work as a local process; choose Nahook MCP for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
DChoose Dashpilot MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DASHPILOT_API_URL, DASHPILOT_API_KEY, DASHPILOT_DRIVE_DEVELOPER_ID, DASHPILOT_DRIVE_KEY_ID, DASHPILOT_DRIVE_KEY. - You want tools like
check_drive_connection, get_delivery_quote, accept_quote.
Choose Nahook MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: other.
- You want tools like
whoami, list_endpoints, get_endpoint.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | D Dashpilot MCP | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | other |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | DASHPILOT_API_URLDASHPILOT_API_KEYDASHPILOT_DRIVE_DEVELOPER_IDDASHPILOT_DRIVE_KEY_IDDASHPILOT_DRIVE_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 17 | 12 |
| Full listing | View Dashpilot MCP | View Nahook MCP |
Tools & capabilities
Dashpilot MCP tools 17
check_drive_connectionVerify your local Drive key (side-effect-free)get_delivery_quoteDelivery fee, tax, ETA — nothing moves yetaccept_quoteAccept a quote — dispatches a real Dasherdispatch_deliveryQuote + accept in one stepschedule_deliveryDeferred dispatch — stores the unsigned payload onlyschedule_batchSchedule a whole event (up to 50, staggered window)dispatch_due_deliveriesPoll the due queue, sign locally (60s JWT), dispatchtrack_deliveryLive status, Dasher info, ETA, tracking URLupdate_deliveryTip / instructions / contact phonecancel_deliveryCancel (Drive cancellation rules apply)batch_dispatchUp to 25 deliveries in one calllist_deliveriesOperations board + scheduled queue- +5 more on the listing page
Nahook MCP tools 12
whoamiLocal config sanity check — workspace, region, token id, expiry.list_endpointsList every endpoint in the current workspace.get_endpointFetch one endpoint by `ep_xxx`.create_endpointCreate a new endpoint. Defaults to the workspace's default environment; also accepts slugs like `production`.update_endpointPartial patch — pause/resume, change URL, update description.list_environmentsList every environment in the workspace.list_deliveriesPage through an endpoint's deliveries, newest-first.get_deliveryFetch one delivery by `del_xxx`. Pass `include_payload: true` to also fetch the original webhook body — critical for debugging.list_attemptsList every attempt against a delivery (useful for debugging failures).retry_deliveryRe-enqueue a failed or dead-lettered delivery.trigger_eventFire an event by type — the backend fans it out to every subscriber.send_to_endpointSend a webhook directly to one endpoint.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Dashpilot MCP
{
"mcpServers": {
"dashpilot-mcp": {
"command": "uvx",
"args": [
"doordash-dashpilot-mcp"
],
"env": {
"DASHPILOT_API_URL": "YOUR_DASHPILOT_API_URL_HERE",
"DASHPILOT_API_KEY": "YOUR_DASHPILOT_API_KEY_HERE",
"DASHPILOT_DRIVE_DEVELOPER_ID": "YOUR_DASHPILOT_DRIVE_DEVELOPER_ID_HERE",
"DASHPILOT_DRIVE_KEY_ID": "YOUR_DASHPILOT_DRIVE_KEY_ID_HERE",
"DASHPILOT_DRIVE_KEY": "YOUR_DASHPILOT_DRIVE_KEY_HERE"
}
}
}
}
Nahook MCP
No confirmed install command for Nahook MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Dashpilot MCP is categorized under Developer Tools and uses a local stdio subprocess. Nahook MCP belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Dashpilot MCP for developer tools work and Nahook MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Nahook MCP has no confirmed install command yet — follow its own setup instructions.
Dashpilot MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Nahook MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dashpilot-mcp and getnahook-nahook-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dashpilot MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Nahook MCP has 48/100 (Fair) with 3 views, 0 installs and 1 GitHub stars.