Overview
How to operate an Algomo workspace from an assistant, what a change goes through before it is live, and every operation the server exposes.
Algomo runs an AI agent on your website. You configure, test and review that agent from the dashboard or from an assistant you already use, such as Claude, ChatGPT, Claude Code, Codex or Cursor, over Algomo's MCP server. Both work on the same workspace and the same edit sessions.
Connect an assistant
Add the server to your client, sign in, and make your first change.
Sessions and publishing
What a staged change is, how it is reviewed, and when it goes live.
Permissions
What a connected assistant can read, change and run, and what it cannot.
Operation reference
Every operation with its tool and schemas, from the server's own catalogue.
Where things happen
| You want to | Use |
|---|---|
| Change a chatbot, a goal, a tool, a card or a knowledge-base page | An assistant or the dashboard; either way the change is staged in a session |
| Review what is about to go live | The dashboard, with the session selected; an assistant can give you the link |
| Make it live | Publish the session, in the dashboard or through the assistant's publish tool |
| See what a visitor was told, or why a workflow failed | An assistant, through the read tool |
| Try the agent before visitors see a change | A test conversation, through an assistant or the dashboard's test panel |
Help
Troubleshooting lists the errors a connected assistant can run into and what to do about each. To reach a person, email support@algomo.com; Support lists what to include.