SuperCompress MCP OAuth design

Hosted MCP is designed for OAuth 2.1 + PKCE with Google sign-in. The path that works today is the CLI: npm install -g supercompress-proxy then supercompress setup.

October 1, 2026 · Launch note

Connecting SuperCompress to a coding agent should not mean hunting for an API key, editing the right config file, and restarting just to try compression. The hosted MCP URL is designed so an OAuth-capable client can prompt Google sign-in instead of a pasted key.

That OAuth path is how the feature is designed, it is not a promise that every client completes dynamic client registration or browser sign-in end-to-end today. Use npm install -g supercompress-proxy then supercompress setup to wire detected agents, or send a dashboard API key as a header on https://www.supercompress.dev/api/mcp.

Why it matters

The logs, diffs, and huge file reads your agent pulls in go through the hosted query-aware Neural Keep model before they hit the context window. It keeps the lines that actually answer the question, in their original wording, and drops the noise. Your agent stays sharp and your sessions last longer.

Claude Code

Two commands:

/plugin marketplace add Supercompress/Supercompress
/plugin install supercompress@supercompress

Prefer a terminal?

npm i -g supercompress-proxy && supercompress setup

supercompress setup finds the coding agents on your machine and wires them all up.

Hosted MCP URL

https://www.supercompress.dev/api/mcp

Designed as OAuth 2.1 + PKCE, using the same Google account path as CLI device-link. Clients that speak OAuth are meant to get a browser sign-in prompt on connect. Until that path is verified end-to-end in your host, prefer supercompress setup or an API key header.

Coding agents docs → Changelog

Tell me what breaks. I am reading every reply. Arjun