> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/mcp/install/claude.md).
# Install FLORA MCP in Claude (web and Desktop)
Add FLORA MCP to Claude on the web and in Claude Desktop as a custom connector, on Free, Pro, Max, Team or Enterprise plans.
You add [FLORA MCP](https://flora.ai/mcp) to Claude as a custom connector, using FLORA's server URL. Anthropic's connector directory doesn't accept AI image, video or audio generation services, so FLORA isn't listed there, and a custom connector is the way to add it.
| | |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Fastest** | Open [**Customize → Connectors**](https://claude.ai/customize/connectors), click **Add custom connector**, and paste `https://agents.flora.ai/mcp` |
| **Needs** | Any Claude plan (Free allows one custom connector). On Team and Enterprise, an Owner adds it first. Plus a FLORA plan: Starter or above for ongoing use, or Free on the $2.50 of usage every new workspace gets ([pricing](/plans-and-billing/pricing.md), [details](/mcp/authentication.md#who-can-connect)). |
| **Sign in** | Click **Connect**, then sign in on FLORA's sign-in page |
| **Verify** | "List my FLORA workspaces. Don't generate anything." |
| **Remove** | **Customize → Connectors**, then **Remove** next to FLORA |
Claude Desktop uses the same connectors as claude.ai. Add FLORA once on your account and it shows up in both. Don't add FLORA to `claude_desktop_config.json`; that file is for local servers.
## Free, Pro and Max
1. Open [**Customize → Connectors**](https://claude.ai/customize/connectors) in Claude.
2. Click **Add custom connector** (on some accounts, **+ Add** first).
3. Name it `FLORA` and enter the server URL `https://agents.flora.ai/mcp`.
4. Leave the OAuth client ID and secret empty. If the dialog asks how to sign in, choose **Sign in now**. If it asks for an **OAuth client**, choose **Register automatically**: FLORA registers Claude for you.
5. Click **Add**, then **Connect** on the new FLORA connector.
6. Sign in on FLORA's sign-in page with the account you use at [app.flora.ai](https://app.flora.ai). You return to Claude when it's done.
On the Free plan you can add one custom connector.
## Team and Enterprise
An Owner adds FLORA once for the organization. On Enterprise, members with a custom role that can manage the organization's libraries can add it too. Members can't add a custom connector themselves.
**Owner:**
1. Open [**Organization settings → Connectors**](https://claude.ai/admin-settings/connectors).
2. Click **Add**, then **Custom**. If asked for the type, choose **Web**.
3. Enter `https://agents.flora.ai/mcp`. Leave the OAuth client ID and secret empty.
4. Click **Add**.
**Each member:**
1. Open **Customize → Connectors**.
2. Find **FLORA** with the **Custom** label.
3. Click **Connect** and sign in with your own FLORA account.
Every member signs in as themselves. Generations bill the FLORA workspace each person picks, not the Owner's.
## Turn FLORA on in a chat
In a conversation, click **+**, open **Connectors**, and turn **FLORA** on. Turn it off in chats where you don't need it.
## Check it works
Start a new chat with FLORA on and ask:
> List my FLORA workspaces. Don't generate anything.
Open in Claude
Claude calls `flora_list_workspaces` and lists your workspaces. Then try the [quickstart](/mcp/quickstart.md).
## Files you share in Claude
Images and files you attach in a Claude chat are already hosted, so Claude can pass their URLs straight to FLORA. For a file that isn't in the chat, Claude can give you a FLORA upload link that works for 15 minutes. See [Upload your own images, video and files](/mcp/recipes/upload-files.md).
## Gotchas
| Symptom | Cause | Fix |
| ---------------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| No **Add custom connector** option | On Team or Enterprise, only Owners can add custom connectors | Ask an Owner to add FLORA under **Organization settings → Connectors**. |
| The Free plan won't add FLORA | Free allows one custom connector | Remove the other custom connector, or upgrade your Claude plan. |
| Sign-in fails right after **Connect** | The URL has a typo, often a trailing slash (`/mcp/` returns 404) | Remove the connector and add it again with exactly `https://agents.flora.ai/mcp`. |
| Claude doesn't use FLORA | FLORA is off in this chat | Click **+ → Connectors** and turn FLORA on. |
| Claude asks before each FLORA action | Claude asks for approval on tool calls by default | Approve each call, or choose **Always allow** for FLORA's read-only tools. |
| Claude calls a retired tool such as `flora_generate` | Old instructions or a cached tool list | Start a new chat. See [Retired tools](/mcp/retired-tools.md). |
Claude reaches FLORA from Anthropic's servers, not from your computer, so a VPN or firewall on your machine doesn't affect the connection.
## Remove
Open **Customize → Connectors**, find FLORA, and click **Remove** (or use the **⋯** menu). Team and Enterprise Owners remove it for everyone under **Organization settings → Connectors**.
See [Authentication](/mcp/authentication.md#disconnect-and-revoke) for revoking API keys and what FLORA stores.
## Next
* [Quickstart](/mcp/quickstart.md): your first image, with a cost quote first.
* [Skills and plugins](/mcp/skills.md): add FLORA's tested workflows to Claude.
* [Troubleshooting](/mcp/troubleshooting.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flora.ai/mcp/install/claude.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.