Hosted MCP

Dataplicity exposes a hosted Model Context Protocol server for agent tools such as Cursor. The server runs at https://mcp.dataplicity.com/mcp and uses the same organisation API keys as the Gateway API.

MCP URL	https://mcp.dataplicity.com/mcp
Transport	Streamable HTTP
Auth	Authorization: ApiKey <key> or X-API-Key: <key>
Org context	Derived from the API key (no separate org hash required)

Create a key for MCP

1. Open organisation API keys in the Dataplicity app.
2. Create a key with mcp:read (and mcp:write only if the agent must mutate fleet state).
3. Alternatively grant the underlying scopes (developer:devices:read, fleet_jobs:read, monitors:read, incident_automation:read, and matching write scopes).
4. Copy the plaintext key once and store it in your secret manager or shell environment as DATAPLICITY_API_KEY.

Prefer read-only keys for exploration. Write tools can rename devices, toggle wormhole flags, create or cancel fleet jobs, and bootstrap remote services.

Cursor configuration

Add a remote server to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "dataplicity": {
      "url": "https://mcp.dataplicity.com/mcp",
      "headers": {
        "Authorization": "ApiKey ${env:DATAPLICITY_API_KEY}"
      }
    }
  }
}

Reload Cursor MCP servers, then ask the agent to list devices or inspect offline members of the fleet.

Tool surface (read-first)

Tool	Typical use
list_devices / get_device	Fleet inventory and detail
update_device	Rename or change wormhole flags (mcp:write)
refresh_device_status / get_device_health	Presence and disk health
list_logs	Recent log lines
list_fleet_jobs / get_fleet_job / cancel_fleet_job	Fleet automation jobs
list_monitors / get_monitor	Endpoint and heartbeat monitors
list_wormhole_fleet / get_wormhole_status	Wormhole summaries
get_device_timeline	Device timeline events
get_device_telemetry	Device telemetry samples
Incident automation reads	Rules and insights
get_remote_host / open_remote_service	Remote access bootstrap (open_remote_service is dangerous)

Interactive PTY streaming, arbitrary shell fan-out, billing, and CS-portal internals are intentionally not exposed.

Safety

• Start with mcp:read until you need mutations.
• Treat open_remote_service as privileged: it can open terminal or file services on a device.
• Rotate keys after exposure; never commit plaintext keys to git.
• MCP does not replace the Gateway HTTP API for production backend integrations that need a stable REST contract.

Related

• Organisation API keys
• Gateway authentication
• Gateway fleet overview
• Interactive Gateway reference