Skip to main content
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 and your AI vendor’s help centre.
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 (often a Workspace Owner or admin).
  • An AI app in Slack whose product supports custom remote MCP over HTTPS (Streamable HTTP). 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://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 (from Slack: AppsBrowse 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: add a custom connector with your MCP URL under 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.”
  1. 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 serverReal Talk Studio MCP
PurposeLets the assistant read and act in Slack (search, messages, canvases, etc.)Lets the assistant create simulations and related actions in Real Talk Studio
Endpointhttps://mcp.slack.com/mcp (see Slack docs)URL provided by Real Talk Studio
Where you configure itIn the AI client / app per Slack’s MCP and OAuth requirementsIn 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

IssueWhat to try
Cannot install the AI appAsk a Slack admin; check Manage apps / Enterprise app allowlists.
Assistant never invokes Real TalkConfirm 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.aiConnectors 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 errorsCheck the URL, HTTPS/TLS, and (for traffic to your own infrastructure) firewall rules — including Anthropic IP ranges if those connectors call into your network.

Further reading


Need help?

Contact the Real Talk Studio team at realtalkstudio.com for MCP URLs, authentication, and simulation setup. For Slack installs, app policies, and Enterprise controls, see Slack Help.