AI agents (MCP)

Connect an AI client to the data and work you choose to share with it.

AI agents overview

Every plan, including Free, includes MCP. Free owners can make the same permitted changes as in the UI; Viewers cannot write. Paid scans, content briefs and market re-research remain subject to paid-plan gates and quotas.

An MCP connection lets a compatible client read permitted data and perform allowed work, such as updating context or handling tasks and campaigns. Permissions, company plans, roles and review rules determine what it can do. You can continue using the browser alongside an agent.

Use this guide to find connection settings and access controls. Client setup, tool descriptions and technical examples live in the Supasaito MCP overview and the app’s current MCP reference.

Find the connection method your client supports

Open MCP & API tokens in Settings. The screen shows the endpoint and explains OAuth and personal access tokens. OAuth uses browser sign-in and an access-consent screen. A personal token is a secret the connection owner creates and stores for the client.

Connection availability is checked across your companies and eligible Service access, not only the company currently selected in the browser. Seeing a connection option does not grant access to every company. Follow the MCP reference for setup rather than copying a tool catalog from this guide.

Choose and review the permitted resources

Select the companies and brands the connection needs and allow only the required actions. Future companies and brands are excluded unless you explicitly include them. Service conversations have a separate permission selection.

Use Edit permissions to review an existing token or connected app’s permissions. Older connections may have broader legacy permissions; inspect their scope before relying on it. Permission edits do not bypass your role, company limits or task-review rules.

Revoke a personal connection or block it for a company

In your personal connection settings, Revoke revokes a token and Connected apps (OAuth) lists authorised apps whose access you can revoke. Personal revocation disconnects the credential or app across its granted scope.

A company Owner or Admin can instead restrict a connection only for their company in History & Access, including blocking all of a member’s current and future MCP connections. That is separate from changing their human Team membership.