Integrations

Settings → Integrations has three tabs — Access Tokens, Webhooks and Social — which are gated on different plans:

Access tokens	Solo plan
Outbound webhooks	Org plan
Social connections	Org plan

Access tokens, webhooks and social connectionsOpen /a/settings/integrations in the app

×

Access tokens

A token allows an external client to act on your behalf — typically an AI agent over MCP, but also the curator browser extension or custom scripts.

Two properties distinguish a token from a password:

Scopes. A token carries only the permissions granted to it: reading workspaces, reading or writing wiki spaces, reading projects, submitting to ingestion. Over MCP, a tool outside the token’s scopes is not listed at all rather than listed and refused. The full list is in the MCP scope table.

A resource filter. A token can be restricted to specific resources rather than to everything its scopes would otherwise permit, and the filter can be amended after the token has been issued.

Revocation is immediate. A token that cannot be accounted for should be revoked rather than investigated; issuing a replacement has no cost.

Certain scopes require an elevated role before a token carrying them can be created. A scope absent from the list indicates a missing role rather than a fault.

The token is displayed once

Copy it at the point of creation. It cannot be retrieved afterwards; a lost token must be replaced.

Webhooks

An organisation can register outbound webhook endpoints. The platform calls the registered URL when an event occurs, removing the need to poll.

Endpoints can be created, edited and deleted, and each can be sent a test ping. Sending one is recommended before relying on an endpoint: a failed delivery produces no visible signal, which is indistinguishable from no event having occurred.

Social

Connected social accounts, used for cross-posting. Accounts are connected and disconnected here.

IntegrationsSettings → Integrations