Cloudpepper Update
MCP now available
Cloudpepper now speaks MCP.
Hook up your AI assistant (Claude, Claude Code, Codex, or any other MCP client) and it runs your hosting and tunes your Odoo right alongside you. Nothing new to learn. You ask, it does the work.
Connect in a minute
- Add the server URL
https://mcp.cloudpepper.ioin Claude, Claude Code, or Codex. - A sign-in page opens. Log in to Cloudpepper and pick the account you want the assistant to act on.
- Approve, and the tools are there.
The per-client walkthrough is in the setup guide.
Run your whole platform
- Spin up servers. Add a Cloudpepper server or connect your own box over SSH (AWS, Hetzner, DigitalOcean, you name it). Just say what you need.
- Backups on demand. Grab a backup before a risky change. Restore one when something goes sideways. All by asking.
- Manage instances and domains. Deploy, update, point a domain. The stuff you’d click through in the dashboard, now you just say it.
Find what’s slow. Fix it.
- Catch slow queries. Your assistant reads the slow-query log and points at the exact ones dragging a screen down. In plain terms: which page is slow, and why.
- Add the missing index. It spots the queries that belong on an index and adds it for you. Next load is fast.
- See what’s running right now. Watch the queries hitting your database live. Handy when Odoo stalls mid-import and you need to know what’s holding it up.
- EXPLAIN before you commit. Run EXPLAIN on any query and read the plan together, so you fix the cause instead of guessing.
Optimize your own code
Point it at the custom modules you’re building. It works against your live database (your real schema, your real data), so the advice fits your app instead of a generic checklist. A slow ORM call, a query that should be batched, an index you forgot. It catches them while you’re still writing the code, not after a customer complains.
It acts as you, not as a shared key
Every action the assistant takes lands in your audit log under your name, and it can only do what your role allows. A read-only teammate stays read-only, even through the assistant. The access is scoped to you, not your whole workspace, and there is no long-lived key to store or leak. And every tool got tested and tuned before this shipped: adding a server, creating a backup, reading a query plan. They each do exactly what they say.
Who can use it
MCP access is available on Pro and Agency. Set it up from your Cloudpepper dashboard. Then ask it to find your slowest query. Good first question.