MCP Server dev Not Authenticated

Rocks MCP Server

This endpoint serves Rocks tools over MCP for any compatible client. OAuth metadata and token-backed tool access are available from this same host.

Sign in to approve OAuth access and persist your Rocks token for MCP tool calls.

Sign in Refresh

Auth and Token Flow

  1. Client discovers OAuth metadata from the .well-known endpoints.
  2. User signs in and approves access.
  3. OAuth token is exchanged and cached per MCP session/user.
  4. Subsequent MCP tool calls reuse that token until expiration.

MCP Client Notes

Use this server as a Streamable HTTP MCP endpoint in your MCP client configuration.

Use your publicly reachable HTTPS MCP URL for remote clients and OAuth callbacks.

Quick Test

Send an MCP initialize request directly:

curl -X POST "https://old-mcp.fullscale.rocks/" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Operational Notes

Downstream Rocks API auth failures (401/expired token) clear the cached session token. Re-authenticate, then retry the tool call.

Upstream auth URL: https://old-api.fullscale.rocks/auth/token