Personal access tokens for scripts and agents

Interactive AI apps connect by opening the Workspace369 sign-in page. A script, a scheduled job, or an agent running on a server cannot do that. For those, create a personal access token: a long-lived credential you paste into the client as a bearer token.

A token acts as you, in one workspace, with the scopes you choose. It can never do more than your own role allows, because every call is still checked against your live permissions.

Before you begin

• MCP must be enabled for the workspace by an admin. See Enable MCP and manage connected apps.
• Decide what the client needs. A reporting script needs view scopes only; give it nothing else.
• Have a secret manager or environment variable ready for the value. The token is shown once.

Create a token

1. Open Account settings and scroll to Connected AI apps.
2. Under Personal access tokens, choose Create token.
3. Enter a Token name that says what will use it, such as "Weekly revenue report".
4. Under Scopes, select only the scopes the client needs. The count of selected scopes is shown beside the label.
5. Under Expiry, choose 30 days, 90 days, 1 year, or No expiry. 90 days is the default and one year is the longest fixed expiry.
6. Choose Create token.
7. In the Token created dialog, copy the value and store it, then choose Done. The value is not shown again.

The token is scoped to the workspace you had open when you created it.

Use the token

Send it as a bearer token on every request to the MCP server:

Authorization: Bearer mcp_pat_…

In clients configured from a file, add it as a header on the server entry:

{
  "mcpServers": {
    "workspace369": {
      "url": "https://mcp.workspace369.com/mcp",
      "headers": {
        "Authorization": "Bearer mcp_pat_…"
      }
    }
  }
}

The server URL is the same one interactive apps use. To pin the token to a specific workspace URL, use the workspace-specific form described in Connect an AI app to your workspace.

What a token can and cannot do

• It carries only the scopes you selected. A call to a tool outside those scopes is refused.
• It is checked against your current permissions on every call. If your role changes, the token's reach changes with it.
• It stops working the moment you are removed from the workspace, and when an admin turns MCP off.
• Each call is paid in Tokens from the workspace balance, like any other MCP call. See How MCP access is controlled and billed.
• Anyone holding the token can act as you within its scopes. Treat it like a password.

Review and revoke tokens

Under Personal access tokens, each token shows its name, scopes, when it was last used, and when it expires. Expired tokens are labeled.

1. Find the token and choose Revoke.
2. Confirm. Any client using the token loses access immediately.

Admins see every member's tokens under Access tokens (all members) on the AI Connections (MCP) screen and can revoke any of them.

Rotate a token

1. Create the replacement token with the same scopes.
2. Update the client with the new value.
3. Revoke the old token.

Rotate whenever a token may have been exposed, when the person who created it leaves, and before a fixed expiry runs out.