MCP Catalogs
← Homejetski screenshot

jetski

by hyprmcp·★ 209·Score 50

An MCP analytics and authentication platform with zero code changes that provides OAuth2.1, real-time logs, and client onboarding.

monitoringsecuritydeveloper-tools
9
Forks
1
Open issues
1 mo ago
Last commit
2d ago
Indexed

Overview

Jetski is a comprehensive analytics and authentication platform for MCP servers that sits in front of your MCP server as a proxy. It solves three critical problems: installation friction by auto-generating setup instructions for various MCP clients, user authentication through OAuth2.1 and dynamic client registration (DCR), and visibility into prompt usage patterns with real-time analytics. The platform captures detailed logs showing which prompts trigger which tools, helps identify user behavior patterns, and enables debugging issues quickly. It works as a Kubernetes-managed gateway that intercepts all MCP traffic without requiring changes to your existing server code.

Try asking AI

After installing, here are 7 things you can ask your AI assistant:

you:Monitoring and analyzing MCP server usage patterns across different clients
you:Implementing OAuth2.1 authentication for MCP servers without code changes
you:Generating client-specific setup instructions to reduce onboarding friction
you:Debugging MCP server issues with real-time logs and analytics
you:What problem does Jetski solve?
you:Does my MCP server need to be modified to use Jetski?
you:What analytics can I expect from Jetski?

When to choose this

Choose Jetski when you need to add authentication and analytics to existing MCP servers without modifying them, and when you want visibility into prompt-tool usage patterns.

When NOT to choose this

Don't choose Jetski if you need fine-grained control over authentication logic beyond OAuth2.1, or if you're building a simple MCP server without advanced monitoring needs.

Comparable tools

mcp-gatewayauth0-mcpokta-mcpcustom-proxy

Installation

Installation

Quick Start with Cloud

Get started with the fully managed HyprMCP Cloud at [https://app.hyprmcp.com](https://app.hyprmcp.com/).

Local Development

  1. Clone the repository:
git clone https://github.com/hyprmcp/jetski.git
cd jetski
  1. Install dependencies:
mise trust
mise install
pnpm i
cp .dex.secret.env.example .dex.secret.env
docker compose up -d
  1. Add host file entry:
echo -e "\n127.0.0.1    host.minikube.internal\n" | sudo tee -a /etc/hosts
  1. Start the platform:

Terminal 1 - Backend:

mise run serve

Terminal 2 - Frontend:

pnpm run start

Generate demo data:

mise run generate

Access at http://localhost:4200 with credentials: admin@example.com / password

Claude Desktop Configuration

To use with Claude Desktop, configure the following in your claude_desktop_config.json:

{
  "mcpServers": {
    "hyprmcp": {
      "command": "npx",
      "args": ["@hyprmcp/mcp-gateway"],
      "env": {
        "HYPRMCP_SERVER_URL": "https://your-server.com",
        "HYPRMCP_CLIENT_ID": "your-client-id"
      }
    }
  }
}

FAQ

What problem does Jetski solve?
Jetski solves three main problems for MCP servers: installation friction by providing auto-generated setup instructions, authentication via OAuth2.1 without code changes, and lack of visibility through analytics and logging of prompt usage patterns.
Does my MCP server need to be modified to use Jetski?
No, Jetski works as a proxy/gateway in front of your existing MCP server with zero code changes required to your server implementation.
What analytics can I expect from Jetski?
Jetski provides comprehensive prompt analytics showing which prompts triggered which tools from which clients, real-time debugging logs, and usage pattern insights to help you understand how users interact with your MCP server.

On Hacker News

Recent discussion from the developer community.

Compare jetski with

jetski vs mcp-server-chartjetski vs everythingjetski vs filesystemjetski vs timejetski vs sequentialthinking
GitHub →

Last updated · Auto-generated from public README + GitHub signals.