The Livalos MCP: your agents at work on your website
The problem
AI assistants such as Claude or ChatGPT can do a lot, but they cannot see your systems. If you want an assistant to create a page, look up a contact or prepare a quote, it needs access. Doing that safely is hard. Sharing keys or granting broad rights is a risk.
The approach
MCP stands for Model Context Protocol. It is a standard that lets an AI assistant use tools a system offers. The Livalos MCP runs on app.livalos.com and works like this:
Sign in with OAuth. Your assistant asks you to sign in with your dashboard account. No passwords are shared.
Your rights, no more. An assistant gets the rights of your role on your site. What you cannot do, it cannot do either.
- 213 tools. They come from the description of our platform API and cover CRM, deals, tickets, pages, quotes, invoices, projects and newsletters.
Limits and a log. At most 1,000 requests per hour and 300 write actions per hour. Every action goes into an audit log. Deleting asks for confirmation first.
Our own agents use the same route. What we give customers, we use ourselves.
The result
| Number | Value |
|---|---|
| Tools for sites | 213 |
| Limit per hour | 1,000 requests, 300 write actions |
| Sign-in | OAuth 2.1 with your dashboard account |
| Status | The MCP server runs on app.livalos.com. The site tools go live with the next platform release |
Source: Livalos dashboard and platform API, as of 09-11-2026.