# Native Soil [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://nativesoil.dev  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/native-soil

## Description
Save an AI chat's working state, load it in any other model or provider. Verified, secret-safe.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "native-soil": {
    "command": "npx",
    "args": ["-y","native-soil"]
  }
}
```

## Documentation

## What the Native Soil MCP server does

The Native Soil MCP server is described as a way to preserve an AI chat's working state and load that state into another model or provider. Its primary use case is moving ongoing work between AI systems without starting from an empty conversation.

The available description does not define what parts of a chat make up the working state. It also does not list separate MCP tools, commands, supported providers, or supported client applications. Treat the stated capability as chat-state portability rather than assuming broader conversation-management features.

## How it works

Native Soil appears to provide a saved representation of an AI chat's working state that can be loaded elsewhere. The listing says the state is “verified” and “secret-safe,” but provides no technical explanation of verification, secret detection, encryption, storage, transport, or identity handling.

Because the repository README is unavailable, the exact workflow cannot be established from the supplied material. The source does not say whether state is saved locally, uploaded to a hosted service, shared through a file, or transferred through an MCP connection. It also does not identify which model or provider combinations are supported.

A developer evaluating the Native Soil MCP server should therefore confirm the state format, provider compatibility, persistence model, and handling of credentials before adopting it for production workflows. The clearest fit is a workflow where an AI conversation must continue in a different model or service.

## Limitations and notes

The available information is limited to the project name, website, and a short description. There is no README content describing installation, configuration, environment variables, API credentials, licensing, pricing, MCP transport, or client compatibility. No executable installation command can be identified with confidence.

The term “secret-safe” is part of the supplied product description, but its implementation and scope are unspecified. Do not infer that the service removes, encrypts, masks, or never stores secrets without documentation confirming those behaviors.

Likewise, “any other model or provider” is the stated portability goal, not a verified list of integrations. Before relying on a particular provider, check Native Soil's current documentation for explicit support and for any restrictions on the type or size of chat state that can be saved and loaded.

_Full upstream README: https://allmcps.com/mcp/native-soil/readme_