Connectivity

Soil reaches your AI clients through three tiers · Remote MCP, Soil Desktop's local MCP, and copy-paste · so "load anywhere" is true without overclaiming.

"Load anywhere" is only honest if there's always a working path. So Soil reaches AI clients through three connectivity tiers. You don't usually pick one manually · you use the best one your client supports · but it helps to know how they fit.

The three tiers

1. Remote MCP + OAuth · the primary path

Paste the Soil MCP URL, log in, done. Covers most major clients today and needs no install. This is the default and the focus.

Available now (beta). See Soil Cloud.
Requires the client to support remote MCP + OAuth. Soil auto-registers via Dynamic Client Registration (DCR), so supporting clients connect with no manual client id · see clients & rendering. Once connected, the connection renews silently with refresh tokens.

2. Soil Desktop's local MCP · optional fallback

For MCP-capable clients that lack remote + OAuth, plus a privacy/offline option. Soil Desktop holds your Soil login and runs a local stdio MCP server on your machine. It's a narrow, optional fallback · never the primary path.

Not yet released. Part of Soil Desktop.

3. Copy-paste from the dashboard · the universal backstop

Works in any tool, including non-MCP ones (e.g. Xcode). Open the console dashboard, copy your handover's restore prompt, paste it. Always present behind the scenes so the product never hits a dead end.

Available now (beta).

When to use which

Situation	Use
Your client supports remote MCP + OAuth	Remote MCP (tier 1)
MCP-capable client without remote/OAuth, or you want local/offline	Desktop's local MCP (tier 2, not yet released)
Any tool, including non-MCP ones, or a client that won't connect cleanly	Copy-paste (tier 3)

Why three tiers

Frictionlessness means there's always a working path. Honesty means we never promise MCP magic in a client where it's clunky or unsupported. The copy-paste backstop guarantees no broken first impressions.