Agent Chef

net.agentchefPublished by agentchef.netOfficial publisherv0.3.0Updated Oct 27, 2026

Family meal planning run by your agent: weekly dinners, household votes, grocery list minus pantry.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP endpoint for family meal planning: an assistant can plan weekly dinners, run household votes and build grocery lists minus pantry items.

What you can do
  • Plan weekly family dinners and household meal schedules
  • Run household votes on meal choices
  • Build grocery lists that subtract what is already in the pantry
  • No individual tools are listed, so exact operations are not documented; capabilities come from the short registry description.
When to use it
Worth adding when a household wants an assistant to help decide weekly dinners, collect family preferences by vote, and turn the plan into a shopping list that accounts for pantry stock.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's site; no local package or runtime. Authentication is OAuth-based and requires an Authorization header carrying a bearer API key, which the user creates in the provider's agent settings (free trial, no card).
Before you install
The server requires a bearer API key in the Authorization header; treat it as a secret. It handles household meal plans, votes and pantry contents, which are personal data sent to a third-party service. No tool list is published, so what it can read or change is not documented.

Installation

In SourceWeft

  1. Open Agent Chef in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.agentchef%2Fagent-chef/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "agent-chef": {
      "type": "http",
      "url": "https://agentchef.net/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.