mcpField
L
Limonene

Limonene

Remote
limonene.appBusiness & Marketing0Updated 5w ago

About Limonene

Limonene is a remote MCP server for Amazon sellers using ChatGPT, Claude, or compatible clients. It offers read-only store analysis by default, with separately consented management tools for approved changes.

Key features

  1. 01Read sales, alerts, and trends
  2. 02Check Buy Box and FBA inventory
  3. 03Review revenue, fees, and cost coverage
  4. 04Optional approved listing and pricing actions

Use cases

  1. 01Investigate recent sales and alerts
  2. 02Review SKU pricing and Buy Box status
  3. 03Assess FBA inventory health
  4. 04Preview and approve listing or pricing changes

MCP support

Exposes Amazon store analytics through a hosted MCP endpoint. A basic connection provides six read-only tools; separately authorized management access enables additional tools and requires approval before changes.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://limonene.app/api/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Limonene AI connector

Amazon seller investigations through ChatGPT, Claude and compatible MCP clients. Basic connections expose six read-only tools. Separately consented management access supports additional analysis and approved actions; the initial read-only Claude directory listing is public and expanded management metadata is in review.

Endpoint: https://limonene.app/api/mcp Setup and permissions: https://limonene.app/connect-ai Revoke connections: https://limonene.app/api/mcp/connections Privacy: https://limonene.app/privacy

Claude listing: https://claude.ai/directory/limonene. Its approved description currently covers six read-only tools; the expanded listing update is in review. The separate Claude Code/Cowork plugin and OpenAI submissions remain in review.

Connection

  1. Sign in to Limonene and connect an Amazon store. Complete its initial sync.
  2. Add the endpoint as a custom remote connector in your AI client (account/workspace support varies).
  3. Authenticate in the browser. Read the client name and callback origin, select a store and choose Read only or Read and manage. Management requires a separate acknowledgment and approval before each change.
  4. Ask: “Review my last seven days. What deserves investigation? Cite sources, dates, and limitations.”

Claude Code: claude mcp add --transport http limonene https://limonene.app/api/mcp, then use /mcp to authenticate. The package includes separate OpenAI and Claude manifests referring to the same remote server; there is no local executable and no credential embedded in the package.

Basic tools

  • get_store_overview: bounded marketplace-local sales window.
  • get_open_insights: dated existing alerts, capped at 25.
  • get_pricing_and_buybox: cached observations for up to 20 SKUs; no price edits.
  • get_inventory_health: FBA-only inventory, optional SKU.
  • get_sales_trend: SKU history for 1–60 days.
  • get_profit_breakdown: revenue/fees and available cost-coverage information; do not label fees-only figures net profit.

The six-tool basic connection excludes changes and buyer contacts. Choosing Read and manage in a compatible client enables up to 57 tools, depending on store feature availability, including approved prices, listings, repricing rules and schedules. Advertising changes and paid reimbursement filing are excluded. DeepSeek’s current package is a read-only pilot. Each grant is bound to one store and its active marketplace; reads fail closed while a different marketplace is active. To read that marketplace, reconnect. Results use the existing capability caches and may trigger their normal background refresh. The external AI generates the answer; this connector does not run a second Limonene model call or debit chat credits. First-party telemetry records connection, revocation, tool name, success and duration; it does not log prompts, arguments, tokens or tool results. Existing billing remains advisory under the current app policy. This release does not introduce a paid gate or promise unlimited access. Limits: 60 MCP requests/minute/store plus the existing IP ceiling.

Privacy and security

OAuth authorization code flow with mandatory S256 PKCE and resource binding. Public clients register with token_endpoint_auth_method: none. Access tokens expire after one hour; refresh tokens rotate and expire after 30 days. Tokens/codes/browser nonces are stored hashed. Consent requests expire after ten minutes and codes after one minute. Ownership, connection health, revocation and marketplace are rechecked on access. Product and alert text are untrusted data.

The AI service receives the requested store results under the seller's authorization. Its own data policies apply. Revocation blocks subsequent reads, not copies already retained by that service. Account deletion removes grants and their token/code records.

GitHub Copilot in VS Code

Copy vscode.mcp.json to your workspace as .vscode/mcp.json, then start the server from VS Code and complete the browser authorization. Your editor must support remote HTTP MCP and OAuth. This configuration is for GitHub Copilot in VS Code; it is not a Microsoft 365 Copilot marketplace listing.

Installation package

This repository contains public connector configuration and documentation only. The hosted Limonene service is separate. No API key is required in these files; each user signs in and grants access to their own store.

A Limonene account and a connected, synchronized Amazon store are required. Availability and pricing: https://limonene.app/pricing. Do not connect a customer store for platform review; use a dedicated review account.

Pilot status

The remote endpoint is live. Six read tools have passed MCP Inspector against the isolated live reviewer account; the original ChatGPT read workflows were also tested. OpenAI and the Claude Code/Cowork plugin are under review. The six-tool Claude connector is published. All 57 tools passed live MCP Inspector sample checks, and Claude completed a fictional inventory → price preview → explicit approval → simulated completion workflow. Four MCP prompts were listed and retrieved. This is not evidence that every real Amazon workflow has been exercised. Installing this package does not imply endorsement by any platform.

Support: [email protected] Setup: https://limonene.app/connect-ai Terms: https://limonene.app/terms Privacy: https://limonene.app/privacy

The MIT license applies only to files in this public connector package, not to the hosted service or its backend.

DeepSeek Harness

A pinned OAuth bridge and DSH bundle are available. See DeepSeek setup and validation boundaries. This is a community developer integration, not a consumer DeepSeek chat-app listing.

Management workflows

With explicit Read and manage consent, up to 57 tools cover product and order analysis, inventory/inbound, listings, pricing and repricing, costs, reimbursement evidence, available ads analysis, schedules, structured queries and seller notifications. See management permissions and operations.

Four MCP prompts guide multi-step work: weekly_store_review, pricing_change_plan, inventory_action_plan and listing_improvement_plan. Every action uses a frozen preview, explicit approval and a tracked operation. Scheduled analyses use Limonene AI credits; approved schedules and repricing rules may continue after disconnecting.

The Claude plugin manifest is version 0.2.0 for direct installation. It does not mean the separate plugin marketplace review has approved that version. DeepSeek Harness remains a read-only pilot.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.