MCP Tools

Dashtray MCP tools reference

MCP Tools

Complete reference for tools available via Dashtray MCP.

send_notification

Send a notification to your device via Claude Desktop or Cline. Notifications appear on your phone with an MCP - prefix and are also logged in your history.

Parameters

Parameter	Type	Required	Description
title	string	Yes	Notification title (1–200 chars). Shown with an MCP - prefix in the app
body	string	Yes	Notification body/details (1–500 chars). Can include status, error details, links, etc.

Limits are enforced by the MCP server itself (matching the Dashtray API), so oversized input fails fast with a clear message.

Response

{
  "ok": true,
  "data": {
    "id": "notif_abc123",
    "title": "Build Complete",
    "body": "Your build succeeded in 2m 45s",
    "createdAt": 1710000000000
  }
}

Error Response

{
  "ok": false,
  "error": "Error description"
}

Examples

Basic Notification

title: "Build Complete"
body: "Your build succeeded in 2m 45s"

Deployment Notification

title: "Deployment Successful"
body: "Version 1.2.0 is now live"

Warning Notification

title: "API Rate Limit Warning"
body: "You've used 90% of your monthly quota"

Error Notification

title: "Build Failed"
body: "Jest tests failed in /src/components"

Usage in Claude Desktop

When connected to Dashtray MCP, Claude can send notifications like:

Prompt:

Send me a notification saying I'm done with this analysis

Claude Response:

I'll send you a notification about completing the analysis.
[Calls send_notification with title and body]
Notification sent successfully!

Usage in Cline

When running automation, Cline can send status updates:

Cline: "Starting deployment..."
Cline: [sends notification about progress]
Cline: "Deployment complete"
Cline: [sends notification about completion]

Constraints and Limits

Per Notification:

• Title: 1–200 characters
• Body: 1–500 characters

Per Account (per API key, per minute):

• Starter: 100 requests/minute
• Pro: 1,000 requests/minute

Error Handling

Validation Failed:

• Missing title or body returns an error (both are required)
• Titles over 200 chars or bodies over 500 chars are rejected

Rate Limited:

• If you exceed your limit, you’ll receive a 429 error
• Wait for the limit window to reset
• Consider upgrading your plan

Best Practices

✅ Do:

• Use descriptive titles and concise bodies
• Keep status, error details, or links in the body
• Space out notifications for readability

❌ Don’t:

• Send spam or duplicate notifications
• Use excessively long bodies
• Abuse the tool for non-critical updates
• Ignore rate limit errors

Integration Example

# In your agent/automation
agent.addTool(
  name="send_notification",
  description="Send a notification to user's device",
  parameters={
    "title": "string - notification title (required)",
    "body": "string - notification body (required)"
  }
)