Skip to main content
Sign in to Agent Builder once to initialize your workspace. You need a Labs user API key and an MCP client that supports Streamable HTTP with custom headers.

​
Connection details

The endpoint is also available in Settings → MCP Server. Use the positive integer ID of a workspace the key owner belongs to. Ask your workspace administrator for the ID if needed. Alternatively, a client with a Labs OAuth integration can send Authorization: Bearer YOUR_LABS_ACCESS_TOKEN. That request uses the user’s selected workspace. An API key cannot be used as a bearer token; do not send both credential types together.

​
Connect and verify

  1. Open the MCP server settings in your client.
  2. Add the endpoint and both API-key headers above.
  3. Save the key using the client’s secret or environment-variable support.
  4. Connect and review the available tools.
  5. Ask the assistant to list your agents and confirm the expected workspace is returned.
Use your client’s documented remote-server configuration. Keep credentials out of shared configuration files. See authentication for key management and workspace access.

​
Tasks to try

  • List the agents in my workspace.
  • Show the definition of my appointment agent.
  • Find documentation about webhook payloads.
  • Update the greeting in my agent’s draft.
Review proposed changes before letting an assistant perform actions. Tools enforce the key owner’s workspace role; a Viewer cannot perform Editor or Admin operations. Inspect and test saved drafts, then publish when ready. The workspace server manages your product resources. A documentation search MCP server, if offered by the docs site, is a separate connection.