Cloudpepper MCP
Cloudpepper speaks MCP. Connect Claude, Claude Code, or Codex to your account and your assistant runs your hosting and reads your live PostgreSQL, over an authenticated connection scoped to your role.
MCP (Model Context Protocol) is the open standard that AI assistants use to talk to outside tools. Cloudpepper runs an MCP server at https://mcp.cloudpepper.io. Once it is connected, you ask your assistant in plain language and it does the work you would otherwise click through in the dashboard.
What you can do
Section titled “What you can do”- Run your platform. Create servers, deploy instances, take backups, manage domains and modules, all by asking.
- Find what is slow. Read the slow-query log, run EXPLAIN, and see what is hitting the database right now.
- Fix it. Add a missing index or tune PostgreSQL to your server’s resources.
- Work on your own code. Point the assistant at the custom modules you are building and it checks them against your real schema and data, not a generic checklist.
MCP access is available on Pro and Agency plans. You connect by signing in with your Cloudpepper account, and your assistant acts with your permissions. See Connect Claude or Codex.
Safe by design
Section titled “Safe by design”The hosted server exposes read and write tools only. Read tools have no side effects. Write tools are additive and reversible, and the ones that restart a service ask first.
Destructive actions, like deleting an instance, restoring a backup over a live database, or uninstalling a module, are not available over MCP. They stay in the dashboard, where they need a typed confirmation. See Safety and permissions.
Prefer raw HTTP?
Section titled “Prefer raw HTTP?”MCP is the way in for AI agents. For scripts and CI, the full REST API is documented at api.cloudpepper.io.