Prostack CIto

This is currently in beta.Feedbackis very welcome.

Authentication is required- when you connect your AI tool you will be redirected to the Prostack portal to login.

When you first log in you'll be prompted to authorise the MCP server for your account.

Run the following in your terminal client:

claude mcp add --transport http Cito https://mcp.prostack.uk/mcp

Then start a Claude Code session and use the/mcpcommand to authenticate. A browser will open to log you into the Prostack Portal.

Once you're authenticated you can close the browser window and switch back to your terminal. You can then try a test prompt, such as "Tell me what Cito servers I have?". This should trigger thecito_list_serverstool.

The MCP URL ishttps://mcp.prostack.uk/mcp- you can name it Cito.

Once it's added, click the 'Connect' button and you will be directed to the portal to login. From there you can start a chat - e.g. by asking 'Is my Cito server healthy?'

Settings → Tools & MCP → Add MCP Paste in the following JSON:

{ "mcpServers": { "Cito": { "url": "https://mcp.prostack.uk/mcp" } } }

You can ask for things in natural language:

- "Tell me if my server is healthy"
- "Fetch the error logs for my staging website"
- "Create a new Wordpress site"
- "Show me the last 50 lines of the error log for example.com"
- "Create a MySQL database called app_db and add a read-only user to it"
- "Clonemywebsite.comtostaging.mywebsite.com.

These will trigger the appropriate tool call.

If you have multiple servers, you can prompt the AI to work with a specific server.

You can ask your AI tool to create a new site. You'll be prompted for the necessary information- site type, domain name, username and framework.

"Deploy this project to Cito" is supported for local clients, such as Claude Code and Cursor.

- Detect the site type (Laravel, NodeJS etc). This is done by looking at the files in the project repository.
- Offer to create a site with the correct deployment profile, or use an existing site if specified.
- Rsync files to the chosen site. The MCP server will generate an ephemeral SSH keypair to do this. The private key is never persisted to disk and is deleted afterwards.
- Run any post-install commands. The commands are based on the project type detected- e.g.composer installornpm install. Only specific, framework-relevant commands are supported.

Deployment uses tools available on your local machine. You will be prompted through each step.

Certain files are excluded from deployment by default, and will not be rsynced to the server. These include:

- .git,.github,.gitlab-ci.yml
- node_modules/
- .env,.env.local,.env.*.local- you must configure environment variables via SSH or File Manager.
- tests,__tests__,spec,coverage
- IDE files (.idea,.vscode)
- Build configs (Dockerfile,docker-compose.yml)
- Documentation (README.md,CHANGELOG.md)

The MCP serverdoesallow you to delete files, sites or databases. We take a conservative approach here, and have built-in guardrails for these tool calls.

Before carrying out any destructive action, the MCP server will prompt you to confirm if you wish to proceed.

Certain features of the Cito dashboard are not currently available via MCP. This includes:

- Anti-malware scanning and detection
- Outbound email logs
- Managing docker containers
- Configuring redirects, cron jobs or caching.

If any of these would be useful to you,let us know.

This MCP server is in beta. Whilst it has undergone extensive testing, LLMs can still behave in unexpected ways, so you should be careful to review all tool calls before running them. You should prompt as carefully as you can to ensure you get accurate results.

We take the following safety precautions when deploying via the MCP server:

- SSH private keys are never stored. We generate ephemeral SSH keys, use these to deploy to Cito, and delete them afterwards. We do not use your local SSH keys or access them.
- Arbitrary commands are not supported. The MCP server can only run specific, authorised commands related to the framework of the site you're deploying. Unauthorised commands are rejected.
- The MCP server cannot read/write files outside of/home.
- Destructive operations, such as deleting a site, require confirmation to proceed.

Contact support via theusual channelsif you experience issues or have feature requests.

Please provide as much detail as possible if you encounter bugs- including the prompts and conversation history if possible.

Create, build, deploy, and manage Netlify resources using natural language.

European cloud hosting. Use your favorite AI coding assistant to easily deploy and manage apps on Ploi Cloud.

Simplifies framework deployments on various hosting environments, with a focus on shared hosting.

Expose the entire ArgoCD API to LLMs via MCP using just 2 auto-generated tools powered by the OpenAPI spec.

Bult.ai MCP Server lets Claude Desktop deploy and manage Bult.ai cloud hosting resources, including projects, services, GitHub and Docker deployments, routes, volumes, templates, logs, and build history.

Integrate with the Coolify API to manage your servers, applications, and databases.

An MCP server for interacting with the Coolify API to manage servers and applications.

An MCP server for integrating with Coolify, the self-hostable alternative to Netlify and Vercel.