> ## 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.

# MCP setup and management

> What the Model Context Protocol is, how Real Talk Studio uses it, and how to connect supported platforms.

<Info>
  **Beta** — Real Talk Studio’s MCP server and platform connectors are in beta. Capabilities, URLs, and setup steps may change; we recommend testing in a non-production agent before wide rollout.
</Info>

## What is MCP?

**Model Context Protocol (MCP)** is an open standard for connecting AI assistants and agents to external systems — tools, APIs, and data — in a consistent way. Instead of each platform inventing its own integration pattern, MCP defines how a **client** (your copilot or agent runtime) talks to an **MCP server** that exposes **tools** the model can call when a user’s request needs real actions (for example, creating a simulation or fetching structured data).

Real Talk Studio provides an MCP server so compatible platforms can **discover** our tools (such as creating roleplay simulations) and **invoke** them when the conversation warrants it, without custom code in your agent for every capability.

***

## How it works

1. **Registration** — In your platform’s admin or agent settings, you add Real Talk Studio as an MCP server using the **server URL** we provide. The client stores that endpoint and knows how to reach our server over HTTPS.

2. **Discovery** — The MCP server publishes a **tool catalog**: names, descriptions, and parameters. Your platform’s orchestration layer uses those descriptions to decide *when* a tool is relevant to the user’s message.

3. **Invocation** — When the model chooses a tool, the client sends a structured request to the MCP server. The server runs the action and returns a result (for example, a link to a simulation). The model can then surface that to the user in natural language.

4. **Transport** — Real Talk Studio’s MCP server uses **Streamable HTTP**, the transport pattern supported by modern MCP clients (including Microsoft Copilot Studio). No extra plugins are required beyond what the platform’s MCP onboarding asks for.

5. **Updates** — When we add or change tools on our side, connected clients typically **refresh the catalog** automatically, so new capabilities can appear without you redeploying custom integrations.

***

## Connect a platform

Use the guides below to wire Real Talk Studio into each supported environment. More platforms will be added over time.

<CardGroup cols={2}>
  <Card title="Microsoft Copilot Studio" icon="microsoft" href="/mcp-setup/copilot" horizontal>
    Add Real Talk Studio as an MCP tool and test simulations from the Copilot test panel.
  </Card>

  <Card title="Claude" icon="sparkles" href="/mcp-setup/claude" horizontal>
    Add Real Talk Studio as a custom remote MCP connector via Customize → Connectors (web, Desktop, and Claude Code).
  </Card>

  <Card title="Slack" icon="slack" href="/mcp-setup/slack" horizontal>
    Use Real Talk Studio from Slack via Marketplace AI apps (e.g. Claude) and the provider’s MCP connector settings.
  </Card>
</CardGroup>

***

## What you’ll need in general

* A **Real Talk Studio MCP server URL** (provided by Real Talk Studio for your organisation or deployment).
* Appropriate **admin or customizer** access in the target platform to add tools and connections.
* **Network access** to reach our MCP endpoint over HTTPS (see [Firewall configuration](/it-admin/firewall-configuration) if traffic is restricted).

For product support, credentials, or environment-specific questions, see [How to get help](/it-admin/how-to-get-help).