FoodPhoto

ai.foodphotoPublished by foodphoto.aiOfficial publisherv1.0.1Updated Oct 24, 2026

Create food photos, menus and restaurant campaigns. Account-based paid service with Stripe checkout.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Lets an assistant generate food photos, menus, and restaurant marketing campaigns through a hosted paid service.

What you can do
FoodPhoto is a remote MCP endpoint that lets an assistant create food photography, menu content, and restaurant campaign material. It is an account-based service, so work is tied to a user account rather than run locally. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to produce food imagery, menu layouts, or promotional campaign assets for a restaurant or food business. It is not useful for general image editing or non-food creative work.
Requirements
A remote MCP client connecting to the hosted endpoint over streamable HTTP. An account with the provider is needed, and the service is paid through Stripe checkout. No packages, environment variables, or headers are declared.
Before you install
This is a paid service: using it involves Stripe checkout and spending money. It is account-based, so account credentials and billing details are handled by the provider. The manifest declares no authentication, so confirm how access is actually secured before connecting.

Installation

In SourceWeft

  1. Open FoodPhoto 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/ai.foodphoto%2Fstudio/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": {
    "foodphoto": {
      "type": "http",
      "url": "https://foodphoto.ai/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. v1.0.1LatestSep 16, 2026

Score

67% 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
  • 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.