ChatGPT Workspace Agents

Add STACK as a custom MCP in the Workspace Agent builder. The agent can then use the STACK tools that the workspace and the STACK session allow.

Run fleet Missions

Connect the service and approve the fleet policy before starting automated work. The approved provisioner enrolls workers with their own keys. A worker uses its key to obtain a short-lived MCP session, then calls stack_start_mission with the job’s exact access and limits.

Use the returned Passport for calls through STACK. Routine allowed calls require no additional approval. Call stack_renew_mission to continue the same job without resetting its allowance. The client can obtain another session and reconnect with the worker’s key when its MCP session expires.

Interactive OAuth signs the client in as a member. Fleet execution uses the enrolled worker’s identity. Use a client or application runtime that can present the worker’s session token for this flow.

1. Prerequisites

• A ChatGPT Business, Enterprise, or Edu workspace with Workspace Agents enabled.
• Permission to add a custom MCP to the agent.
• A STACK account with at least one service connected at https://getstack.run/app/connect.

2. Add the custom MCP

In the agent builder, open Tools. Select Add tool, then add a custom MCP with this endpoint:

https://mcp.getstack.run/mcp

Complete the STACK OAuth prompt. Scan the tool list. Test one read-only tool before you enable write actions.

3. Choose the account model

• End-user account: each person signs in to STACK. Use this for per-user attribution and access.
• Agent-owned account: the agent uses one shared connection. Use a service account and narrow its access.

Do not use a founder or administrator account as the shared agent account. The account model controls whose STACK authority the Workspace Agent uses.

4. Configure controls

• Allow only the STACK tools that the agent needs.
• Keep confirmation enabled for actions that send, edit, publish, pay, or delete.
• Use STACK service grants and Passports to narrow agent actions beyond the workspace tool list.
• Review the first test actions in the STACK audit log.

5. Revoke access

Remove or disable the custom MCP in the workspace to stop discovery there. Revoke the STACK MCP session in Settings to invalidate its refresh-token family. Revoke a Passport separately when the agent run used task-bound Passport authority.