Chatfuel MCP Sign-In, Read-Only Access and CLI Token
Sign in with Chatfuel on the consent screen, turn on Read-only to let the assistant only look, or use a CLI token as a Bearer header. Revoke in Connected apps.
Last updated on
The Chatfuel MCP server works on your behalf with the same permissions as your Chatfuel account. Most assistants connect by signing in with Chatfuel in the browser, where you can choose read-only access. Assistants that can't open a browser, scripts and CI connect with a CLI token instead.
How does signing in with Chatfuel work?
When you add the server link, the assistant opens the Chatfuel sign-in page. Log in with your Chatfuel account and approve access on the consent screen. The assistant then works with the bots and workspaces you can access, with your role in each bot. The assistant never sees your Chatfuel password.
The MCP link https://mcp.chatfuel.com/panel and the API MCP link https://mcp.chatfuel.com/panel/api are separate connections, so sign in to each one you add.
How to give the assistant read-only access
On the consent screen for https://mcp.chatfuel.com/panel, turn on Read-only. With read-only access the assistant can list bots, read Automations, the Knowledge Base, posts and chats, review chats and diagnose the bot, but it can't change anything or send messages. The default is full access.
Read-only access is available only on the MCP link. The API MCP link always works with full access, because some GraphQL queries also change data.
How to switch from read-only to full access
Disconnect Chatfuel in the assistant, connect again and leave Read-only off on the consent screen. The same works the other way round.
How to revoke the assistant's access
Open Connected apps in the Chatfuel dashboard (panel.chatfuel.com/connected-apps) and revoke the assistant. The assistant then has to sign in again before it can use Chatfuel.
When to use a CLI token
A CLI token (Beta) is for assistants that can't sign in through the browser, and for scripts and CI. The assistant sends the token in the Authorization: Bearer <token> header on every request, and it works on both links with full access.
- In the Chatfuel dashboard, open the account menu → CLI token (panel.chatfuel.com/integration/auth/token).
- Click Create token and copy it. The token is shown only once.
- Add the token as a header in your assistant. The exact command for each assistant is on its setup page, for example how to connect Claude Code to Chatfuel.
Anyone with the token can access your Chatfuel account, so keep it secret and out of shared files and repositories. The CLI token is the same personal API token described in Public API authentication and tokens.
Common issues
The assistant can see my bots but can't change anything
The connection was made with Read-only on. Disconnect Chatfuel in the assistant, connect again and leave Read-only off.
I signed in, but the developer link still asks me to sign in
The MCP link and the API MCP link are separate connections. Sign in to the API MCP link as well.
Should my team share one CLI token?
No. Everyone who uses a CLI token acts as its owner. On team plans in Claude and other assistants, let each person sign in with their own Chatfuel account instead.