Scopes

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.

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.

Getting started

Reference

Resources

Upgrading a connection

​Upgrading a connection

Upgrading a connection