ellmos-servercommander-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVERCOMMANDER_LANG | No | Language for localized tool descriptions. Allowed values: en, de, es, zh, ja, ru. Default is en. | |
| SERVERCOMMANDER_CONFIG | No | Path to a custom configuration file. Defaults to ~/.servercommander/config.toml or ~/.config/servercommander/config.toml. | |
| SERVERCOMMANDER_LOCALE | No | Alternative environment variable for language. Same as SERVERCOMMANDER_LANG. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sc_deployB | Build a safe deployment plan. Alpha only: execution requires dry_run=true. |
| sc_deploy_statusC | Show configured deployment profiles and alpha deployment-history status. |
| sc_mail_listC | Alpha mail status endpoint for listing an IMAP folder. |
| sc_mail_readC | Alpha mail status endpoint for reading a message. |
| sc_mail_sendC | Alpha mail status endpoint for sending mail; does not send yet. |
| sc_mail_searchC | Alpha mail status endpoint for searching mail. |
| sc_logs_analyzeB | Analyze Apache/Nginx access logs from inline text or a local file path. |
| sc_health_checkB | Check HTTP endpoints and return status codes plus latency. |
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 8 tools
Each tool targets a fairly distinct area: deploy vs deploy_status differ by planning versus status inspection, and the four mail tools split cleanly along list/read/send/search. The main risk is sc_deploy vs sc_deploy_status, which could be confused at a glance, but descriptions clarify the boundary.
All tools share an sc_ prefix and snake_case, with mostly predictable noun_verb ordering (sc_mail_list, sc_health_check, sc_logs_analyze). sc_deploy is a bare verb outlier and the mail_* group reads as noun_action rather than verb_noun, but the scheme is readable and consistent overall.
Eight tools is well within a sensible range for a server-commander surface spanning deploy, mail, logs, and health. No obvious redundancy or padding, though half the set is devoted to mail operations that are still alpha stubs.
Mail coverage (list/read/send/search) and deploy (plan + status) are reasonably complete, but several operations are explicitly non-functional alpha status endpoints (send 'does not send yet') and there is no log tailing/filtering beyond one-shot analysis. The server-commander domain lacks service restart, config, or process-management operations, leaving notable gaps.