# Limonene for DeepSeek Harness — read-only pilot

Connect your Amazon store to DeepSeek Harness through the same Limonene MCP server. This is a community installation package, not a listing inside the consumer DeepSeek chat app or an endorsement by DeepSeek.

## Install

Requires Node.js 22+, a configured DeepSeek Harness installation/model provider, and a Limonene account with a synchronized Amazon store.

```sh
dsh plugin --profile web add github:M-Abozaid/limonene-mcp
dsh web
```

A browser window opens for Limonene OAuth. Verify the client name, select your store, and choose **Read only**. No Amazon credentials, Limonene password or bearer token belongs in the configuration file. Model-provider access and charges are separate from this connection.

Alternative: download `cordis.patch.yml` from this repository and run `dsh --profile web --patch /absolute/path/to/cordis.patch.yml`. Do not install the bundle and overlay together: they register the same server name.

## Try it

“Review my last seven days. Which issues deserve attention? Cite dates and missing data.”

“Compare FBA stock and recent sales for SKU [your SKU]. What else do we need before reordering?”

“Break down revenue and Amazon fees. Tell me which costs are missing before discussing profit.”

## Permissions and compatibility

This pilot targets the six read tools. The tested DSH MCP adapter does not propagate MCP write/destructive annotations into its registered tool definitions, so we have **not** validated management approval behavior in DeepSeek. Do not enable Read and manage for this pilot. Existing tokens retain their original consent; reconnect to change permissions.

Validated with DeepSeek Harness MCP client 0.1.5-rc.2 and mcp-remote 0.14.2: real browser OAuth, six-tool discovery, and one sample-store read through the actual DSH MCP plugin in a minimal test context. Full DSH UI/model conversation testing and downstream directory acceptance are not claimed.

The pinned `mcp-remote` bridge is an external open-source dependency. It runs locally, connects to https://limonene.app/api/mcp, and caches OAuth credentials locally under its standard `~/.mcp-auth` directory. Keep that directory private. It does not require copying access tokens into files. The DSH model provider receives requested tool results under its own policies.

Disconnect at https://limonene.app/dashboard/settings/account#ai-apps and remove the bundle with `dsh plugin --profile web remove limonene-dsh`. Revocation prevents future access; it does not erase results already retained by an AI provider. If a login expires, reconnect instead of adding a static token.

Support: hello@limonene.app. Privacy: https://limonene.app/privacy. Setup: https://limonene.app/connect-ai.