Skip to main content
Use this page when Kyberis skill installation or MCP connection fails.

​
Node.js is too old

Both npm setup tools require Node.js 20 or newer with npx.
Upgrade Node.js if the version is below 20.

​
Connect Token is Invalid or Expired

Generate a new one-time connect token from API keys when setup reports: Use --print-config to print manual installation guidance without updating local client files.
--dry-run and -n are compatibility aliases for --print-config. These commands still exchange and spend the one-time connect token, register the MCP client, and create server-side credentials; they only skip local client configuration changes. Use --json when you need machine-readable connection details. It also exchanges and spends the connect token.
If the JSON includes api_key_id and api_key_secret_retrievable is true, the installed MCP configuration uses direct API-key auth. If api_key_secret_retrievable is false, the exchange used a legacy bearer fallback. The API key secret was not returned and cannot be retrieved later, so create a separate API key in the dashboard when you need Authorization: ApiKey <key_id>:<secret> for direct REST API calls.

​
Agent does not show Kyberis tools

Check the client’s MCP config file: For Claude, rerun setup with --print-config and verify the printed claude mcp add command. Restart or reload the agent after changing MCP configuration.

​
Agent does not Follow the Kyberis Workflow

Check whether the skill is installed:
Refresh installed skills with:

​
API Calls Return 401

401 usually means credentials are missing, invalid, or expired. Reconnect MCP with a fresh connect token so the agent receives a current MCP credential.

​
API Calls Return 403

403 usually means the current MCP credential is missing required scopes. Check missing_scopes first; it lists the scopes your current credential lacks. required_scopes lists the full scope set required by the endpoint or tool. To fix the connection:
  1. Open API keys.
  2. Create or update an API key that includes the missing_scopes.
  3. Associate the MCP connection with that API key.
  4. Reconnect MCP so direct API-key clients receive an updated local credential.

​
API Calls Return 429

Back off and honor retry_after_seconds when present. Repeated bad authentication attempts can also trigger 429.

​
Report a Setup Issue

When asking for help, include:
  • agent client and version
  • setup command used, without secrets
  • request_id, run_id, and step_id from any failed Kyberis call
  • relevant error code and message