MCP

Authentication

How the Skytells MCP maps CLI credentials to tools, and why credential values are never returned to the client.

The MCP never returns credential values. The Skytells CLI supports three independent credentials, and the local MCP server uses whichever ones are already configured for the CLI on your machine.

OperationsCredential
Account and user projectsskytells login or SKYTELLS_TOKEN
Linked-project resourcesskytells link <key> or SKYTELLS_ACCESS_KEY
Models and predictionsskytells api-key set or SKYTELLS_API_KEY

Models and predictions require the separate Skytells API key — it is not interchangeable with the personal access token or project access key.

Interactive login and API-key entry must run in the user's terminal. Calling skytells_auth_setup returns the correct command and Console URL rather than attempting to collect credentials itself.

  • Local Installation — set up the local server that consumes these credentials.
  • CLI: Auth — configure login, link, and api-key set from the terminal.
  • Tools Reference — which tools require which credential.

How is this guide?

Local installation

Run the Skytells MCP server locally with npx for authenticated tools covering projects, deployments, and predictions.

Tools

Every public and local tool exposed by the Skytells MCP, including skytells_run for complete CLI coverage.

On this page

Related