Connecting to Generic MCP Clients

This page is the plain MCP fallback guide for clients that can connect to MCP servers but do not have a dedicated Fluent setup guide or rich Fluent widget layer.

If you are using ChatGPT, Claude, Codex, or OpenClaw, start with their dedicated guides first. Use this page when your host supports HTTP MCP tools and resources but should be treated as text-first.

Current Status

Generic MCP clients can use the same Fluent contract as the documented clients:

shared profile and domain tools
Meals, Style, and Health tools
fluent_get_capabilities for contract version, domain readiness, and tool discovery
the open-source runtime for self-hosted use today
managed early access when your account has been provisioned

Do not assume generic MCP clients can render Fluent rich widgets. ChatGPT and MCP Apps-style rich views are optional UI companions, not the portable baseline.

Manual Configuration

For the open-source runtime, most HTTP MCP clients use a shape like:

json

{
  "mcpServers": {
    "fluent": {
      "type": "http",
      "url": "http://127.0.0.1:8788/mcp",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}

Replace <your-token> with your bearer token.

For early-access testing, the managed endpoint is:

json

{
  "mcpServers": {
    "fluent": {
      "type": "http",
      "url": "https://mcp.meetfluent.app/mcp"
    }
  }
}

Use this only when you have early access. Billing and account management stay on meetfluent.app rather than inside the MCP client.

First Call

Start every generic MCP session with:

fluent_get_capabilities

That response tells the client:

the current contract version
which domains are available, enabled, and ready
onboarding state
profile summary
tool discovery groups

After that, use the relevant Meals, Style, or Health tool for the request.

Plain MCP Fallbacks

Use canonical tools directly:

User asks for	Preferred tool path
A recipe	`meals_get_recipe`
A grocery list	`meals_get_grocery_plan`
A week plan	`meals_get_plan`
A purchase decision	`style_prepare_purchase_analysis`, then the purchase-analysis result the host can support
Today's workout context	`health_get_today_context`

If the client cannot render widgets, answer from the tool result in structured text. That is expected behavior, not a broken integration.

Rich App Views

The current rich app views are documented in the Tools Reference, but generic MCP clients should not call them by default.

Avoid assuming support for these rich views:

meals_render_recipe_card
meals_render_pantry_dashboard
meals_render_grocery_list_v2

Only use a rich view when the host explicitly supports MCP Apps-style widget resources and bridge behavior. Otherwise, keep the result textual and complete.

style_render_purchase_analysis is the structured text-first purchase-analysis fallback after the user provides item details, an image, or other purchase evidence. It is not a widget view.

Connecting to Generic MCP Clients ​

Current Status ​

Manual Configuration ​

First Call ​

Plain MCP Fallbacks ​

Rich App Views ​