Skip to main content
The Agent Builder MCP server authenticates through Labs OAuth. Use a client with Streamable HTTP, OAuth, and Client ID Metadata Documents (CIMD) support. The client opens sign-in and consent, then manages token storage and refresh. Keep the final / in the server URL. It is part of the OAuth resource identifier. See client setup for client-specific requirements and connection limitations.

​
Workspace permissions

The voai scope grants service access. Your current workspace membership and role determine which tools you can use. Reading workspace resources requires Viewer or higher. Agent creation and editing require Editor or higher. Some tool or telephony operations require Admin or Owner; check the individual tool’s requirements. Workspace selection is shared by your account. Switching through MCP affects subsequent requests from the console and other connected MCP clients. Switching does not grant access to a workspace you do not belong to.

​
API keys and REST tokens

Labs API keys and tokens issued for REST endpoints cannot authenticate to this MCP server. Do not add X-BW-LABS-AGENTS-API-KEY or X-VOAI-ORGANIZATION-ID to an MCP connection. For a server-to-server REST integration, use REST authentication.

​
Reconnect

If access expires or your client reports an authentication error, repeat the client’s OAuth login. If authentication succeeds but a tool returns a permission error, check the selected workspace and your role. See MCP troubleshooting.