SkyDemon MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKYDEMON_LOGIN | Yes | Your SkyDemon account email address. | |
| SKYDEMON_PASSWORD | Yes | Your SkyDemon account password. | |
| SKYDEMON_CHARTS_DIR | No | Optional override for the charts directory. | |
| SKYDEMON_ROUTES_DIR | No | Optional override for the routes directory (default: ~/Documents/SkyDemon/Routes). | |
| SKYDEMON_INSTALL_DIR | No | Optional override for the SkyDemon install directory. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| skydemon_loginA | Log in once; session is held in memory and reused (no repeated logins). Args: login: username ('user' or 'user/slot'); defaults to SKYDEMON_LOGIN. password: password; defaults to SKYDEMON_PASSWORD env. force: true to force a fresh login even if a valid session exists. |
| skydemon_session_statusA | Show cached login state (token tail only, never the full secret). |
| skydemon_logoutA | Drop the in-memory session (does not touch SkyDemon's own files). |
| skydemon_api_infoB | Show SkyDemon API base + client identity used by this wrapper. |
| skydemon_list_flightplansA | List saved flightplans on disk (read-only). Default: ~/Documents/SkyDemon/Routes. |
| skydemon_read_flightplanA | Read one flightplan from disk (read-only, no edits). Args: name: file name (e.g. 'EGKK-EGCC.flightplan') or absolute path. |
| skydemon_search_airfieldsA | General airfield search over installed charts (offline, read-only). Matches ICAO exactly / by prefix, then name substring. Biggest airfields rank first. |
| skydemon_airfield_infoA | Full airfield info: offline record (runways, frequencies, fuel, circuits, contacts) + online pilot notes & live feedback text. Online extras need a login session; without one only offline data is returned (online_error set). |
| skydemon_list_cloud_flightplansA | List flightplans in SkyDemon cloud storage (User root, read-only). Args: pattern: server-side filter, e.g. '.flightplan' or '.gpx'. |
| skydemon_download_cloud_flightplanA | Download one cloud flightplan and summarize it (no edits by default). Args: name: exact cloud file name from skydemon_list_cloud_flightplans. save: also save a copy into the local Routes dir. overwrite: allow replacing an existing local file when saving. |
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 10 tools
Tools mostly have distinct purposes: local vs cloud flightplan listing/downloading are clearly separated, and search_airfields vs airfield_info differ by search-vs-detail. The only mild overlap is among the session/diagnostic tools (session_status, api_info, login, logout), but each is still distinguishable.
All tools share a consistent 'skydemon_' prefix and predominantly use a verb_noun pattern (list_flightplans, read_flightplan, search_airfields, download_cloud_flightplan). Minor deviations are noun-style names (session_status, api_info, airfield_info), but overall the convention is predictable.
10 tools is well-scoped for a SkyDemon wrapper, covering session management, local flightplans, cloud flightplans, and airfield lookups without bloat or redundancy.
The surface is deliberately read-only: no create/update/delete of local flightplans and no cloud upload operation, which are natural lifecycle gaps for the domain. Reading, searching, downloading, and auth are covered, so agents can accomplish inspection tasks but hit dead ends for any editing workflow.