General Tools

whatscooking.guide

An MCP server for recipe discovery, browsing shared recipes, and suggesting meals based on available ingredients.

1 endpoint3 known toolsFirst detected October 25, 2026Last detected October 25, 2026

ENDPOINT 1

https://whatscooking.guide/mcp-server

No auth detected

MCP server metadata

Name: whats-cooking
Version: 1.0.0

Capabilities

tools

Server instructions

Ask Gusto what to cook tonight from what someone has on hand (whats_for_dinner), or browse recipes people and Gusto have shared (browse_explore, get_explore_recipe). The full recipe comes back in the response — no need to send people anywhere.

Known tools 3

whats_for_dinner

What should I cook tonight with what I have?

Inferred read-only

browse_explore

What recipes have people and Gusto shared on What's Cooking?

Inferred read-only

get_explore_recipe

What's the full recipe for this Explore pick?

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.whats-cooking]
url = "https://whatscooking.guide/mcp-server"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "whats-cooking": {
      "type": "http",
      "url": "https://whatscooking.guide/mcp-server"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: whats-cooking
Remote MCP URL: https://whatscooking.guide/mcp-server

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "whats-cooking": {
      "url": "https://whatscooking.guide/mcp-server"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "whats-cooking": {
      "type": "http",
      "url": "https://whatscooking.guide/mcp-server"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "whats-cooking",
  "transport": "streamable-http",
  "url": "https://whatscooking.guide/mcp-server"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.