Skip to main content
Glama
zampou-code

@skynode/mcp

by zampou-code
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

@skynode/mcp

Serveur MCP qui donne à votre agent de code — Claude Code, Cursor, Codex — la visibilité sur vos serveurs SkyNode.

Ce paquet est en lecture seule : il liste vos serveurs et rend leur état. Il ne modifie rien, n'ouvre aucune session SSH, et ne peut ni commander ni payer.

Installation

Créez d'abord un jeton d'accès personnel dans votre espace client, sur /compte/securite, en cochant la portée « Lire mes serveurs et leur état ». La valeur n'est affichée qu'une seule fois.

Claude Code

claude mcp add skynode --env SKYNODE_TOKEN=sky_votre_jeton -- npx -y @skynode/mcp

Cursor, Windsurf, Codex

Dans la configuration MCP de votre client :

{
  "mcpServers": {
    "skynode": {
      "command": "npx",
      "args": ["-y", "@skynode/mcp"],
      "env": { "SKYNODE_TOKEN": "sky_votre_jeton" }
    }
  }
}

Related MCP server: Akamai Cloud MCP Server

Outils

Outil

Ce qu'il fait

list_servers

Liste vos serveurs : nom, adresse IP, état, identifiant

server_status

Détaille un serveur : état, IP, système, région, échéance

Variables d'environnement

Variable

Rôle

SKYNODE_TOKEN

Requis. Votre jeton personnel, commençant par sky_

SKYNODE_API_URL

Facultatif. Par défaut https://api.skynode.africa/api/v1

Le jeton se déclare par variable d'environnement, jamais en argument de ligne de commande : les arguments d'un processus sont lisibles par tout utilisateur de la machine.

Ce que SkyNode ne voit pas

Ce serveur tourne sur votre machine. SkyNode ne reçoit que les appels d'API classiques de votre compte — les mêmes que ceux de votre espace client.

Développement

pnpm install
pnpm test
pnpm build

Pour l'essayer contre une API locale :

SKYNODE_API_URL=http://localhost:3001/api/v1 SKYNODE_TOKEN=sky_… node dist/index.js

Licence

MIT

Available Tools

2 tools
list_serversLister mes serveurs SkyNodeA

Liste les serveurs (VPS) du compte SkyNode : nom, adresse IP, état, identifiant. À appeler en premier pour savoir sur quelle machine travailler. Lecture seule.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses read-only nature ('Lecture seule') and enumerates the returned fields (name, IP, state, ID), offering useful behavioral context beyond the empty schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact—two sentences—with the main purpose front-loaded and no superfluous content. Every sentence contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation with no parameters and no output schema, the description provides essential information: what is returned, that it is read-only, and when to use it. It adequately covers the tool's context given its simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool accepts zero parameters, so there is no parameter semantics to convey. The baseline for no parameters is 4, and the description correctly omits any parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists SkyNode VPS servers with their name, IP, state, and ID, using the specific verb 'list' and resource 'servers (VPS) of the SkyNode account'. It also differentiates from the sibling tool 'server_status' by indicating it should be called first to know which machine to work on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to call this tool first to determine the machine to work on, providing clear usage context. It does not explicitly mention exclusions or alternatives, but the sequencing guidance is sufficient for typical workflows.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

server_statusDétail d’un serveur SkyNodeA

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
server_idYesIdentifiant du serveur, tel que rendu par list_servers

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of disclosing behavior. It explicitly states 'Lecture seule' (read-only) and enumerates what information is returned. It does not discuss errors or permissions, but for a read-only detail endpoint this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with the tool's purpose and output fields. Every word earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read-only tool with no output schema, the description fully covers what the tool does, what it returns, and how to obtain the required ID. It is complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines server_id. The description adds value by telling the agent that the ID comes from list_servers, which is genuinely useful contextual information beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses the specific verb 'Détaille' with a clear resource ('un serveur') and lists concrete attributes (état, adresses IP, système, etc.). It clearly distinguishes itself from list_servers by focusing on a single server's detailed status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent to obtain the identifier via list_servers, establishing a clear usage flow. It does not mention when not to use it, but for a simple detail lookup the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0
Disambiguation5/5

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 Consistency3/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Bitcoin Node MCP Server

    andy-builds-ai
    A
    license
    Not graded
    quality
    C
    maintenance
    Read-only MCP server that monitors a Bitcoin Core full node via JSON-RPC, providing tools to check node status, network info, mempool, and peer information.
    MIT

  • Cartrack MCP

    KhulaNode
    A
    license
    Not graded
    quality
    C
    maintenance
    A read-only MCP server for Cartrack fleet management, enabling listing vehicles and checking their last-known status and location.
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zampou-code/skynode-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server