jetski

Authentication, analytics, and prompt visibility for MCP servers with zero code changes. Supports OAuth2.1, DCR, real-time logs, and client onboarding out of the box

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

View docs

Command

claude mcp add --transport stdio hyprmcp-jetski docker run -i hyprmcp/jetski:latest \
  --env JETSKI_PORT="8080" \
  --env JETSKI_CONFIG="path or JSON configuration for Jetski" \
  --env JETSKI_LOG_LEVEL="info"

How to use

Jetski is an open source MCP analytics and authentication platform that sits in front of your MCP server and collects analytics while easing client onboarding, authentication, and visibility. It provides zero-code authentication, real-time debug logs, and auto-generated setup instructions for MCP clients. The included gateway orchestration helps you deploy and manage instances of the MCP gateway that sits in front of your MCP server, giving you centralized analytics and controlled access. To get started, run Jetski in a container (via Docker) and connect your MCP server behind the Jetski gateway so requests flow through the proxy where authentication, prompts analytics, and tooling orchestration are applied. Use the built-in tooling to generate per-client connection instructions and observe real-time logs to troubleshoot issues.

How to install

Prerequisites:

Docker and Docker Compose (optional for orchestration)
Git
Basic familiarity with MCP concepts (prompts, tools, and clients)

Installation steps:

Clone the Jetski repository: git clone https://github.com/hyprmcp/jetski.git cd jetski
Pull and run Jetski using Docker: docker pull hyprmcp/jetski:latest docker run -d --name jetski -p 8080:8080 -i hyprmcp/jetski:latest
Configure Jetski to point at your MCP server behind the gateway:
- Edit the Jetski configuration file or environment variables as needed (JETSKI_CONFIG, JETSKI_PORT, etc.).
- Ensure your MCP server is accessible from the Jetski deployment (network/firewall rules).
(Optional) If you prefer local development without Docker, install prerequisites and build from source according to the repository's development guide, then run the built binary following the provided instructions in the docs.
Verify operation:
- Access the Jetski UI or API endpoints as documented in the project docs.
- Check logs for health/status messages and connect an MCP client to verify analytics and authentication flows.

Additional notes

Tips and common considerations:

Jetski is under active development; APIs and CLI may change. Keep an eye on the official docs for breaking changes.
When running behind Kubernetes or a reverse proxy, ensure proper TLS termination and header forwarding as required by the gateway.
Use the environment variables to fine-tune logging, ports, and configuration paths. Start with safe defaults and increase verbosity only for debugging.
If you encounter connectivity issues, confirm that the MCP server is reachable from the Jetski deployment and that the gateway is correctly proxying authentication prompts to the appropriate endpoints.