Clients
One short guide per AI client · how to connect Soil and the same four soil commands everywhere.
Soil Cloud connects to your AI client over Remote MCP + OAuth: one URL, one sign-in. These guides cover the clients we have proven end to end · connect, then use the same four commands with the same grammar in every one of them. Save in one client, load in any other; it is the same account everywhere.
- MCP URL (the same in every client):
https://mcp.nativesoil.dev/mcp/soil
ChatGPT
1-click add from ChatGPT's app directory.
Claude
Add the connector in claude.ai and Claude Desktop.
Claude Code
One claude mcp add command in the terminal.
Codex
A config.toml block plus codex mcp login · CLI and IDE.
Cursor
1-click install, or one mcp.json entry.
VS Code
1-click install, or add an HTTP MCP server.
Grok
Add the Soil connector in Grok's connector settings.
Zed
A context_servers entry in settings.json · OAuth is automatic.
Gemini CLI
An httpUrl entry in ~/.gemini/settings.json.
Not on this list?
Any other MCP client that supports remote servers with OAuth connects the same
way: add the MCP URL, sign in, run soil info. See clients &
rendering for how connection and rendering work, and the
copy-paste backstop for tools with no MCP support at all.
Clients & rendering
Which AI clients connect to Soil Cloud over Remote MCP, what Soil's responses look like, and where your connected clients are listed.
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.