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

# Connecting Real Talk Studio with Slack

> Run Real Talk Studio simulations from Slack using MCP-capable AI apps from the Slack Marketplace.

<Info>
  **Beta** — Real Talk Studio’s MCP integration is in beta. Slack and third-party AI apps change their UIs and policies often; confirm labels and menus in your workspace against the latest [Slack Marketplace](https://slack.com/marketplace) and your AI vendor’s help centre.
</Info>

Slack is a common place to chat with **AI assistants** (Claude, Cursor, and others). To use **Real Talk Studio** there, you typically install an **MCP-capable** assistant from the Slack Marketplace, then register Real Talk Studio’s **remote MCP URL** in **that AI provider’s** connector settings — not in a generic “MCP URL” field inside Slack itself.

***

## What you’ll need

* Permission to **install or request** apps from the [Slack Marketplace](https://slack.com/marketplace) (often a **Workspace Owner** or **admin**).
* An **AI app in Slack** whose product supports **custom remote MCP** over **HTTPS** (Streamable HTTP). **[Claude](https://slack.com/marketplace/A08SF47R6P4-claude)** is a widely used example; availability and plans vary by region and org.
* Your **Real Talk Studio MCP server URL** — provided by Real Talk Studio.
* Optional clarity on **two different MCP roles**:
  * **[Slack’s MCP server](https://docs.slack.dev/ai/slack-mcp-server)** (`https://mcp.slack.com/mcp`) lets an assistant use **Slack workspace context** (search, channels, etc.).
  * **Real Talk Studio’s MCP server** exposes **simulation tools** (e.g. creating a roleplay). They are separate endpoints; an assistant may use **both** when the host supports multiple MCP servers.

***

## Step 1: Install an MCP-capable AI app in Slack

1. A workspace admin opens the [Slack Marketplace](https://slack.com/marketplace) (from Slack: **Apps** → **Browse apps** / **Slack Marketplace**, depending on client).
2. Choose an assistant that supports **remote MCP** in its parent product (for example, install **Claude** if your organisation uses Anthropic’s Slack integration).
3. Complete **install** and **OAuth** steps so members can use the app in **DMs**, **channels**, or the **assistant** experience your workspace uses.

Exact install flows depend on Slack edition (Pro, Business+, Enterprise Grid) and your **app management** policies.

***

## Step 2: Add Real Talk Studio in the AI provider’s MCP settings

Register Real Talk Studio where the **model host** manages tools:

* **Claude (Anthropic)** — Follow **[Connecting Real Talk Studio to Claude](/mcp-setup/claude)**: add a **custom connector** with your MCP URL under **[Customize → Connectors](https://claude.ai/customize/connectors)** (or your org’s **Connectors** admin on Team/Enterprise). That page covers authentication, **Anthropic IP allowlisting** for private endpoints, and enabling connectors per conversation.

* **Other assistants** — Use that vendor’s docs for **remote HTTP MCP**. Enter the **Real Talk Studio MCP URL** they ask for. If an app only supports **local stdio** MCP and not hosted HTTP, it may not work with Real Talk Studio’s cloud MCP until the vendor adds HTTP support.

***

## Step 3: Use Real Talk from a Slack conversation

1. Open the **DM**, **thread**, or **@mention** flow your AI app uses in Slack.
2. If the provider requires it, **enable connectors / tools** for that conversation (see their in-product UI).
3. Ask for a simulation, for example:

> "Create a roleplay simulation where a manager needs to give difficult feedback to a team member about consistent late delivery of work."

4. **Approve tool use** if prompted. You should get a **Real Talk Studio** simulation link in the thread.

***

## Slack’s MCP server vs Real Talk Studio

|                            | **Slack MCP server**                                                                       | **Real Talk Studio MCP**                                                              |
| -------------------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------- |
| **Purpose**                | Lets the assistant read and act in **Slack** (search, messages, canvases, etc.)            | Lets the assistant **create simulations** and related actions in **Real Talk Studio** |
| **Endpoint**               | `https://mcp.slack.com/mcp` (see [Slack docs](https://docs.slack.dev/ai/slack-mcp-server)) | URL provided by Real Talk Studio                                                      |
| **Where you configure it** | In the AI client / app per Slack’s MCP and OAuth requirements                              | In the **AI vendor’s** custom MCP / connector settings                                |

Using **both** is normal when you want answers grounded in Slack **and** the ability to spin up Real Talk simulations from the same assistant.

***

## Troubleshooting

| Issue                                       | What to try                                                                                                                                                                                                         |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cannot install the AI app                   | Ask a Slack admin; check **Manage apps** / Enterprise **app allowlists**.                                                                                                                                           |
| Assistant never invokes Real Talk           | Confirm the **custom connector** exists in the **provider’s** account (e.g. Anthropic), not only in Slack; enable it for the chat; use prompts that mention **roleplay** or **simulation**.                         |
| Slack AI behaves differently from claude.ai | Connectors are tied to the **vendor product**; ensure you’re using the same account and that the Slack app’s current documentation still maps to custom MCP connectors.                                             |
| MCP connection errors                       | Check the URL, HTTPS/TLS, and (for traffic to your own infrastructure) firewall rules — including [Anthropic IP ranges](https://docs.anthropic.com/en/api/ip-addresses) if those connectors call into your network. |

***

## Further reading

* Slack Help: [Guide to the Slack MCP server](https://slack.com/help/articles/48855576908307-Guide-to-the-Slack-MCP-server) (Slack as an MCP **server** for external AI clients)
* Slack Developer Docs: [Slack MCP server overview](https://docs.slack.dev/ai/slack-mcp-server)
* Real Talk Studio: [Claude MCP setup](/mcp-setup/claude)

***

## Need help?

Contact the Real Talk Studio team at [realtalkstudio.com](https://realtalkstudio.com) for MCP URLs, authentication, and simulation setup. For Slack installs, app policies, and Enterprise controls, see [Slack Help](https://slack.com/help).