Skip to main content
Beta — Real Talk Studio’s MCP integration is in beta. Anthropic’s custom connectors (remote MCP) feature is also in beta; UI labels and plan limits may change. See Anthropic’s custom connectors documentation for the latest details.
Use this guide to connect Real Talk Studio’s conversation simulations to Claude (claude.ai, Claude Desktop, Cowork, and mobile apps where remote connectors are supported). Once connected, you can ask Claude to create roleplay simulations in natural language.

​
What you’ll need

  • A Claude account on a plan that supports custom connectors (remote MCP) — available on Free, Pro, Max, Team, and Enterprise (Free is limited to one custom connector; Team/Enterprise owners add org-wide connectors).
  • Your Real Talk Studio MCP server URL — provided by Real Talk Studio.
  • If your MCP endpoint is inside a private network: inbound HTTPS from Anthropic’s IP ranges must be allowed. Remote connector traffic is initiated from Anthropic’s cloud, not from the user’s laptop, even in Claude Desktop. See Important notes below.

​
Add Real Talk Studio as a custom connector

Anthropic’s recommended path is Customize → Connectors. Do not rely on claude_desktop_config.json for remote MCP servers — Claude Desktop loads those connectors from your Claude account; remote servers are added through the Connectors UI, not as local stdio entries in the config file.

​
Pro or Max (individual)

  1. Open Customize → Connectors.
  2. Click +, then Add custom connector.
  3. Enter your Real Talk Studio MCP server URL (exact path as provided by Real Talk Studio).
  4. If Real Talk Studio supplies OAuth client details, open Advanced settings and enter the OAuth Client ID and OAuth Client Secret when instructed. If your deployment uses no authentication, leave advanced auth fields empty unless your admin says otherwise.
  5. Click Add to finish.

​
Team or Enterprise

Owner or Primary Owner (organisation-wide connector):
  1. Open Organisation settings → Connectors.
  2. Click Add.
  3. Hover Custom, then choose Web.
  4. Enter the Real Talk Studio MCP server URL and complete Advanced settings only if OAuth credentials are required.
  5. Click Add.
Members (after the owner has added the connector):
  1. Go to Customize → Connectors.
  2. Find the Custom connector your organisation added.
  3. Click Connect and complete any authentication steps.

​
Use the connector in a chat

  1. Start or open a conversation in Claude.
  2. Use the + control in the chat UI, choose Connectors, and enable Real Talk Studio for that conversation (wording may vary slightly by client).
  3. Ask Claude to create 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.”
Claude should invoke the Real Talk Studio tool and return a simulation link. Approve the tool request if Claude asks for confirmation.

​
Claude Code (optional)

If you use Claude Code, you can register the same remote server with HTTP transport: 
claude mcp add --transport http real-talk-studio <YOUR_MCP_SERVER_URL>
Use the /mcp command in a Claude Code session if the server requires OAuth. MCP servers you add in claude.ai may also appear automatically when you use Claude Code with a Claude.ai login — see Anthropic’s MCP documentation for Claude Code.

​
Important notes

​
Network and firewall

Remote MCP calls are made from Anthropic’s infrastructure. Your Real Talk Studio MCP URL must be reachable from the public internet (or from those IPs if you restrict ingress). If connections fail only from Claude but work from your browser, review allowlisting for Anthropic IP addresses alongside Real Talk Studio firewall guidance.

​
Transport

Claude supports Streamable HTTP (and SSE today, with SSE possibly deprecated later). Real Talk Studio’s MCP server uses Streamable HTTP, which aligns with Claude’s remote connector model.

​
Trust and approvals

Custom connectors can run arbitrary tools. Only connect to Real Talk Studio URLs your organisation issued, review tool-approval prompts, and follow Anthropic’s guidance in Security and privacy considerations for custom connectors.

​
Troubleshooting

IssueWhat to try
Cannot add a custom connectorConfirm your plan supports custom remote MCP; on Team/Enterprise, an Owner may need to add the org connector first.
Connection or timeout errorsEnsure the MCP URL is correct, TLS is valid, and Anthropic’s IPs can reach your server if you use IP restrictions.
Tools never runEnable the connector for the conversation via Connectors; use prompts that clearly mention roleplay, simulation, or conversation practice.
Works on public internet but not from ClaudeTraffic is from Anthropic’s cloud — allowlist their published ranges and check any WAF or geo rules.

​
Further reading

​
Need help?

Contact the Real Talk Studio team at realtalkstudio.com for MCP URLs, authentication, and simulation setup. For Claude-specific connector behaviour, use Anthropic support.