Client configuration

This page covers the technical configuration patterns for connecting Fluent to MCP-compatible AI apps.

These configs tell an AI app how to reach Fluent. You still talk to ChatGPT, Claude, Codex, or another assistant directly; Fluent is the MCP server that supplies the closet and its tools underneath.

For the fastest setup path, start with Connect Fluent.

Hosted endpoint

Fluent is a hosted service with one public MCP endpoint:

https://mcp.meetfluent.app/mcp

It uses OAuth sign-in; there is no bearer token to copy. Approve every scope Fluent requests during sign-in.

Standard mcpServers block

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

Native server block

Some apps, such as OpenClaw, register a native server object instead of the wrapped mcpServers block. Use the native mcp.servers.fluent JSON block:

{
  "url": "https://mcp.meetfluent.app/mcp",
  "transport": "streamable-http"
}

Scaffold generator

The scaffold generator in this repository prints the same hosted configuration for a named client.

npm run scaffold:mcp -- --client <client> --track cloud [--out <path>]

Parameter	Values	Purpose
--client	claude, codex, openclaw	Output shape: codex and claude return a standard mcpServers.fluent block; openclaw returns the native server object
--track	cloud	Fluent's hosted endpoint
--out	path	Write config to file

Checked-in client bundles

Client	Bundle root	Key checked-in files
Codex	plugins/fluent/	.codex-plugin/plugin.json, .mcp.json
Claude	claude-plugin/fluent/	.claude-plugin/plugin.json, .mcp.json

General patterns

First call

Start with fluent_get_capabilities. It returns the contract version, the available closet features, and tool discovery hints.

Closet context

Use fluent_get_closet_context with domain="style" as the normal entry point: intent="closet" before naming clothes the user owns, and intent="purchase" for a "should I buy this?" question.

Tool discovery

The MCP tools/list endpoint is the authoritative public registry. See the tools reference.

Reconnecting

After an update, or if your app shows an older tool set:

1. Reconnect the MCP server in your app
2. Re-authorize if prompted
3. Clear stale credentials if the app caches an older registration