Pre-release integration map

Bring context efficiency to the workflow you already run.

CutCtx source includes SDKs, compatible proxy routes, local CLI wrappers, MCP tools, gateways, and IDE setup paths. Availability and live acceptance depend on the host, auth mode, provider, and beta scope.

Private beta · Access by request · Host-specific support

Choose the access surface

One platform, several ways in.

SDK, proxy, wrapper, and MCP paths expose different parts of CutCtx. Available compression, retrieval, policy, and telemetry depend on the selected integration and configuration.

SDKs

Application clients

Python, TypeScript, and Go client implementations exist in source. Public PyPI and npm packages are not currently available; confirm source access and installation with the beta team.

Compatible paths

Provider-aware proxying

OpenAI, Anthropic, and Gemini-compatible adapters exist in source. Live inference acceptance varies by account, auth mode, and client path; a configured endpoint alone is not proof of processing.

CLI and agents

Host-specific coverage

Claude Code and Codex have documented live checks for specific configurations. Other wrappers include experimental paths. Confirm your client version, authentication mode, and provider with the beta team before relying on a workflow.

MCP and gateways

Connect tools and retrieval

MCP tools and gateway paths can process tool results where enabled. MCP availability does not mean model inference requests pass through the CutCtx proxy.

IDE operations

Setup paths vary

VS Code and JetBrains integration code is available, but catalog entries and configuration paths do not establish live client acceptance.

Customer deployment

Choose the beta boundary

Local, Docker/Compose, and Kubernetes deployment paths exist in source; setup and acceptance must be confirmed for the supplied beta build.

Cursor and experimental host limits

Cursor model proxying is scoped to BYOK paths. Cursor subscription inference is not processed by CutCtx, and Cursor Agent subscription access is MCP-only. Other catalogued hosts are integration mechanisms, not blanket live support; ask the beta team to confirm the exact host and authentication path.

A practical evaluation

Start with one confirmed workflow.

Use a source checkout supplied for the beta, configure the host and auth path confirmed for your account, then inspect local request evidence.

01
Install

Build from the supplied checkout; Python 3.10+ and Rust are required.

02
Configure

Use the host, auth, SDK, proxy, or MCP path confirmed for your beta scope.

03
Inspect

Separate local token estimates from provider billing, cache, routing, retrieval, and task-quality outcomes.

Next step

Confirm your host and auth path.

Request beta access for the source checkout and integration scope that match your environment.