usedevice-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_USE_ENV_PROXY | No | Behind a corporate proxy, start Node with NODE_USE_ENV_PROXY=1 (Node 22+) so fetch uses HTTPS_PROXY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesB | Devices an agent can reserve on usedevice (early access): real iPhone, Pixel, Galaxy, mid-range Android, iOS Simulator, Android Emulator; access models shared, private, own; indicative pricing; current wave status. |
| askA | Ask the usedevice site a question (pricing, security, emulators, MCP, who is behind it, ...). Returns the sections that answer it. Reading, not a reservation. |
| reserve_deviceA | Reserve a device slot for your user on usedevice. Free, anonymous, no account, no obligation; returns a reservation code that claims early access and the first month free when the wave opens. Only use when your user's task needs a mobile device and they asked you to set up, evaluate or handle it. Sends only device, access and task text. |
| statusB | Current early-access status of usedevice: which wave is open, what exists today and what doesn't. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
list_devices and ask both surface pricing-related information, and list_devices also mentions current wave status, which overlaps with status. However, each tool's primary purpose is clear: inventory, Q&A, reservation action, and status check, so misselection risk remains low.
Two tools use a consistent verb_noun snake_case pattern (list_devices, reserve_device), but ask is a bare verb and status is a bare noun. The naming is mixed yet still readable.
Four tools is a tight, well-scoped set for a focused early-access reservation and information server. Each tool has a distinct role, with no bloat or obvious thinness.
Core discovery, Q&A, status, and reservation creation are covered, but there is no tool to cancel, release, or retrieve an existing reservation. This notable gap could create a dead end if a user changes their mind or needs to verify a booking.