Skip to main content

AI Coding Agents

Once the Dashtray MCP server is configured, any AI coding agent can text your phone when it finishes a task. Kick off a long refactor, close the laptop, and get the ping:
“Implement the export feature, and when you’re done notify me on mobile through Dashtray.”
Setup is one-time and global - the server runs on your machine via npx, so the same config works in every project you open afterwards.

Prerequisites

  1. A Dashtray account (no plan needed to sign up; the API requires an active subscription - see pricing)
  2. An API key from Settings → API keys
    • copy it immediately - keys can’t be viewed again

Claude Code (terminal)

The simplest setup of any client - one command, scoped to your user so it works in every project:
Verify with claude mcp list (shows dashtray - ✓ connected), then just ask: “Ping my phone when the tests pass.”

VS Code (Copilot)

Create .vscode/mcp.json in your project (or add it to your user mcp.json for every project):
VS Code uses "servers" (not "mcpServers" like the other clients) and wants an explicit "type": "stdio". Easy to mix up when copying from another tool’s config.

Zed

Add to ~/.config/zed/settings.json:

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

Gemini CLI

Add to ~/.gemini/settings.json:

Any other MCP client

If your tool speaks MCP over stdio, the server config is always the same shape: run npx -y @dashtray/mcp-server with DASHTRAY_API_KEY in the environment. Claude Desktop, Cursor, and Cline have dedicated guides:

Claude Desktop

claude_desktop_config.json setup

Cursor

Cursor MCP setup

Cline

Cline setup

Troubleshooting

Server fails to start inside a monorepo (sh: 1: dashtray-mcp: not found or a silent startup failure): npm’s runner can resolve the npx binary against your workspace’s own node_modules instead of the fetched package. Two fixes:
  1. Install the server globally and point your client at it directly:
    then replace the command with "command": "dashtray-mcp" (no args).
  2. Or set the server’s working directory to a neutral location (for example your home directory) in your client’s MCP config, if it supports a cwd field.
“Invalid API key”: the key is wrong or revoked - generate a new one in API keys. Notifications not arriving: check quiet hours in the app’s notification settings, and note the API rate limits (Starter: 100 requests/min, Pro: 1,000 requests/min).