Skip to content
MCP server

Device Magic MCP by usefulapi

Read Device Magic forms, submissions, devices and groups; send and revoke dispatches.

Install
Runs
Remotely
Version
1.19.0
Listing updated
4 days ago

About Device Magic MCP by usefulapi

Device Magic MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.

Install

Run in a terminal

claude mcp add --transport http device-magic https://device-magic.usefulapi.io/mcp

Add to Settings → Connectors → Add custom connector

https://device-magic.usefulapi.io/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "device-magic": {
      "url": "https://device-magic.usefulapi.io/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "device-magic": {
      "type": "http",
      "url": "https://device-magic.usefulapi.io/mcp"
    }
  }
}

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

{
  "mcpServers": {
    "device-magic": {
      "serverUrl": "https://device-magic.usefulapi.io/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "device-magic": {
      "type": "http",
      "url": "https://device-magic.usefulapi.io/mcp"
    }
  }
}

Tools this server provides (17)

Read directly from the server.

devicemagic_list_forms
List the organization's forms: id, namespace (the form's unique id used for dispatching), version, description and group. GET /organizations/{org}/forms.json.
devicemagic_get_form
One form's definition: title and its questions/pages with identifiers and types (the identifiers are the keys inside submissions and dispatch payloads). Optionally a specific version. GET /organizations/{org}/forms/{id}.json.
devicemagic_list_submissions
Submitted data of one form, newest data as stored in the form's Device Magic Database destination (it must be active on that form). Each record has form info, metadata (device, user, submitted_at, received_at, submission_id) and the answers. The reply says current_page, total_pages and total_count. Filter by from_date/to_date (yyyy-mm-dd). GET /api/forms/{id}/device_magic_database.json.
devicemagic_list_devices
List the organization's devices (phones, tablets, web-form users): id, identifier, owner, description, group and whether approval is pending. GET /organizations/{org}/devices.json.
devicemagic_get_device
One device: id, identifier, owner, description, pending_approval, groups and custom attributes. GET /organizations/{org}/devices/{id}.json.
devicemagic_list_groups
List the organization's groups (which devices see which forms), optionally narrowed by a name filter or by tags. GET /api/v2/organizations/{org}/groups.json.
devicemagic_list_resources
List the organization's resources (lookup tables and files used by forms): id, original filename, version, description. GET /api/resources.json.
devicemagic_describe_resource
Metadata of one resource: status, version and, for spreadsheets, its tables and columns. The file content itself is not downloaded. GET /api/resources/{id}/describe.json.
devicemagic_list_destinations
List where one form's submissions are sent (e-mail, Dropbox, database, ...): id, active flag, format and transport types, timestamps. GET /api/forms/{id}/destinations.json.
devicemagic_get_destination
One destination of a form. Credentials and tokens of the destination are never returned. GET /api/forms/{form_id}/destinations/{id}.json.
devicemagic_list_dispatches
Outstanding dispatches (prefilled forms pushed to devices and not yet completed) of the whole organization: id, form name and namespace, device, scheduled time. Dispatch is an Enterprise-plan feature. GET /api/v2/organizations/{org}/dispatches.json.
devicemagic_list_device_dispatches
Outstanding dispatches of one device. GET /api/v2/devices/{identifier}/dispatches.json.
devicemagic_get_dispatch
One dispatch of a device including the values it was prefilled with. GET /api/v3/devices/{identifier}/dispatches/{id}.json?include_inputs=true.
devicemagic_list_dispatch_recipients
Devices and web-forms users a dispatch can be sent to (first 100 by default; use items and page for more). GET /api/v3/dispatch_authors.json.
devicemagic_send_dispatch
WRITE: pushes a form, optionally prefilled, to one device where its user will see it (like assigning a job). Not idempotent: calling it twice sends two dispatches. Needs the Enterprise plan. The form is named by its namespace (list_forms); `payload` maps question identifiers (get_form) to prefilled values (subforms = nested objects, repeat groups = arrays). POST /api/v2/devices/{identifier}/dispat
devicemagic_revoke_dispatch
WRITE: withdraws one outstanding dispatch from a device (the form disappears from the device). It cannot be undone, but the dispatch can be sent again. DELETE /api/v2/devices/{identifier}/dispatches/{id}.json.
devicemagic_approve_device
WRITE: approves a device that is waiting for approval (pending_approval is true) so it can receive forms. Approving an approved device has no effect. POST /organizations/{org}/devices/{id}/approve.

Device Magic MCP by usefulapi FAQ

How do I add Device Magic MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http device-magic https://device-magic.usefulapi.io/mcp