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 (for example https://www.realtalkstudio.com/api/mcp). Do not use the apex host or app.realtalkstudio.com (Supabase).
  • OAuth — Claude registers itself automatically. Only add an OAuth Client ID / Secret in Advanced settings if automatic registration fails.
  • An organization admin Real Talk Studio login to complete the browser consent screen.
  • 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.
  4. Click Add, then complete the browser consent flow (sign in as an org admin and approve access for your organization).
  5. If Claude asks for an OAuth Client ID, open Advanced settings and enter the Client ID and secret from your Real Talk Studio admin.

​
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. Leave Advanced OAuth fields empty unless automatic registration fails.
  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 the Real Talk Studio consent screen (org admin required).

​
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. You can also ask Claude to list, read, or archive org simulations, add one to a studio, or pull a usage report (get_org_report). Claude can test 1:1 and team scenarios (test_simulation — predicted example transcript + realism, not a live engine run). Refine (refine_simulation — propose then confirm with expected_updated_at) is 1:1 only and can change backstory, structure, avatar fields, the learning objective, and skill good/poor examples (the score rubric). Preview links need login and organization credits. Soft-archive hides a scenario from the org catalog but does not remove studio links or archive personas. Studios with domain restrictions return an iframe embed snippet instead of a bare learner URL.

​
Claude Code (optional)

If you use Claude Code, you can register the same remote server with HTTP transport:
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

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