MCP.so
Sign In

DeviceLink MCP ServerVerifiedFeatured

@Jayanka Sampath

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Files & Storage

Author

Jayanka Sampath

Submitted by

Jayanka Sampath

About DeviceLink MCP Server

DeviceLink lets you share folders from your computer with AI assistants, securely and in real-time. Nothing is uploaded. Your files stay on your machine, and are only accessible while the device sharing them is connected - your agent while it runs, or a browser tab while it stays open.

Connection details

https://mcp.devicelink.ai/mcp

Setup

claude mcp add devicelink --transport http https://mcp.devicelink.ai/mcp

DeviceLink MCP Server tools

4

Simple health check — returns server status.

Discover workspaces, devices, shared folders, and available tools in one call. Call this first to understand what is available before invoking device_tool_call. Automatically selects workspace, device, or folder when only one option exists; returns a list of choices when disambiguation is needed.

Execute a tool on a connected device. Use discover first to find available tool names, device IDs, and workspace IDs. When workspace_id, device_id, or directory_id are omitted, the server uses the unambiguous default if one exists.

Check that a device is reachable and how long a round trip takes. Reads no files, needs no shared folder and consumes no credit, so it is the safe way to prove a device is live.

Overview

What is DeviceLink

DeviceLink gives an AI assistant read access to folders on your own computer.

Most AI clients cannot see your local files at all. Claude and ChatGPT in a browser or on a phone run in the cloud, with no path to your disk. DeviceLink is that path: you choose a folder, and your assistant can read what is inside it - and nothing else.

Your files are never uploaded, copied or stored. They are read on your machine, in response to a request you made, and streamed straight back into the conversation.

How it works

There are two ways to connect a folder. Both end up at the same place.

From your browser - nothing to install. Open devicelink.ai, sign in, and share a folder. Your operating system shows its own permission dialog, you pick the folder, and your browser tab becomes the connected device. It stays connected while that tab is open. This takes a few seconds and needs no terminal, no download and no admin rights.

With the DeviceLink agent - stays connected. Install the agent if you want the connection to survive closing the tab, or if you want to reach a machine you are not sitting at. It runs on macOS, Windows and Linux.

Either way you stay in control: the folders you shared are the only ones visible, and closing the tab or quitting the agent revokes access immediately.

What your assistant can do

DeviceLink configures its tool surface per device, so an assistant is offered only what that device actually supports. Every device provides:

ToolWhat it does
fs_listList the entries in a shared folder
fs_readRead a single file
fs_infoSize and modified time, without reading contents
dl_pingCheck the device is responding

A machine running the DeviceLink agent can offer more, including recursive listing and search across the folder.

Every tool is read-only. Nothing in DeviceLink can write to, move, rename or delete a file. That is not a limitation waiting to be lifted - it is the boundary the product is built on.

Security

Trust is the whole point of a product that reads your files, so the design is deliberately narrow:

  • Read-only. No tool writes. Nothing can be modified or destroyed.
  • Scoped to what you picked. Access is confined to the folders you shared. Paths outside them are refused, and the check is applied per path, in code - not left to the model's judgement.
  • Consent from your own OS. The browser route uses the operating system's native folder-permission dialog. Your machine asks, you answer, and the scope is whatever you chose.
  • Nothing stored. File contents pass through in response to a request and are not retained.
  • Revoke instantly. Close the tab or stop the agent. Access ends with it.
  • OAuth 2.1 with PKCE, dynamic client registration (RFC 7591) and token revocation (RFC 7009).

Getting started

  1. Open devicelink.ai and sign in.
  2. Add the DeviceLink connector to your AI client, or use the server URL above.
  3. Share a folder - from your browser, or by installing the agent.
  4. Ask your assistant to read something in it.

New accounts start with free credits, so you can try it before paying for anything.

Requirements

  • The browser folder picker needs a Chromium-based browser such as Chrome or Edge.
  • The DeviceLink agent runs on macOS, Windows and Linux.
  • Works with any MCP client that supports remote servers over streamable HTTP, including Claude, ChatGPT, Cursor, Copilot, Windsurf and Cline.

Links

Frequently asked questions

1

What is the DeviceLink remote MCP server?

The DeviceLink remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.devicelink.ai/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the DeviceLink MCP server?

Add the endpoint https://mcp.devicelink.ai/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the DeviceLink MCP server require authentication?

Yes. DeviceLink uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the DeviceLink MCP server use?

DeviceLink exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments