Verified integration surfaces

Bring context efficiency to the workflow you already run.

CutCtx meets applications and coding agents through SDKs, compatible proxy contracts, local CLI wrapping, agent plugins, MCP, gateways, and IDE integrations. The exact path depends on the host and deployment you control.

Keep your chosen provider · Start locally · Add infrastructure deliberately

Choose the access surface

One platform, several ways in.

Each integration routes through the same context, policy, retrieval, and telemetry foundation while respecting the host protocol and configuration.

SDKs

Application clients

Use Python, TypeScript, or Go clients to connect application traffic to CutCtx proxy and runtime endpoints.

Compatible paths

Provider-aware proxying

Use verified OpenAI, Anthropic, and Gemini-compatible paths, with adapters that preserve the request contract.

CLI and agents

Wrap the workflow

Use the CLI with supported coding-agent wrappers, including Codex, Claude Code, and OpenCode integration surfaces.

MCP and gateways

Connect tools and retrieval

Use MCP, gateway, and agent plugin surfaces where the host supports them.

IDE operations

Manage the local proxy

Use VS Code-compatible and JetBrains integrations for proxy lifecycle, status, and supported AI-extension configuration.

Customer deployment

Keep the boundary yours

Run locally or in customer-managed infrastructure while choosing the provider and endpoint that serve the workload.

A practical evaluation

Start with one workflow, not a migration.

Install CutCtx locally, wrap an existing agent or application path, and review evidence from normal work before you coordinate more teams or controls.

01
Install

Add the package to the environment you control.

02
Wrap or connect

Choose the CLI, SDK, compatible proxy, plugin, MCP, or IDE path that fits your workflow.

03
Inspect

Review savings, routing, and operational telemetry on your own traffic.

Next step

Evaluate the path your team already uses.

Begin with the quick start, then use the full documentation for the integration and deployment detail relevant to your environment.