[ developers and mcp ]
Customer-operations infrastructure for your AI agents
Every tool, rule and action Algomo builds is exposed over MCP. The interface we use to build an agent is the one you get.
[ 01 of 06 ] · ask it, click it, or script it. same agent.
Ask it, click it, or script it. Same agent.
Every operation lands the same way whichever surface calls it: the agent in conversation, the dashboard on screen, or any MCP client, whether that is Claude, Cursor, or an agent you built. Same primitives, every surface.
[ 02 of 06 ] · four primitives, one system
Four primitives, one system
Connections
Discovered from the site, or declared when they cannot be found.
Tools
Generated from connections, written at runtime on request, callable over MCP.
Rules
Permissions and limits, set in natural language, enforced everywhere the agent acts.
Channels
Deployment surfaces you switch on; the same tools and rules apply in each.
[ 03 of 06 ] · changes you can review before they ship
Changes you can review before they ship
Every change happens in a session you can diff and validate, then save or discard. Nothing reaches your visitors until you say so.
[ 04 of 06 ] · what you drive over mcp
What you drive over MCP
MCP is the interface, not an export
Configuration, tools, behaviour rules, content, deployment: point Claude, Cursor or your own agent at the server.
Drive the visitor's browser
Navigate, request, run a script, take a screenshot, in the visitor's own session; not something a competitor can copy quickly.
Write a tool at runtime
Ask for a capability it lacks and it writes the tool itself, on top of what your systems already do.
Repair on change
When endpoints move, it maps your site again and repairs the part that broke.
Repair on changeBring endpoints it cannot find
Discovery covers what your site calls for itself; auth-gated or internal endpoints are declared. Same tool interface either way.
Test before it reaches anyone
Generate a test reply against a thread; no real conversation touched.
[ 05 of 06 ] · quickstart
Quickstart
From connection to first tool call; the full reference lives on the Docs page.
[ 06 of 06 ] · built like infrastructure
Built like infrastructure
Observability
Every conversation, tool call and change is on the record; review what the agent did and why.
Version history
Changes land in sessions you can diff and validate, then save or discard. Nothing ships silently.
[ next step ]