Most agents use the first two together: the docs MCP server to look up how something works, and the CLI to do it.
Docs MCP server
Fluid’s docs come with a hosted, read-only Model Context Protocol (MCP) server at:- Search the docs, guides, and API reference.
- Read any docs page or OpenAPI spec in full.
- Send feedback about a docs page that’s wrong or missing something.
Connect from a docs page
Every docs page has a menu at the top. Use it to copy the MCP server URL or install the server in Cursor or VS Code in one click.Connect by hand
- Claude Code
- Cursor
- VS Code
- Claude Desktop
Run this in any terminal. Claude Code keeps the server in your configuration.
Without MCP
Agents that can’t use MCP can still read the docs:/llms.txtindexes every page for language models./skill.mdis a short guide for AI tools: where to look, Fluid’s naming, and the main conventions.- Every page can be copied as Markdown from its page menu.
Fluid CLI
To make changes, give the agent the Fluid CLI. It works on your company’s themes, and its plugins run Fluid’s guided setups, such as connecting a back office, opening a country, or setting up payments onboarding. Every guided-setup command prints JSON, so an agent can read the result of each step. Sign the CLI in one of two ways:-
Your own sign-in. Run
fluid loginand enter the code Fluid emails you. Use this when you’re at the keyboard with the agent. -
An API token. Create one at Settings → API Tokens, then sign in with it. Pass it in an environment variable so it stays out of your shell history:
Use this when the agent runs on its own. See Authentication for token types.
fluid theme skills install to give your agent Fluid’s theme skills as well. To set up a whole store with an agent, follow the agent launch guide.
The docs MCP server and the CLI are separate. The MCP server never sees your token.