Koyeb MCP server

What the model can do

Koyeb serverless platform: apps, services with status and current deployment, deployments with what they run (repository, branch, image, regions, instance types) and why they failed, running instances by region, domains and their DNS state, volumes, the organisation's activity feed, hours of use per service and plan quotas; when you ask, can redeploy, pause or resume a service or a whole app, cancel a pending deployment, create or rename an app, add, re-check or remove a custom domain, and delete a service, an app or a volume.

Reads

• koyeb_appsKoyeb apps (groups of services): name, status (HEALTHY, PAUSED, DEGRADED …), domains and when it last changed.
• koyeb_servicesServices (web services, workers, databases): name, type, status, app, active and latest deployment ids and Koyeb's status messages.
• koyeb_deploymentsDeployments, newest first as Koyeb lists them: status, what was deployed (repository and branch or image, commit), regions, instance types, scaling…
• koyeb_instancesInstances (running replicas): status, region, datacenter, instance type and replica number, for a service, app or deployment.
• koyeb_domainsDomains: Koyeb-assigned (<app>-<org>.koyeb.app) and custom ones, with status (PENDING, ACTIVE, ERROR), the app each points at…
• koyeb_volumesPersistent volumes: name, region, status (attached or detached), size in GB and the service using it.
• koyeb_activityThe organisation's activity feed, newest first: what happened (created, updated, deleted, redeployed, paused …) to which app, service…
• koyeb_usageHours of compute per app, service, region and instance type for a period (Koyeb reports time used, not prices)…

Acts, when you ask

These change something in Koyeb. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• koyeb_redeploy_serviceRedeploys a Koyeb service to production now: Koyeb builds it again (unless skip_build) from its current definition, or from the commit sha given…
• koyeb_pause_servicePauses a Koyeb service: its instances stop and it serves nothing until resumed with koyeb_resume_service.
• koyeb_resume_serviceResumes a paused Koyeb service, starting its instances again (billing restarts).
• koyeb_pause_appPauses a whole Koyeb app: EVERY service in it stops serving until the app is resumed.
• koyeb_resume_appResumes a paused Koyeb app and its services (billing restarts).
• koyeb_cancel_deploymentCancels a Koyeb deployment that is still pending, provisioning or scheduled; it will not go live and cannot be resumed (a new deploy is needed).
• koyeb_create_appCreates an empty Koyeb app (a container for services, with its own <name>-<org>.koyeb.app domain).
• koyeb_rename_appRenames a Koyeb app.
• koyeb_add_domainAdds a custom domain to a Koyeb app.
• koyeb_refresh_domainAsks Koyeb to re-check a domain's DNS now (after the CNAME was set), rather than waiting.
• koyeb_delete_domainRemoves a domain from Koyeb; the app stops answering on it at once.
• koyeb_delete_servicePermanently deletes a Koyeb service, its deployments and instances; it stops serving immediately.
• koyeb_delete_appPermanently deletes a Koyeb app together with EVERY service in it and its domains.
• koyeb_delete_volumePermanently deletes a Koyeb volume and the data on it.

Connect it

First connect Koyeb on Dashboard → Connections, then add Memtro to your client once. The Koyeb tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Koyeb connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Why did the latest deployment of the api service fail?
• › Which services are unhealthy right now?
• › Which instances are unhealthy, and in which region?
• › How many hours did each service use last month?
• › Redeploy the worker service.

Questions

Is this an official Koyeb MCP server?

No. It is Memtro's MCP server with Memtro's Koyeb connector behind it: the connector reads Koyeb through its API with the credentials you connect on Dashboard → Connections, and Koyeb publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Koyeb?

Only when you ask, and only what it has been granted: redeploy a service (builds and ships it again); pause a service; resume a paused service; pause every service in an app; resume a paused app; cancel a pending deployment; create an app; rename an app; add a custom domain to an app; re-check a domain's DNS; remove a domain; delete a service; delete an app and its services; delete a volume. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server