Assistant help
Assistant access and MCP availability
Use Rollout’s public guides with an assistant today, and understand the current limits of account-connected MCP access.
Reviewed October 22, 2026
Account-connected MCP is not available yet. There is no customer MCP endpoint or supported client setup to connect today. This page will be updated when a tested connection is available.
Ask questions about the public guides
You can give an assistant a public guide URL and ask it to explain the workflow. This does not give it access to your account, release sheets or Todoist. Check its answer against the linked guide before acting.
Read https://releaserollout.com/docs/tasks/ and explain the difference between a campaign checklist and a linked Todoist project. Use only the documented features. Link your sources and say when the guide does not answer a question.
Use https://releaserollout.com/docs/integrations/ to help me prepare a CSV import. Explain what I should review after import. Do not assume there is continuous Google Sheets synchronization.
Account connection setup
Customer setup instructions are pending a tested release. When account access becomes available, this guide will list supported clients, the verified server address, the sign-in and consent steps, exact permissions, and how to disconnect or revoke access.
Do not paste a password, session cookie or Todoist API token into a chat. Public documentation access does not require those credentials. Connecting an assistant must not create broader account permissions.
Examples for a future account assistant
These examples describe intended interaction patterns. They are not working MCP commands, and the following actions are not available through a customer assistant today.
Summarize the selected release’s timeline and checklist. Read only. If the release is missing or inaccessible, stop and tell me.
Draft a release plan using only the details I supply. Mark missing dates and names as unknown. Show me the draft before saving anything.
Propose one Todoist task for the selected release. Show the destination project, title and due date before any action. Stop if access is denied.
The boundary for future access
An assistant should work only within explicit permissions and a fixed action budget. It should stop when blocked, uncertain or at risk. It should not expand its own scope, retry indefinitely or delegate around safeguards.