Access and Permissions

Authentication. The Attentive MCP server authenticates through Attentive's standard login using OAuth. When you first connect, your MCP client opens an Attentive login page in your browser. After you sign in, the client receives a token and the connection is established. You never paste an Attentive password or API key into a configuration file.

Permission scoping. The tools available to your assistant mirror your own Attentive UI permissions. You can only see and act on the companies and capabilities your Attentive user already has access to. If you cannot do something in the Attentive UI, your assistant cannot do it through the MCP server.

Read-only by default. Every connection starts in read-only mode. In read-only mode, the assistant can retrieve data (reporting, existing campaigns, segments, and configuration) but cannot create, edit, or delete anything. To enable write actions, you opt in explicitly when you connect (see Configuration options).

Confirmation on writes. When write actions are enabled and your MCP client supports confirmation prompts, the server asks you to confirm before it changes data in your account. Keep a human in the loop for higher-risk actions such as scheduling or launching a send.