Home · Setup · Cline

MCP Ingredient Converter in Cline

Convert cups, tablespoons and grams per ingredient, with a real density table and friendly fractions. convert_ingredient turns an amount of a named ingredient between cups, tablespoons, teaspoons, milliliters, fluid ounces, grams and ounces using a per-ingredient density table; scale_recipe doubles or halves a list of recipe lines into friendly fractions; convert_bulk converts many amounts at once and reports unknown ingredients per item; decimal_to_fraction and fraction_to_decimal handle the 1 1/2 cup style; common_conversions lists the most-googled conversions; list_ingredients dumps the table with sources.

Pure function, no state: auto-approve without hesitation, the worst outcome is a gram count you would sanity-check against the bag anyway.

What you get in Cline

You say	Tool
How many grams is 1 cup of all-purpose flour?	`convert_ingredient`
Double this recipe: 1 1/2 cups flour, 1/2 cup sugar, 100 g butter.	`scale_recipe`
Convert 250 g butter and 120 ml honey to cups.	`convert_bulk`

The contract suite walks a real stdio case through the density table: 1 cup of all-purpose flour comes back as 125 grams with cups, tablespoons and ounces alongside, unknown ingredients are refused with a reason, and nothing hangs.

Install it in Cline

The file is mcp.json, and the key inside it is mcpServers.

Scope	Path
Cline CLI	`~/.cline/mcp.json`
The editor extension	`opened from the Cline panel, not by path; the documentation deliberately calls it the MCP settings JSON used by the extension`

If you also run Claude Desktop, the shortest path there is one click: ingredient-convert.mcpb from the bundle catalog opens as an extension, with no JSON and no terminal. Cline reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "ingredient-convert": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/ingredient-convert/dist/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

The node command above wants a built file. From a clone, once:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/ingredient-convert

That writes servers/ingredient-convert/dist/index.js, and its absolute path is the one argument the config needs.

The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:

{
  "mcpServers": {
    "ingredient-convert": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-ingredient-convert"]
    }
  }
}

No full-app restart. The MCP settings actions include restarting an unresponsive server if its tools do not appear.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/ingredient-convert over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.

Write the transport in. Omitting type falls back to the legacy sse transport, which will not talk to this endpoint:

{
  "mcpServers": {
    "ingredient-convert": {
      "type": "streamableHttp",
      "url": "https://mcp.zovo.one/mcp/ingredient-convert",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cline notes worth knowing first

Cline is the one client here with an unsafe transport default. `type` selects it, and omitting `type` falls back to the legacy sse transport, so a streamable HTTP endpoint needs it written in or you will debug a server that is fine. Local entries carry "disabled" and an "autoApprove" array.

Free: Everything: seven tools, the full density table, no metering, no key. Pro is $19 once, verified offline.

Questions

Where does the config live?

The CLI reads ~/.cline/mcp.json. For the extension, do not hunt for a path: MCP Servers icon, Configure tab, Configure MCP Servers. cline mcp opens a wizard, and cline config mcp --json is the non-interactive form.

The hosted endpoint will not connect.

Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in.

Should I auto-approve MCP Ingredient Converter's tools?

Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.

MCP Ingredient Converter in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs · Buy Pro