localsend-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCALSEND_CLI | No | Absolute path to localsend-cli as a fallback sender. | |
| LOCALSEND_MCP_CONFIG | No | Path to a custom config JSON file. | |
| LOCALSEND_INBOX_ALIAS | No | Alias for the inbox receiver when running localsend-mcp-inbox. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| localsend_scanA | Scan the local LAN for active LocalSend receivers and return aliases, IP addresses, ports, and protocols. |
| localsend_sendC | Send one or more absolute file paths to a LocalSend target by alias, IP, host:port, or URL. |
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 2 tools
The two tools have clearly distinct purposes: one scans for receivers, the other sends files. There is no possible confusion between them.
Both tools follow a consistent snake_case pattern with the 'localsend_' prefix and a clear verb: 'scan' and 'send'.
Two tools is minimal but acceptable for a focused server that only handles scanning and sending. However, it feels thin compared to the broader file-sharing domain.
The server provides only sending capabilities; receiving files is entirely missing. This is a significant gap for a file-sharing tool, as agents cannot complete a full send-receive workflow.