Recipe Commerce MCP

Recipe Commerce MCP runs locally from a Node.js package published to the npm registry: recipe-commerce-mcp version 0.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y recipe-commerce-mcp@0.1.3. It reads these environment variables: OPENAI_API_KEY (required, secret) and MCP_API_KEYS (secret); set them in the client's configuration for this server.

Recipe Commerce MCP runs locally from a Node.js package published to the npm registry: recipe-commerce-mcp version 0.1.3. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "recipe-commerce-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "recipe-commerce-mcp@0.1.3"
      ],
      "env": {
        "OPENAI_API_KEY": "<secret>",
        "MCP_API_KEYS": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect