localsend-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| localsend_devicesA | Scan the local Wi-Fi/LAN for active LocalSend devices and list their aliases, IPs, and models. |
| localsend_sendA | Send files, folders, or direct text/clipboard snippets to a LocalSend device on LAN by alias or IP. |
| localsend_statusA | Inspect local network addresses, active MCP listening port, certificate fingerprint, and inbox status. |
| localsend_historyA | List incoming files received by the LocalSend MCP server inbox. |
| localsend_setupC | Update LocalSend MCP server configuration (alias, download directory, or transport). |
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 5 tools
Each tool targets a distinct concern: device discovery, sending, server status, receiving history, and configuration. There is no overlap or ambiguity between tools.
Names consistently use a localsend_ prefix and snake_case. However, not all follow a strict verb_noun pattern—devices, status, and history are nouns while send and setup are verbs—so it is mostly consistent with minor deviation.
Five tools is well-scoped for a focused LocalSend integration. Each tool covers a necessary capability without redundancy or bloat.
The set covers the full local workflow: discovering devices, sending content, checking server status, reviewing received files, and updating configuration. No major gaps are apparent for the stated purpose.