Welcome to Rocks MCP

This service exposes Rocks tools to MCP clients. Authentication is session-based and tokens are scoped to each MCP session.

Sign in Refresh

How MCP Auth Works

  1. Your MCP client connects to this server.
  2. The auth tool receives your credentials (or bearer token).
  3. The tool calls Rocks API at https://preprod-api.fullscale.rocks/auth/token.
  4. The response token is cached using your MCP session_id.
  5. Other tools reuse that token for Rocks API calls until expiration.

Supported Login Response

The auth tool expects access_token and also stores metadata like token_type, expires_in, refresh_token, login_session_id, and user_platform.

Operational Notes

If a downstream Rocks API call returns 401, the session token is cleared and the client must authenticate again before retrying tools.