34Five Studio Connector
Understand the Studio application an Aura™ can hold.
Availability #
The Studio connector is built but not yet verified live. The required end-to-end walkthrough has not been completed, and the catalog entry is inactive until enabled. Do not treat the example below as a generally available feature.
What the connector does #
The Studio application lets an Aura™ use a connection to read one Studio workspace's identity, Team Members, Auras™, and Session History. It uses the same read-only MCP capability described in MCP Tool Reference.
A worked example #
A team wants an Aura™ to answer questions about action items from a previous session. Once the connector is enabled and verified, the team connects the intended Studio workspace, confirms its identity, and assigns the allowed connection. The Aura™ can then search Session History and retrieve the relevant session through the connected credential's role.
Multiple workspaces #
A connection is bound to one workspace. If an Aura™ holds connections to several Studios, confirm the intended account before reading. A credential issued by the target workspace determines that connection's access.
Next steps #
Review Connection Scopes and Security and Data Handling.