Integration guide / Internal preview
Your tools.
Our sandboxes.
Keep using Codex, Claude Code, or Cursor with your existing account. Add Condensation as an infrastructure tool through MCP, the shared protocol for connecting coding assistants to tools.
One connector. Three familiar tools.
Install the local read-only bridge once, then add it to your coding tool. Python 3.9 or newer is required. These shell examples target macOS and Linux. You need an existing Condensation internal operator key; public sign-up and scoped customer keys are not available yet.
Available now: fleet health, resource lists, and resource inspection. The bridge cannot run shell commands, edit sandbox files, create sandboxes, or buy credits. Remote execution and the generic sandbox lifecycle API are the next integration step.
mkdir -p "$HOME/.local/share/condensation"
curl -fsSL https://workspaces.condensation.ai/downloads/condensation-mcp.py \
-o "$HOME/.local/share/condensation/condensation-mcp.py"
# Review the downloaded script, then configure your internal operator key:
python3 "$HOME/.local/share/condensation/condensation-mcp.py" --configureExisting operators can skip configuration when their private ~/.config/condensation/operator.json already contains a valid key. Otherwise, your Condensation key is saved in ~/.config/condensation/mcp.json with private file permissions. The bridge does not read or transfer your coding-tool credentials. The current operator key can access the whole fleet, so use this connector only in a trusted internal workspace.
01 / Codex
Keep your ChatGPT sign-in.
Use Codex with its normal ChatGPT sign-in for eligible subscription usage. API-key sign-in uses separate OpenAI API billing. Add the local bridge from a terminal:
codex mcp add condensation -- python3 "$HOME/.local/share/condensation/condensation-mcp.py"Start a new Codex session and use /mcp to check the connection. Ask: “Use Condensation to check fleet health and list existing app resources.” Your Codex permissions still apply.
02 / Claude Code
Use your normal Claude login.
Claude Code supports eligible Claude subscription accounts through its own login flow. Confirm the active method with /status; an approved Anthropic API key can take precedence and incur API usage.
claude mcp add --transport stdio --scope user condensation -- python3 "$HOME/.local/share/condensation/condensation-mcp.py"Start Claude Code, open /mcp, and check that Condensation is connected. Ask it to inspect an existing resource using the key returned by a resource list.
03 / Cursor
Add Condensation to your editor.
Keep your normal Cursor account and model settings. Add this entry to the mcpServers object in ~/.cursor/mcp.json, preserving any servers you already use:
{
"mcpServers": {
"condensation": {
"type": "stdio",
"command": "python3",
"args": [
"${userHome}/.local/share/condensation/condensation-mcp.py"
]
}
}
}Reload MCP servers in Cursor, confirm the tools are available, and ask Agent to check Condensation fleet health. This adds infrastructure tools; it does not move your Cursor subscription or export its model access to another service. Team policies may require an administrator to allow the connector.
Two bills, with clear jobs.
| Account | Covers |
|---|---|
| Your coding-tool account | Eligible model usage in that provider’s product, subject to its plan and limits. |
| Condensation | Allocated sandbox CPU, memory, retained storage, and billable network usage. |
The proposed Build subscription is $20/month and includes $25 in sandbox credits. Monthly credits reset at renewal and are spent before purchased credits. Top-ups are one-time purchases and carry forward. One credit dollar pays for one USD of resource usage at the published rates.
Credits cannot extend Codex, Claude, or Cursor model quotas. Direct model API calls inside a sandbox require the provider’s supported authentication and are billed separately. The connector does not sell or pool model subscriptions.
Preview plans and credit top-ups →If the connection needs attention.
- Python not found: use the full path to your Python 3 executable in the MCP configuration.
- Key missing or HTTP 401: rerun the connector with
--configureand a valid Condensation operator key. - HTTP 503: the operator service is unavailable or not configured; the connector cannot repair fleet configuration.
- No tools appear: restart the coding tool, check its MCP panel, and confirm your workspace policy allows the connector.
- Unexpected model charges: check your coding tool’s active authentication and billing settings. Condensation cannot change those entitlements.
- Need sandbox execution: this release exposes read-only inspection. The connector is not a remote development environment or a replacement for a provider’s cloud agents.
Provider documentation checked September 7, 2026. The connector is tested at the MCP protocol and HTTP-adapter level; a signed-in live session in each provider has not been verified.