Soil Cloud (Remote MCP)

Available now (beta). Paste one URL into your AI client, sign in, and the soil tools appear. No install.

Available now · beta

Soil Cloud is the Remote MCP connector. It's live in beta. Connect it to any AI client that supports remote MCP servers with OAuth, and the soil commands become available in your conversations.

Soil Cloud is the primary way to use Soil. It's a hosted Remote MCP connector: you paste a URL into your AI client, sign in, and your client gains the soil commands, with no install and no local process.

MCP URL: https://mcp.nativesoil.dev/mcp/soil
Dashboard: https://console.nativesoil.dev

Connect your client

Add the MCP server

In your AI client's MCP / connectors settings, add a remote MCP server and paste the Soil MCP URL:

https://mcp.nativesoil.dev/mcp/soil

For exact, per-client steps (ChatGPT, Claude, Claude Code, Codex, Cursor, Grok, Zed, Gemini CLI), see the client guides.

You don't supply a client id or secret. Soil's OAuth bridge implements Dynamic Client Registration (DCR / RFC 7591), so a supporting client registers itself automatically the first time it connects.

The client opens Soil's OAuth flow. Sign in with Google, or with email and password (new accounts get a verification email, and there's a password reset if you forget it). The connection then renews itself silently with refresh tokens, so you sign in once per client, not once per session. Soil runs its own OAuth bridge, so auth stays first-party, and you can revoke any client from the console's Connect page at any time.

Use the soil commands

Once connected, the soil commands work in the conversation. Start by asking the model to run soil info to confirm the connection and see your account status.

Verify the connection

Once connected, ask the model to run soil info. It returns your project and handover counts and confirms your client reached Soil and is authenticated. That round-trip is the proof the connection works.

Client support varies

Different clients support remote MCP + OAuth to different degrees. Soil auto-registers via Dynamic Client Registration (DCR), so clients that support it complete the "paste URL → log in" flow with no manual client id · see client support. When a client can't connect cleanly, the copy-paste backstop always works.

What you can do

The full user-facing command set is four commands:

soil save · capture this conversation as a checked, graded handover. One command: the model and Soil handle the extraction, verification, and drift check internally. A bare soil save is a personal, standalone snapshot; name it (soil save #my-thread) and every named save is kept, never overwritten. soil save @project adds this thread to a shared project you belong to · where your work accumulates over time · and soil save #name @project names it in the same breath. @ says where, # says which, in either order.
soil list · see everything you can load · your saved handovers, newest-first, plus the projects you belong to. soil list @project lists a project's threads.
soil load #001 (exact code), soil load #my-thread (by name), soil load @project #001 or soil load @project #auth-flow (one thread inside a project, by code or by name), or soil load @project (the project in one restore: its knowledge, every thread listed, the newest inline).
soil info · project + handover counts, your most recent handovers, and connection status.

See the tools reference for details, and the guides for a worked save-then-load walkthrough.

Where your data lives

Soil Cloud stores safe projections only · meaning, never secrets or raw prompts (see safe projections). The connector, auth, and storage all run in a single Google Cloud project · no third-party hosting vendor in the path.