serverkit-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_serversA | Broadcast on the local network to find ServerKit phones running the MCP server. Returns a list of { name, url }. If it comes back empty, no phone answered - ask the user for the ip:port shown in their ServerKit app instead of retrying. |
| connectA | Connect to a ServerKit MCP server at the given URL (e.g. from discover_servers, or an ip:port the user gave you - format it as http://:/mcp). Call this before start_session/run_command. |
| disconnectB | Disconnect from the current ServerKit server. |
| start_sessionA | Start a tool-use session on the connected ServerKit server. Must be called once before run_command/run_command_sudo will do anything. If the server replies that a PIN is required, ask the user for it and call this again with the pin argument. |
| end_sessionB | End the current tool-use session on the connected ServerKit server. |
| run_commandA | Run a shell command on the server ServerKit is connected to over SSH. Requires start_session first. Blocked if the command invokes sudo/doas/su/pkexec. |
| run_command_sudoA | Run a shell command with sudo permitted. Only works if the phone owner enabled sudo tools in the app - if it errors as unknown, that tool is disabled there. |
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 7 tools
Each tool maps to a distinct stage in a clear lifecycle: discovery, connection, session, and command execution. The only near-overlap is run_command vs run_command_sudo, but the sudo distinction is spelled out explicitly in both descriptions. An agent can easily pick the right tool at each step.
Almost everything follows a consistent snake_case verb_noun pattern (discover_servers, start_session, end_session, run_command, run_command_sudo). The only minor deviations are the bare connect/disconnect pair, which are still predictable and readable, plus the _sudo suffix variant.
Seven tools is well-scoped for a remote-command bridge: discovery, connection management, session management, and command execution. Every tool earns its place with no redundant or filler entries.
The connection-to-command lifecycle is fully covered (discover, connect, start/end session, run, run with sudo). Minor gaps exist around introspection such as checking connection/session status or transferring files, but core workflows have no dead ends.