Scopes - Botdog API

The Botdog MCP server uses two scopes:

Scope	Display name	Grants
`mcp.read`	Read your campaigns, analytics, leads, lists, sender accounts, webhooks, users, and team	Every read tool: campaigns and campaign statistics, analytics, users, team, leads, replies, lists, sender accounts and their daily limits, paused campaign activities, snippets, webhooks, and the API setup guide.
`mcp.write`	Manage your campaigns (pause/resume), leads, lists, and webhooks	Create and update campaigns, pause/resume campaigns or individual activities, add leads to campaigns and lists, create lists, delete leads from a list, update lead details, stop a lead, create and update snippets, update account sending limits, and create/update/delete webhooks. Implies `mcp.read`.

When connecting, the consent screen lets you check or uncheck each scope your client requested. Every requested scope starts checked. mcp.write tools also require a seat on the team you connected. Without one, read tools keep working and write tools return a “You do not have a seat assigned” error.

Team read-only policy

A team owner or admin can limit every AI app connected to the team to read-only, under Settings → Integrations → AI apps. While it is on:

The consent screen does not offer mcp.write for that team.
Connections that were granted mcp.write earlier keep working, but only the read tools are listed, and write tools return a team_read_only error.
Switching it off restores write access to those connections; nobody needs to reconnect.

Upgrading a connection

To add the write scope to an existing connection, remove the Botdog connector from your AI client and add it again. The client runs a fresh OAuth flow — leave mcp.write checked on the consent screen.