# Connect Claude

> Add the Flowkiwi MCP server to claude.ai, Claude Desktop or Claude Code.

This page connects Claude to the MCP server of a Flowkiwi instance. Read [Connect an AI agent (MCP)](/mcp/) first for the sign-in, access levels and troubleshooting.

Your server URL is:

```text
https://<tenant>.product-management.flowkiwi.net/api/mcp
```

Sign in and pick your instance to fill it into the snippets below (optional, the sign-in only serves the docs):

## claude.ai and Claude Desktop

In Claude, an MCP server is added as a **custom connector**. The same connector then works on claude.ai, Claude Desktop and the Claude mobile apps.

> **Reached from Anthropic's cloud**
>
> Custom connectors connect to the server from Anthropic's infrastructure, even in Claude Desktop. The Flowkiwi MCP server is public, so there is nothing to open on your side. On the Free plan, Claude allows one custom connector.

### Pro, Max and Free plans

<Steps>

1. Go to **Customize > Connectors**.
2. Click **+ Add**, then **Add custom connector**.
3. Enter a name, for example `Flowkiwi - <your instance>`, paste your server URL, then click **Continue**.
4. Keep the default sign-in settings: Claude registers itself with Flowkiwi, so there is no client id or secret to enter.
5. Optional: under **Request headers**, add `Flowkiwi-Api-Version` with the version to pin, for example `2026-07`. See [Choose the API version](/mcp/#choose-the-api-version).
6. Click **Add**, then sign in when Claude asks you to. Your browser opens the Flowkiwi sign-in and consent screen.

</Steps>

### Team and Enterprise plans

An owner or admin adds the connector once for the organization:

<Steps>

1. Go to **Organization settings > Connectors**.
2. Click **Add**, hover **Custom**, then select **Web**.
3. Fill in the name, URL and options as in steps 3 to 6 above.

</Steps>

Each member then goes to **Customize > Connectors**, finds the connector and clicks **Connect**. Every member signs in with their own Flowkiwi account and gets their own permissions.

### Use it in a conversation

In a conversation, click the **+** button at the bottom left, open **Connectors** and turn the Flowkiwi connector on. Then ask, for example: "List the draft products of the Kitchen category".

## Claude Code

### Add the server from the command line

```bash
claude mcp add --transport http flowkiwi https://<tenant>.product-management.flowkiwi.net/api/mcp \
  --header "Flowkiwi-Api-Version: 2026-07"
```

The `--header` line is optional; it pins the [API version](/mcp/#choose-the-api-version). Add `--scope user` to use the server in all your projects, or `--scope project` to share it with your team through the project `.mcp.json`. Without `--scope`, the server is only added for you, in the current project.

### Or share it in `.mcp.json`

To share the server with everyone working on a project, commit it in the project's `.mcp.json`. It holds no secret: each person signs in with their own account.

```json title=".mcp.json"
{
  "mcpServers": {
    "flowkiwi": {
      "type": "http",
      "url": "https://<tenant>.product-management.flowkiwi.net/api/mcp",
      "headers": {
        "Flowkiwi-Api-Version": "2026-07"
      }
    }
  }
}
```

### Sign in

In Claude Code, run `/mcp`, select `flowkiwi` and choose **Authenticate**. Your browser opens the Flowkiwi sign-in and consent screen. You can also sign in from your terminal:

```bash
claude mcp login flowkiwi
```

To reset the connection, for example after a revocation or a 401 loop, run `/mcp`, select the server and choose **Clear authentication**, or run `claude mcp logout flowkiwi`, then sign in again.

> **Several instances**
>
> Access is bound to one instance URL. Add one server per instance, with a distinct name such as `flowkiwi-acme` and `flowkiwi-acme-staging`.