@skynode/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKYNODE_TOKEN | Yes | Required. Your personal token, starting with sky_ | |
| SKYNODE_API_URL | No | Optional. Default is https://api.skynode.africa/api/v1 | https://api.skynode.africa/api/v1 |
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 |
|---|---|
| list_serversA | Liste les serveurs (VPS) du compte SkyNode : nom, adresse IP, état, identifiant. À appeler en premier pour savoir sur quelle machine travailler. Lecture seule. |
| server_statusA | Détaille un serveur : état, adresses IP, système, région, utilisateur SSH, échéance de facturation. L’identifiant s’obtient avec list_servers. Lecture seule. |
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 are clearly distinct: list_servers provides a high-level overview of all servers, while server_status gives detailed information for a specific server. There is no ambiguity in their purposes.
Naming is not fully consistent: list_servers follows a verb_noun pattern, while server_status uses a noun_phrase without a verb. Both are readable, but the mixed patterns make the set slightly less predictable.
With only two tools, the server is minimal but appropriate for a read-only server information utility. However, it feels thin if broader server management capabilities are expected.
For a read-only toolset, it covers the essential operations: listing all servers and retrieving detailed status for one. Missing actions like start/stop are out of scope, but the read-only domain is well covered.