> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fimo.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Add MCP servers

> Add a remote MCP server as an integration for your organization from the CLI, with sign-in, a token, custom headers, or no authentication.

Give your sites tools from a remote MCP server, such as an issue tracker or monitoring service. The server becomes an integration of your organization that Studio chat, agents, the CLI and the hosted MCP can use. People who manage a site can add a server to it; it then shows in the organization's Integrations too. Adding one from the organization's Integrations, with no site, needs an organization admin.

> [!NOTE]
>
> To work on Fimo itself from ChatGPT, Claude, or another AI integration, see [Build your site from ChatGPT or
> Claude](/docs/ai/mcp.md) instead.

## Add a server

`fimo integrations add` adds a remote Streamable HTTP server for your organization and turns it on for the current site:

```bash theme={null}
fimo integrations add crm --url https://mcp.example.com/mcp
fimo integrations list
fimo integrations tools mcp_crm
fimo integrations run mcp_crm <tool> --input '{"key":"value"}'
```

`fimo integrations list` shows the server's integration id, such as `mcp_crm`. Use it with `fimo integrations tools`, `fimo integrations info` and `fimo integrations run`. When an agent wants to run a server tool that changes data, Fimo asks first. See [Changes need a yes](/docs/studio/integrations.md#changes-need-a-yes).

By default, `--auth auto` asks the server how to connect. A public server connects straight away. A server that needs sign-in opens its sign-in page in your browser; add `--no-open` to print the URL instead.

Remote MCP servers must use HTTPS. Local package runners such as `pnpm dlx`, `npx`, `yarn dlx`, and `bunx` are not supported.

## Choose how Fimo signs in

Pick the method the server's owner documents. Pipe secrets on stdin so they stay out of your shell history.

| Method | Flags | Use it for |
| - | - | - |
| Automatic | `--auth auto` (default) | Servers with browser sign-in, and public servers |
| Public | `--auth none` | Open servers that need no credentials |
| Bearer token | `--auth bearer --token-stdin` | A token sent as `Authorization: Bearer <token>` |
| One header | `--auth header --header-name <name> --token-stdin` | A server that expects its own header |
| Several headers | `--auth header --header <name> --header <name> --headers-stdin` | Gateways that need several headers on every call |

A bearer token:

```bash theme={null}
printf '%s\n' "$MCP_TOKEN" | fimo integrations add crm \
  --url https://mcp.example.com/mcp \
  --auth bearer \
  --token-stdin
```

Several headers, as one JSON object of complete header values:

```bash theme={null}
printf '%s\n' "{\"X-Api-Key\":\"$API_KEY\",\"X-Tenant\":\"acme\"}" | fimo integrations add crm \
  --url https://mcp.example.com/mcp \
  --auth header \
  --header X-Api-Key \
  --header X-Tenant \
  --headers-stdin
```

A header value is sent exactly as you give it, so include any prefix the server expects.

## Connect a catalog integration with a token

Semrush, Ahrefs, DataForSEO, PostHog, Resend, Calendly and Cal.com are in the [Integrations](/docs/studio/integrations.md) catalog. Connect them in Studio. To connect Semrush with its API key from the CLI instead, add its server with the catalog address. Semrush expects the key in the `Authorization` header with the `Apikey` prefix:

```bash theme={null}
printf 'Apikey %s\n' "$SEMRUSH_API_KEY" | fimo integrations add semrush \
  --url https://mcp.semrush.com/v2/mcp \
  --auth header \
  --header-name Authorization \
  --token-stdin
```

For an Ahrefs MCP key, a PostHog personal API key or a Resend API key, use `fimo integrations connect ahrefs --token-stdin`, `fimo integrations connect posthog --token-stdin` or `fimo integrations connect resend --token-stdin`.

## Manage a server

```bash theme={null}
fimo integrations reconnect mcp_crm
printf '%s\n' "$NEW_TOKEN" | fimo integrations rotate mcp_crm --token-stdin
fimo integrations remove mcp_crm --yes
```

* `fimo integrations reconnect` signs in again to a server that uses browser sign-in.
* `fimo integrations rotate` replaces the credentials: `--token-stdin` for a bearer token, or `--headers-stdin` with the complete JSON object for a server that uses headers.
* `fimo integrations remove` deletes the server and its credentials for every site of the organization.

The older `fimo mcp` commands still work and print a warning. Use `fimo integrations` instead.

Manage the same servers visually in [Integrations](/docs/studio/integrations.md).

## What's next

> **[Integrations](/docs/studio/integrations.md)**
>
> Connect integrations and choose the sites that use them.

> **[CLI reference](/docs/reference/cli.md#integrations)**
>
> Every `fimo integrations` command and flag.

> **[Automate your site](/docs/automate/overview.md)**
>
> Choose how work starts and runs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.