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

# Integrations

> Connect tools for your organization, choose which sites use them, and manage their access.

Integrations bring tools and data Fimo does not have into your site work. An organization admin connects an integration once and chooses the sites that can use it. Studio chat, agents, the Fimo CLI and the hosted MCP then use it on those sites.

Tool integrations and MCP servers live in **Integrations** in the organization sidebar, and **Settings** → **Integrations** in each site.

## Available integrations

| Integration | What Fimo can do with it | How you connect it |
| - | - | - |
| **Slack** | Answer mentions in the channels you choose | **Add to Slack** |
| **Semrush** | Answer about keyword rankings, backlinks, traffic estimates and competing domains | A Semrush API key |
| **Ahrefs** | Answer about backlinks, keyword rankings and organic traffic | Sign in with Ahrefs, or an Ahrefs MCP key |
| **Profound** | Answer about AI search visibility, citations and competitor performance | Sign in with Profound, or a Profound API key |
| **Peec AI** | Answer about AI search visibility, sentiment, citations and tracked prompts | Sign in with Peec AI, or a personal access token |
| **DataForSEO** | Answer about search results, keyword data and backlinks | Sign in with DataForSEO |
| **PostHog** | Answer about product analytics, experiments, feature flags and insights | Sign in with PostHog, or a PostHog personal API key |
| **Resend** | Read and send email, and manage contacts and domains | Sign in with Resend, or a Resend API key |
| **Calendly** | Read availability, scheduling links and meetings | Sign in with Calendly |
| **Cal.com** | Read availability, event types and bookings | Sign in with Cal.com |
| **Your own MCP server** | Use the tools the server offers, such as an internal tool or a CRM | Sign-in, a token, custom headers, or nothing at all |

> [!NOTE]
>
> **Google Search Console** and **Google Analytics** are in preview and not generally available yet. If they do not
> appear in **Integrations**, they are not available to you yet. See [Google Search Console and Google
> Analytics](#google-search-console-and-google-analytics-preview).

## Sync your site’s code

Use [Code Sync](https://fimo.ai/docs/studio/code-sync.md) in the site’s **Advanced settings** to keep code updated in connected repositories.

## Who can do what

* **Organization admins** manage everything about an integration itself in the organization's **Integrations**: they connect it, add MCP servers, choose which sites can use it, replace keys, credentials and sign-ins, and disconnect or delete it. The organization's **Integrations** also shows an MCP server's tools to every member.
* **People who manage a site** decide whether the site uses an integration and how: they turn it on or off for that site and fill in its settings, for integrations an admin gave the site access to. They can also add a custom MCP server to their site; it then shows in the organization's **Integrations** too.
* **Everyone working on the site** uses the integrations that are on, in chat and in agents.

Someone who is not an admin sees **Copy link** in the integration's panel instead of **Connect**, to send its link to an admin.

## Connect an integration

Open **Integrations** in the organization sidebar and choose the integration. Connecting needs no site: you connect once for the organization, then choose the sites that use it.

### Integrations you sign in to

For **Ahrefs**, **Profound**, **Peec AI**, **DataForSEO**, **PostHog**, **Resend**, **Calendly** or **Cal.com**, select **Connect** in the integration's panel. You go to the provider's sign-in page, approve the access Fimo asks for, and come back to Fimo.

With PostHog, Fimo asks for read access only. It answers questions about your data but cannot change your PostHog project. To let Fimo make changes in PostHog, connect it with a personal API key instead.

Finish signing in in the same browser where you started. A sign-in link opened by someone else, or in a browser signed in to Fimo as another person, is refused, so a forwarded link cannot connect the wrong account.

### Use an API key or a token instead

Some integrations also accept a key or token you create with the provider:

* **PostHog** and **Resend**: select **Use an API key instead**, paste a PostHog personal API key (it starts with `phx_`) or a Resend API key (it starts with `re_`), and select **Save key**.
* **Ahrefs**: select **Use an API key instead**, paste an Ahrefs MCP key, and select **Save key**. Ahrefs gives MCP keys on the Lite plan or higher.
* **Profound**: select **Use an API key instead** and paste a Profound API key. See [Profound authentication](https://docs.tryprofound.com/mcp/authentication).
* **Peec AI**: select **Use an API key instead** and paste a personal access token from **API Keys** → **Personal Access Tokens** in Peec AI. Use a personal access token for MCP, not a project API key. See [Peec AI setup](https://docs.peec.ai/mcp/setup).
* **Semrush**: select **Connect**. Semrush only lets the integrations it lists sign in, so Fimo connects with your Semrush API key. Semrush expects it in a special header, so Fimo fills in the header name **Authorization** and the value prefix `Apikey ` for you: paste your Semrush API key right after the prefix.

Profound and Peec AI require MCP access on the connected account. Available tools and data depend on that account’s permissions and provider plan. Check the provider’s setup documentation for current access requirements.

You find the same options next to **Connect** in a site's **Settings** → **Integrations**.

### Slack

After Fimo merges an edit from Slack, its reply includes the target Branch preview link when the build is ready. If the preview is still building or failed, the reply says so. Preview changes are separate from the published site. You can also ask for the preview link without making another edit.

Select **Add to Slack** on Slack's page, in the organization's **Integrations** or in a site's **Settings** → **Integrations**, and approve Fimo in Slack. Finish in the same browser where you started, signed in to Fimo as yourself: an **Add to Slack** link opened by someone else is refused. From a site, that site turns on for the workspace you just added. Slack connects one workspace per sign-in: to add another, select **Add another account** on Slack's page in the organization's **Integrations**. Then [choose each site's channels](#choose-slack-channels).

### Add your own MCP server

Select **Add MCP server** in the organization's **Integrations**, or in a site's **Settings** → **Integrations**. Enter a name and the server's `https://` address, then choose how Fimo connects under **Connect with**:

* **Sign in**: Fimo opens the server's sign-in page so you can approve access. A public server that needs no sign-in connects straight away.
* **Paste an access token**: for a token from whoever runs the server. Fimo sends it as a standard `Bearer` token.
* **Send custom headers**: for servers or gateways that need their own headers on every call. Enter each value exactly as the server expects it, including any prefix.
* **No authentication**: for open servers that need no credentials.

Fimo cannot check which of these a server accepts, so use a token or headers only if the server's owner gave them to you. Fimo encrypts every token and header value and never shows it again. The server's tools come from the server and can change over time.

## Choose the sites that use an integration

In the integration's panel under **Integrations**, go to **Site access**:

1. Choose **All sites** to turn the integration on for every site, including new ones, or **Only select sites** and pick the sites.
2. Save. Fimo turns the integration on for those sites.

With **All sites**, a new site gets the integration as soon as it is created. If the integration needs a site setting, such as a Search Console property, Fimo picks the one that matches the site's domain, or the site shows **Finish setup**. People who manage a site can still switch the integration off there, and it stays off.

With **Only select sites**, a site you leave out loses the integration, and its managers cannot turn it back on until an admin gives the site access again.

In each site, **Settings** → **Integrations** lists the integrations your organization connected and whether each is on for the site. People who manage the site can switch an integration off and on, and finish its setup when the integration needs a setting; everyone else sees the same panel without changing it. When you connect an integration from the site, its panel opens on **Finish setup** first if the integration still needs a setting, such as a Search Console property. When you ask Fimo for something an integration that still needs setup would answer, it shows a card that opens that setup and continues once you finish. Connecting a new integration from the card takes an organization admin; turning an integration on or finishing its setup takes someone who manages the site.

## Choose Slack channels

Open **Settings** → **Integrations** in the site, choose **Slack**, then **Workspaces and channels**. Each Slack workspace the site answers in has its own row: open it to turn it on for the site and choose the channels where Fimo answers mentions. Which sites use a workspace, and disconnecting it, are on Slack's page in the organization's **Integrations**: **Site access** and the account's **…** menu.

## Manage an MCP server

Open the integration in the organization's **Integrations**. Under **MCP server**, it shows the server's address and its tools, grouped by what they do: reading data, changing it, or deleting it. Open a group to see its tools, and a tool to read its full description.

A connected server can return an empty tool list. If Fimo cannot load its tools, the panel shows **Tools unavailable** instead. Looking up that specific integration in chat or the CLI also reports the connection problem, so a failed lookup does not look like an empty server.

Organization admins fix or change access from the same panel:

* **Reconnect** signs in again for a server that uses sign-in, for example after the sign-in expired or was revoked. It is in the **…** menu, and in the warning Studio shows when the server's tools stop loading.
* **Rotate credentials** in the **…** menu replaces a token or set of headers. When they stopped working, the warning offers **Update credentials** instead. Enter each value exactly as the server expects it.
* **Retry connection** asks a public server for its tools again.
* **Delete server**, in a custom server's **…** menu, removes the server from the organization, for every site that uses it. Studio asks you to confirm first.

## Use it in chat

Ask the way you would ask a colleague:

* "Which of our keywords lost rankings this month?"
* "How often do AI search answers cite our site compared with our competitors?"
* "How many people signed up from the new landing page this week?"
* "Read our competitor's pricing page and compare it with ours."
* "Watch the pricing page of example.com and tell me when it changes."

The chat finds the right integration tool, uses the data for this site only, and combines it with your site content when that helps.

If your question needs an integration that is not on for the site, the chat says which integration would help. An organization admin connects it in **Integrations** and gives the site access, and then the chat can use it.

## Changes need a yes

Most integration tools only read. Some change data in the outside service, such as a sitemap submitted to Search Console or an email sent through Resend. An MCP server's tool counts as a change unless the server marks it read-only. When the server says nothing either way, a tool whose name starts with a reading word, such as `get`, `list` or `search`, counts as a read.

Reads always run, and so do changes you run yourself in Studio or with the CLI. When an agent wants to make a change, from a Studio chat, a Slack thread, a routine, or an AI tool connected through the hosted MCP, Fimo asks first:

* Each change asks once, unless the tool is always allowed on the site.
* Actions that cost money ask every time. They cannot be always allowed.

In a Studio chat, the request shows the integration and the tool, with **Allow**, **Always allow on this site** and **Decline**. **Allow** lets the agent make that exact change once, in that chat. A request can be answered once, the approval works for one change, and both last one hour; a newer message from you also ends it. Fimo keeps a request only until it is answered, used or expired. **Always allow on this site** also lets agents use that tool on the site from then on without asking.

When a routine's run needs approval, the same request appears in its agent's chat, under the agent's reply. A routine cannot wait for a one-time approval, so it offers only **Always allow on this site** and **Decline**. **Always allow on this site** is all it takes: the routine runs again once by itself and makes the change. **Decline** runs nothing. A paused routine stays paused; the permission is saved for future runs.

Elsewhere, the agent or AI tool shares a link to Studio that shows the same request. From a Slack thread, **Allow** or **Always allow on this site** is all it takes: Fimo continues in the thread by itself. For an AI tool or the CLI, **Allow** shows a one-time approval code: paste it into the AI tool that asked, or run the same CLI command again with `--approval <code>`. The code works once, for that exact change, within the hour. After **Always allow on this site**, run the same command again: no code is needed. A link opened again after it was answered says so, with no buttons.

## Use it from the CLI or an MCP client

Coding agents and scripts use the same integrations with `fimo integrations`:

```bash theme={null}
fimo integrations list
fimo integrations tools --search "keyword rankings"
fimo integrations info search-console
fimo integrations run search-console query_search_analytics --input '{"dimensions":["query"],"days":28}'
```

A change that needs approval stops with `APP_APPROVAL_REQUIRED` and a link to Studio. Once someone allowed it there, run the same command again with `--approval <code>` and the code Studio showed, within the hour.

Organization admins can also connect from the CLI. Add an API key with `fimo integrations connect <integration> --token-stdin` for Ahrefs, Profound, Peec AI, PostHog or Resend, and add an MCP server with `fimo integrations add`. Manage MCP servers with `fimo integrations reconnect`, `fimo integrations rotate` and `fimo integrations remove`, and turn an integration on or off for a site with `fimo integrations enable` and `fimo integrations disable`. Sign in to Google, Slack, Ahrefs, Profound, Peec AI, DataForSEO, PostHog, Resend and Calendly from Studio. See [Add MCP servers](https://fimo.ai/docs/cli/mcp.md) and the [CLI reference](https://fimo.ai/docs/reference/cli.md#integrations).

The hosted MCP uses the integrations turned on for a site through five tools: `integrations_list`, `integrations_tools`, `integrations_guide`, `integrations_run` for reads and `integrations_write` for changes. It does not connect integrations. See [MCP tools](https://fimo.ai/docs/ai/mcp-tools.md).

## Google Search Console and Google Analytics (preview)

**Google Search Console** shows which Google searches bring people to your site, the clicks and impressions of each page, how each page ranks, and whether Google indexed it. **Google Analytics** shows who visits the site, where they come from, and what they do on each page, from your GA4 property. Fimo only reads Google Analytics.

When they are available to your organization:

1. Choose **Google Search Console** or **Google Analytics** in **Integrations** and select **Sign in with Google**.
2. Sign in with the Google account that can see your sites in Search Console or Google Analytics, and approve the permissions Fimo lists.
3. Back in the integration's panel, give the sites that need it access.
4. In each site, open **Settings** → **Integrations** and choose the **Search Console property** or **Google Analytics property** the site uses. Fimo suggests the property that matches the site's domain when there is one, and only lists properties the connected Google account can read.

Other admins see which Google account is connected. Nobody sees the account's password or tokens.

Google Search Console's panel in a site also shows **What agents can do on** the site:

* **Read search data**: clicks, impressions, positions, indexing and sitemaps. Always on.
* **Submit your sitemap to Google**: a switch, on by default. Agents ask Google to read the sitemap again after publishing new or moved pages, without asking you first.

People who manage the site can turn **Submit your sitemap to Google** off. Agents then ask before each submission, and the switch stays off until someone turns it back on. Selecting **Always allow on this site** on such a request turns the same switch on.

## Disconnect

Open **Integrations**, choose the integration, and open the **…** menu on its account:

* **Reconnect** signs in again, for example to fix access or switch accounts. Signing in with another account replaces the current one, and the sites keep their settings. An integration with a key offers **Replace key** instead.
* **Disconnect** stops using the account and removes the integration from every site, with its settings, its always-allowed tools and, for an MCP integration, its server. For a Google account, Fimo also revokes its access with Google. Connecting again starts from scratch. If the provider revokes access on its side instead, the integration shows **Reconnect** and keeps each site's settings.

Organization admins can **Rename** a custom MCP server from its **…** menu; the sites and agents that use it keep working. To remove a custom MCP server, use **Delete server** in the same menu: see [Manage an MCP server](#manage-an-mcp-server).

To remove Slack, disconnect the workspace from the account's **…** menu on Slack's page in the organization's **Integrations**.


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