Use My Device As MCP
Give AI secure access
to your devices and data.
UMDAM turns things you own or control into secure Devices that AI agents can use through MCP, without requiring inbound ports or putting private access credentials in an AI conversation.
Start the UMDAM Host
On the computer Device you want your AI to operate:
npx use-my-device@0.2.0-beta.1Connect your AI
Run the Device connection command printed by the Host on the computer with your AI client.
Approve the capabilities
Sign in, review the Device and permissions, then confirm. UMDAM keeps the authorization under your account.
The D in UMDAM
Device first. Data fits naturally.
Use My Device As MCP is the product name and Device is the core domain concept. In UMDAM, a Device is an addressable unit of capability or data that you own or control. For data-backed software, the same D also reads naturally as Use My Data As MCP.
A Device can be physical or logical in the architecture. This release only exposes Computer Devices; other Device kinds are not shown as available until their Provider, security model and end-to-end tests are implemented.
Architecture
Hosts run Providers. Providers give Devices capabilities.
The UMDAM Host is the trusted execution node. A Provider connects a Device to UMDAM, and stable Capabilities describe what AI may read or do. Account authorization and local policy decide which capabilities each AI connection can actually use.
For today's Computer Device, the Host and Device are the same computer. Future Device kinds can be reached through an appropriate Host and Provider without changing the core Device model.
Computer access without surrendering control
Connect multiple Computer Devices, grant each AI connection its own access policy and expiration, and revoke access from your UMDAM console.
Full access is still constrained by the approved Host boundary and the operating-system user running UMDAM. Docker Sandbox can provide a separate execution boundary when configured.