Skip to content
34Five.ai / Documentation
Open Studio ↗
Documentation

Find an answer

Browse popular starting points

DocumentationConnect an Agent
Connect an Agent

Studio MCP Quickstart

Connect an external agent to one Studio workspace and verify its identity.

Studio / MCP v1Reviewed 2026-10-24
Documentation previewDraft content · Staging instructions · Not approved for production
On this pageBefore you connectConnect with your agentConnect by handIf your agent cannot open a browserYour first useful readNext steps

The example address below is a placeholder, not a working service. Replace https://mcp.example.com/v1/mcp with the approved Studio MCP URL supplied by your workspace administrator before using any command, configuration, or prompt.

Before you connect #

You need a supported MCP client, an enabled Studio workspace, and permission to read its data. An approved server URL and enabled access are required. Client setup must be verified for your workspace.

The Studio MCP server uses Streamable HTTP at a versioned path:

text
https://mcp.example.com/v1/mcp

Connect with your agent #

Replace the example address, then copy this prompt into your client. Complete the client's connector setup and Studio sign-in when prompted.

text
Help me connect this client to the 34Five Studio MCP server at https://mcp.example.com/v1/mcp using OAuth. Explain any configuration I must complete myself. After I authorize the connection, call 34five_whoami and report the workspace and role. Stop if either differs from what I expect. Do not request, display, or store my password or API key in this chat.

Choose the setup guide for Claude.ai, Claude Code, Cursor, or ChatGPT. A prompt cannot bypass client or organization permissions.

Connect by hand #

  1. Add the server URL to your client's remote MCP configuration.
  2. Choose OAuth, sign in to Studio, and review the requested consent.
  3. Select the intended workspace if offered a choice.
  4. Enable the connection in your conversation.
  5. Ask the client to call 34five_whoami.

One connection is bound to one workspace. Add a separate connection to use another workspace.

If your agent cannot open a browser #

A headless client can use an API key through the Authorization header. Configure the secret in your client's supported secret store. Do not paste it into a prompt or commit it.

Your first useful read #

After identity verification, ask for a small page of Auras™ or recent sessions. Use MCP Tool Reference for arguments and pagination. The server exposes reads; it does not add write access.

Next steps #

Review Errors, Limits, and Versioning and Security and Data Handling.

34Five DocumentationPrivacyContent 2b5e203ea2