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

# Use Searchable in Slack and Microsoft Teams

> Ask Searchable from Slack and Teams through Claude Tag, Slackbot, Copilot Studio and Microsoft 365 Copilot.

Searchable's MCP server works with the AI agents that live in Slack and Microsoft Teams. Your team can ask about AI visibility, competitors and citations without leaving the chat.

| Route | Where it runs | Who sets it up |
| - | - | - |
| Claude Tag | Slack channels | Each person, for their own requests. A Claude admin, for a whole channel. |
| Slackbot | Slack | A developer who can build a Slack app, and a Slack admin |
| Copilot Studio | Microsoft Teams | A Copilot Studio agent maker |
| Microsoft 365 Copilot | Microsoft 365 Copilot chat | A developer using the Microsoft 365 Agents Toolkit |

> [!NOTE]
>
> Slack, Microsoft and Anthropic own these screens and change them. Each step below links the
> vendor's own page, so follow that page when a menu doesn't match.

## Prerequisites

* **A paid Searchable plan.** MCP isn't available on the Free plan. See the [MCP guide](/integrations/mcp).
* **Access to the projects you want to ask about.** You choose which ones when you authorize a connection.
* **Claude Tag:** a Claude Team or Enterprise plan, with Claude Tag [set up in your Slack workspace](https://claude.com/docs/claude-tag/admins/setup-overview) by a Claude Owner.
* **Slackbot:** a developer who can create a Slack app in your workspace, and a Slack admin who can approve it.
* **Copilot Studio:** permission to create and publish agents, and a Teams admin who allows Power Platform apps.
* **Microsoft 365 Copilot:** Visual Studio Code with the Microsoft 365 Agents Toolkit (version 6.12.0 or later), and a Microsoft 365 account that allows custom app upload.

## Quick setup

The fastest route is Claude Tag with your own Searchable connector, once Claude Tag is in your Slack workspace.

**1. Connect Searchable to Claude**

Add Searchable as a custom connector on your Claude account. The Claude tab in the [MCP guide](/integrations/mcp#setup) has the steps.

**2. Ask in a channel**

In a channel where Claude Tag is installed, send:

```
@Claude list my Searchable projects
```

**3. Allow your connector**

Claude replies in the thread with a prompt that only you can see, asking whether it may use your connectors. Choose **Allow with review** to check each result before it posts, or **Allow**.

**4. Read the answer**

Claude posts your project list in the thread. Everyone in the channel can read it.

Want the whole channel to use Searchable, or scheduled checks? Set up a [channel connection](#give-each-slack-channel-its-own-searchable-access). Using Slackbot or Teams? Follow the tab for your route below.

## Detailed configuration

**Claude Tag (Slack)**

Claude Tag puts Claude in your Slack channels. It is in public beta and available on Claude Team and Enterprise plans. Channel work is billed by usage to your organization, under a spend limit an Owner sets. See [Claude's overview](https://claude.com/docs/claude-tag/overview).

There are two ways to give it Searchable:

* **Your own connector.** This is the Quick setup above. Claude asks first, then uses your connector with your permissions and only for requests you make. A teammate's request never uses it, and neither does a routine. What Claude posts back is readable by everyone in the channel. See [personal connectors](https://claude.com/docs/claude-tag/concepts/personal-connectors).
* **A channel connection.** A Claude admin attaches Searchable to a channel. Everyone there gets the same access, and routines use it. See [adding connections](https://claude.com/docs/claude-tag/admins/add-connections), and set it up in the next section.

Memory belongs to the channel, not to you. Anyone in the channel can read and change it, so don't ask Claude to remember anything private there. See [memory](https://claude.com/docs/claude-tag/users/memory).

**Slackbot (Slack)**

Slackbot is Slack's own assistant. It reaches remote MCP servers through a Slack app. See [Slack's guide](https://docs.slack.dev/ai/slackbot-mcp-client).

**1. Add Searchable to a Slack app**

Someone who builds Slack apps creates one for your workspace. In its settings, open **Features → MCP Servers → Get Started** and enter the name `Searchable`, the URL `https://app.searchable.com/api/mcp-server/mcp`, and the dynamic client registration auth type, which Searchable supports. Slack adds the `mcp:connect` bot scope for you.

**2. Have an admin approve it**

Install the app in your workspace. Where your workspace requires approval, an admin approves it from Slack's app management page. Until then Searchable doesn't appear in Slackbot. See [admin approval](https://docs.slack.dev/ai/slackbot-mcp-client/admin-approval).

**3. Connect your account**

In a direct message with Slackbot, use the **Apps** button in the Slackbot toolbar to connect Searchable. Slack sends you to Searchable to sign in, choose projects, and decide on write access. Write access is off by default.

**4. Approve tool calls**

Slackbot asks you to approve each tool call: **Allow once**, **Always allow** or **Deny**. You can change this later in the MCP config dialog.

Slack cuts off a tool that takes longer than 60 seconds, and each person can have up to 5 active MCP servers. Slack lists MCP support in Slackbot as available on all subscriptions, but Slackbot access and limits vary by subscription, and admin controls over MCP servers exist only on some plans. See [Slack's help article](https://slack.com/help/articles/52414744085139-Connect-Slackbot-to-other-apps-with-MCP) for yours.

**Copilot Studio (Teams)**

A Copilot Studio agent can use Searchable as an MCP tool and run in Teams. See [Microsoft's MCP guide](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent).

**1. Add Searchable as a tool**

Open your agent, go to **Tools**, and select **Add a tool → New tool → Model Context Protocol**. Enter the server name `Searchable`, a short description of what it does, and the URL `https://app.searchable.com/api/mcp-server/mcp`. The agent uses the description to decide when to call the server.

**2. Choose the sign-in**

Select **OAuth 2.0**, then **Dynamic discovery**. Searchable supports dynamic client registration with discovery. Select **Create** and **Next**, then **Create a new connection** and **Add to agent**.

If you pick **API key** instead, choose **Header** and enter `Authorization` as the header name. Each person then supplies a Searchable access token, which Searchable expects in the form `Bearer` followed by the token.

**3. Publish to Teams**

Publish the agent, then open **Channels → Teams and Microsoft Copilot** and select **Add channel**. Share the agent with the people who should use it, then install it in Teams. See [Microsoft's publishing guide](https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams).

Use the agent in a one-to-one chat. Microsoft documents that in Teams group chats and channels, agents can't use knowledge sources that need each person to sign in, and that such agents are supported only in one-to-one chats. Searchable also signs each person in, so treat it the same way.

Copilot Studio bills agent use in Copilot Credits. Use by people with a Microsoft 365 Copilot license is included, and everyone else draws on your organization's Copilot Credits. See [Microsoft's billing rates](https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-messages-management).

**Microsoft 365 Copilot**

Microsoft 365 Copilot reaches Searchable through a declarative agent with an MCP plugin. You build it in Visual Studio Code with the Microsoft 365 Agents Toolkit. See [Microsoft's walkthrough](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/build-mcp-plugins).

**1. Create the agent**

In the Agents Toolkit, select **Create a New Agent/App → Declarative Agent → Add an Action → Start with an MCP Server**. Enter `https://app.searchable.com/api/mcp-server/mcp`.

**2. Pick dynamic registration**

For the authentication type, select **OAuth (with dynamic registration)**. Microsoft registers a client with Searchable at runtime, so you enter no client ID or secret. Microsoft requires the server to issue a client secret, and Searchable does. See [Microsoft's DCR page](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/plugin-authentication-dynamic-client-registration).

**3. Provision and try it**

In the **Lifecycle** pane, select **Provision**. Then open [Microsoft 365 Copilot chat](https://m365.cloud.microsoft/chat), pick your agent in the **Agents** list, and ask a Searchable question. Select the sign-in prompt when Copilot shows it.

Use the Agents Toolkit for this. Microsoft says the Teams developer portal doesn't support dynamic registration yet. Searchable's interactive cards render only where Copilot supports MCP Apps. See [Microsoft's MCP Apps page](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/plugin-mcp-apps).

## Give each Slack channel its own Searchable access

When a Claude admin attaches a connection to a channel, everyone there gets the same access, whoever asks. Routines use it too. So keep it small: one project, read-only.

**1. Generate a token for the channel**

In Searchable, open **Manage Account → Integrations → MCP → Access tokens** and click **Generate
access token**. Name it after the channel, limit it to one project, and copy it. Tokens made
here are read-only, so Claude can look things up but can't change your projects.

**2. Attach it to the channel**

A Claude Owner or Claude Tag admin works in **Organization settings → Claude Tag**. Claude's
guide to [adding a custom MCP
server](https://claude.com/docs/claude-tag/admins/connections/custom) has two parts. First, a
plugin whose `.mcp.json` points at `https://app.searchable.com/api/mcp-server/mcp`. Second, a
custom connector with the **Bearer** credential type, your token as the key, and
`app.searchable.com` as the allowed website. Put both in one
[bundle](https://claude.com/docs/claude-tag/admins/add-connections#create-a-bundle) and add only
that channel under **Where it applies**.

**3. Test it in a new thread**

In the channel, send `@Claude list the Searchable projects you can use`. You should see only
that one project. Plugins apply to new threads only, so start a fresh thread.

> [!WARNING]
>
> Anyone in the channel can ask Claude for anything the token can read, and the answers post in the
> thread. A read-only token can still create a shareable report link, as any project member can in
> the app. Attach it only to channels where everyone may see that project's data.

### Why a token and not a sign-in per channel

Signing in to Searchable once per channel looks simpler, but it breaks. A new sign-in from the same app that narrows the projects revokes your other connections for that app, so each new channel would cut off the one before it. And if you select every project you can see, Searchable stores that as "all projects", which also covers projects you create later. A token is fixed to its project and is revoked on its own.

## Routines that check Searchable for you

A routine is standing work Claude runs in a channel on a schedule. It uses that channel's connections with the same permissions as a typed request. So it needs the channel connection above. Your own connector is never used for a routine. See [Claude's routines page](https://claude.com/docs/claude-tag/users/proactivity).

* **Send the message in the channel where results should post.**
* **Name the timezone.** Schedules run in UTC, so say "every weekday at 9am Eastern". A routine keeps its UTC time, so its local time shifts by an hour when the clocks change. Ask Claude to reschedule it if that matters.
* **Say when to stay quiet.** Tell the routine to post only when something changed.
* **Anyone in the channel can manage its routines.** Send `@Claude !routines` to list them, or ask Claude to disable or move one by name.

### Weekday visibility check

**Category:** Monitoring · **Uses:** `get_visibility` (`compare: "previous_period"`, `group_by: "platform"`)

Posts only when your AI visibility moved by more than 5 percentage points against the period before, and names the AI platforms that moved most. On quiet days the channel hears nothing.

```
@Claude every weekday at 9am Eastern, using the Searchable MCP, compare our AI
visibility for the last 7 days with the 7 days before. Post here only if it
moved by more than 5 percentage points, and say which AI platforms moved most.
On days it didn't, post nothing.
```

### Weekly competitor watch

**Category:** Monitoring · **Uses:** `get_competitors`, `get_share_of_voice` (`compare: "previous_period"`), `get_sentiment`

Once a week, checks your tracked competitors for share-of-voice or sentiment moves worth a reaction. Weeks with nothing to report stay silent.

```
@Claude every Monday at 9am Eastern, using the Searchable MCP, check our
tracked competitors against the week before. Post a short summary of any
competitor whose share of voice or sentiment moved meaningfully, and anything
worth a response from us. If nothing moved, post nothing.
```

### Citation-loss check

**Category:** Monitoring · **Uses:** `investigate` (`question: "citation_gap"`)

Watches how often AI answers cite your site and speaks up only when that is falling.

```
@Claude every Monday at 8am Eastern, using the Searchable MCP, check whether
AI answers are citing us less than before. Look at our citation trend for the
last 90 days and our citation share per AI engine. Post here only if citations
are falling: say which engines lost ground and which source domains AI answers
cite instead. If citations held or grew, post nothing.
```

## What doesn't work yet

* **Searchable doesn't post into Slack or Teams on its own.** There are no Searchable alerts, digests or notifications in either app. An agent asks Searchable when someone asks, or when a Claude Tag routine runs.
* **Teams channels and group chats.** Microsoft documents that in Teams group chats and channels, agents can't use knowledge sources that need each person to sign in, and that such agents are supported only in one-to-one chats. Searchable also signs each person in, so treat it the same way. See [Microsoft's known limitations](https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams#known-limitations).
* **Cards depend on the host.** Searchable's interactive cards need a host that renders MCP Apps. [Microsoft documents that support](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/plugin-mcp-apps) for Microsoft 365 Copilot, and [Slack documents it](https://docs.slack.dev/ai/slackbot-mcp-client/returning-rich-responses) for Slackbot. Anywhere else you get the same answer as text. See [Interactive cards](/integrations/mcp#interactive-cards).
* **@ChatGPT and Slack Connect.** OpenAI says @ChatGPT in Slack doesn't support Slack Connect channels shared with another organization. See [OpenAI's Slack page](https://learn.chatgpt.com/docs/third-party/slack).

## Verification and testing

Ask every route the same first question:

```
List my Searchable projects
```

In Claude Tag, start with `@Claude`. You should see the projects you approved on Searchable's consent screen, or the one project on a channel's access token. Then ask a real question, such as "What's our AI visibility this week compared with last week?"

Then check from Searchable's side. **Manage Account → Integrations → MCP** lists the assistants you've authorized under **Connected apps**, and your **Access tokens**. Disconnect an app or revoke a token there to cut it off.

To check a routine, send `@Claude !routines` in the channel. It lists each routine with its schedule in UTC.

## Troubleshooting

> **Claude says it can't reach Searchable**
>
> A routine or a teammate's request can't use your own connector. It needs the [channel connection](#give-each-slack-channel-its-own-searchable-access).
>
> If the channel connection exists, check three things:
>
> * `app.searchable.com` is in the connector's **Allowed websites**. Claude blocks requests to hosts you haven't allowed, and names the host in the thread.
> * The credential isn't marked **Not enabled** on its connector page. If it is, select **Enable**.
> * You are in a new thread. A plugin added after a thread started doesn't reach it.

> **Claude Tag doesn't ask before using my connector**
>
> You may have saved **Allow** or **Allow with review** earlier. Change it on the **Home** tab of
> the Claude app in Slack, which offers **Auto mode**, **Ask every time** and **Allow with review**.

> **Searchable is missing from Slackbot**
>
> Where your workspace requires approval, Slackbot lists an app's MCP server only after an admin
> approves the app. Also check that the app has the `mcp:connect` bot scope and lists Searchable
> under its MCP servers, then reinstall the app after any change.

> **Slackbot fails to load tools or times out**
>
> Confirm you finished the Searchable sign-in. If you disconnected the app in Searchable under **Connected apps**, connect it again.
>
> Slack cuts off tools after 60 seconds. For a big question, ask for a shorter period or one AI platform.

> **The Copilot Studio agent says there is a billing issue**
>
> If it says "There is a billing issue." or "This agent is currently unavailable. It has reached its
> usage limit.", your organization has used its Copilot Credit capacity. Microsoft disables custom
> agents at 125% of prepaid capacity, and an admin can add capacity. Separately, as a precaution,
> use the agent in one-to-one chats. See [What doesn't work yet](#what-doesnt-work-yet).

> **My Microsoft 365 Copilot agent doesn't show up**
>
> In the Agents Toolkit **Accounts** pane, check that both **Custom App Upload Enabled** and
> **Copilot Access Enabled** show under your account. If either is missing, ask your Microsoft 365
> admin. In Copilot, look for your agent's name with `dev` added at the end.

> **The assistant sees fewer projects than I expected**
>
> What an assistant sees is set when you authorize it: the projects you ticked on Searchable's consent screen, or the one project on an access token. Ask "List my Searchable projects" to see what it has. To change it, connect again and choose the projects you want. For other errors, see [MCP troubleshooting](/integrations/mcp).

More prompts to try are on the [Use cases](/use-cases) page.


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