Supported clients

Soil works with any MCP client · here's the list we recognize (for telemetry and support today) and, in tiers, exactly what we have run ourselves. Honest, not a certification.

The short version: Soil works with any MCP client. The connector speaks standard MCP + OAuth 2.1, and every soil command answers with the same universal monospace card that any client able to show a code block can render. A client Soil has never seen still works fully · connect, save, load, all of it.

So this page isn't a gate. It's two honest lists: the clients Soil recognizes (for telemetry and support today · the hook for any future per-client tuning), and, in tiers, exactly what we have run ourselves and what kind of evidence we kept. Neither list is exhaustive · "not on a list" never means "won't work."

Works with any MCP client

The connector is a standards client, not a per-app integration. If your tool supports remote MCP servers with OAuth, it connects the same way: add the MCP URL, sign in, run soil info. The response renders as the universal monospace card · masthead, rail, readiness gauge, next step · in any tool that shows a fenced code block. See clients & rendering for how connection and the card work, and the copy-paste backstop for tools with no MCP support at all.

Unrecognized clients work fully

An unknown client isn't degraded · it gets the same universal card and the same four commands. Recognition only tunes rendering; it is never a requirement to connect or to use Soil.

Recognized for tailored rendering

Soil detects which client is calling · from the request's User-Agent and the client info it reports · so rendering can be tuned per client. These are the clients it recognizes:

Claude · claude.ai and Claude Desktop
ChatGPT
Codex
Cursor
Grok
Zed
Gemini

Everything else is treated as a generic client and gets the universal card.

What 'recognized' means today (honest)

The universal monospace card is what every client renders right now · the same surface everywhere · so detection currently feeds telemetry and support, not a different-looking response. Recognition is the hook that lets rendering be tailored per client; it doesn't mean a recognized client sees something a generic one can't today.

What we have actually run, by tier

This used to be one list headed "verified in our testing," which claimed every client on it had been connected and round-tripped end to end. That was not true of all of them, so the list is now split by what kind of evidence exists. Only a recorded run earns the top tier; anything weaker says what it is.

Tier 1 · a recorded run

A real Soil operation in that client, recorded and kept. The five films on the home page are these runs, and two of them are complete transfers end to end: a save in Claude Code loaded cold in Codex, and a save in ChatGPT loaded cold in Grok.

Client	What was recorded
Claude Code	a save
Codex	a cold load
ChatGPT	a save
Grok	a cold load
Claude · claude.ai and Claude Desktop	a list

Tier 2 · run by hand, written down, not recorded

We connected and ran these ourselves, and the findings are written into the product's own code and decision records. There is no recording to point at.

Lovable · a soil list run on 2026-06-18, which is why the monospace card is enabled for clients Soil cannot identify; and a soil load on the same day that exposed how strictly this client validates tool schemas, which is why every Soil tool schema is now strict-valid.
Base44 · connected over OAuth repeatedly in June 2026, and its failures are why Soil no longer constrains the shape of opaque OAuth values and why a loosely-shaped save is normalized rather than refused.
v0 · a live soil list followed by soil load on 2026-06-18 that loaded the wrong handover, which is why load codes now come from one counter per account.

Tier 3 · expected to work, not run by us

These speak remote MCP with OAuth, so they should connect exactly like the rest. We have not run Soil in them ourselves, and we are not going to imply otherwise: Cursor, VS Code, Zed, Bolt, Mistral, Gemini CLI.

Tiers, not a certification

"Works with any MCP client" is the design claim, and it holds: the connector speaks standard MCP + OAuth and the card renders anywhere a code block does. What the tiers describe is only our own evidence, not a client's ability. A tier-3 client is not a worse client · it is one we have not personally run, and saying so is cheaper than a claim we cannot back. If yours isn't here, try it · and if anything's off, the copy-paste backstop always works.

The web app-builders · Lovable, v0, Base44, and Bolt · connect through their own backend rather than calling Soil directly, so to Soil they appear as a generic client. Mistral lands the same way. That is why they aren't on the recognized list above · and it costs them nothing: the universal card renders and the commands run.

Per-client connect steps

For copy-paste setup in a specific client, see the client guides · ChatGPT, Claude, Claude Code, Codex, Cursor, VS Code, Grok, Zed, and Gemini CLI each have a short, exact walkthrough.