--- title: 'Coolify MCP server for Claude Code, Cursor, and Codex' description: >- Turn on the Coolify MCP server from your MapleDeploy dashboard and let Claude Code, Cursor, or Codex deploy and manage your apps. Hosted in Toronto. keywords: - coolify mcp server - coolify mcp - deploy from Claude Code - deploy from Cursor - deploy from Codex - manage Coolify with AI - Model Context Protocol Coolify - AI agent deploy apps - self-hosted PaaS MCP heading: 'Deploy from Claude Code, Cursor, or Codex' service_type: Managed Coolify hosting lastUpdated: '2026-09-24' type: article author: Ross Hill locale: en_CA site_name: MapleDeploy slogan: Powerful hosting on Canadian soil organization_url: 'https://mapledeploy.ca/' logo: 'https://mapledeploy.ca//api/logo/lockup' creator: MapleDeploy publisher: MapleDeploy founding_date: '2026-01-13' email: hello@mapledeploy.ca geo_region: CA-ON geo_placename: Toronto address_country: CA area_served: Canada application_category: DeveloperApplication app_url: 'https://app.mapledeploy.ca' llms_txt: 'https://mapledeploy.ca/llms.txt' offers: >- Starter $45/mo, Pro $95/mo, Ultra $195/mo, Ultra 32 $395/mo, Ultra 64 $695/mo CAD in_language: en-CA canonical_url: 'https://mapledeploy.ca/coolify-mcp-server' --- {% hero-section title="Deploy From Claude Code, Cursor, or Codex" %} Your MapleDeploy server has an MCP endpoint built in. Turn it on, and your AI coding client can deploy your apps, restart services, and read logs on your own server in Toronto. {% button href="https://app.mapledeploy.ca/signup" size="large" %} Start your free trial {% /button %} {% /hero-section %} {% intro-section %} The Model Context Protocol (MCP) is how AI clients like Claude Code, Cursor, and Codex connect to outside tools. The endpoint lives at /mcp on your server, part of the Coolify install your plan already includes. There are no scripts to write, no third-party wrapper to trust, and nothing extra to host. {% /intro-section %} {% icon-feature-grid title="What your AI client can do once it's on:" %} {% icon-feature-item icon="refresh" title="Deploy and redeploy" %} Ask for a deploy after a change. The client queues the same deployment you would start by hand. {% /icon-feature-item %} {% icon-feature-item icon="server" title="Start, stop, restart" %} Start, stop, or restart an app, database, or service without opening a dashboard. {% /icon-feature-item %} {% icon-feature-item icon="terminal" title="Read logs" %} Pull recent logs into the conversation, so the client can help you debug what just broke. {% /icon-feature-item %} {% icon-feature-item icon="lock" title="Limited by its token" %} The API token you give the client sets its limits. A read token can look around. A deploy token can act. {% /icon-feature-item %} {% /icon-feature-grid %} {% numbered-steps-section title="How it works" %} {% numbered-step number=1 title="Turn it on" %} In the MapleDeploy dashboard, open your server's Tools tab and turn on the MCP server. You see exactly what it exposes before you confirm. {% /numbered-step %} {% numbered-step number=2 title="Create an API token" %} In Coolify, go to Security, then API Tokens, and create a token with only the abilities your client needs. The token signs the client in and limits what it can do. {% /numbered-step %} {% numbered-step number=3 title="Connect your client" %} Add your server's /mcp endpoint and your token to Claude Code, Cursor, or Codex. Then ask it to deploy. {% /numbered-step %} {% /numbered-steps-section %} {% content-section title="What it exposes" %} Once it is on, any Coolify API token on your instance can reach the endpoint, including read-only tokens. Keep each token's abilities as narrow as the job needs. The realistic risk is prompt injection: text your client reads that tries to steer what it does next. The endpoint never returns environment variable values, only their names. You can turn it off at any time from the same dashboard setting, and the [setup guide](/docs/coolify-mcp-server) covers token abilities in detail. {% /content-section %} {% content-section title="On Canadian infrastructure" %} Your server, its Coolify instance, and the MCP endpoint all run on a dedicated VM in Toronto. Deploys run there, and your application data stays there, governed by [Canadian privacy law](/canadian-hosting) rather than the US CLOUD Act. Anything your client reads through the endpoint, such as logs, becomes part of its conversation with its AI provider, like the code you write with it. Choose token abilities with that in mind. The endpoint uses your server's existing HTTPS address, so there is no new port to open. It stays off until you turn it on. {% /content-section %} {% content-section title="Built on open source" %} The MCP server is not a MapleDeploy add-on. It ships with [Coolify](/open-source-stack), the open-source platform your server runs, so you can read exactly how the endpoint and each of its tools behave in the source. If an AI client helped you build the project, this closes the loop: the [same client that wrote your code](/blog/deploy-your-ai-built-project) can now deploy it, on infrastructure you control. {% /content-section %} {% cta-section title="Ready to deploy with your AI client?" button-text="Start free trial" %} 30 days free on Starter and Pro. Start a server, turn on the MCP server, and deploy a real project from Claude Code, Cursor, or Codex. The [setup guide](/docs/coolify-mcp-server) walks you through connecting your client. {% /cta-section %}