Skip to main content
Glama

Koyeb MCP Server

NOTE

Koyeb MCP is currently a beta pre-release. Feedback, bug reports, and contributions are welcome! Please open an issue or pull request.

Planned features: Secrets, volumes, domains, pause/resume, update app, cancel deployment, metrics, log tailing

A Model Context Protocol (MCP) server implementation for the Koyeb API. This project enables programmatic management of Koyeb resources (apps, services, deployments, instances, logs, and more) via the MCP protocol.

Features

  • App Management

    • List, get, and create Koyeb apps

  • Service Management

    • List, get, create, and update services within apps

  • Deployment Management

    • List and get deployments, query build/runtime logs

  • Instance Management

    • List and get instances for deployments/services

  • One-Click Apps

    • List available one-click (example) apps on Koyeb

Related MCP server: FireHydrant MCP Server

Adding MCP config to your client

Add the following to your .cursor/mcp.json or claude_desktop_config.json.

{
  "mcpServers": {
    "koyebApi": {
      "command": "npx",
      "args": ["-y", "@koyeb/mcp-server"],
      "env": {
        "KOYEB_TOKEN": "your_token_here"
      }
    }
  }
}

CLI usage

  1. Install the package from npmjs:

npm install -g @koyeb/mcp-server
  1. Set your Koyeb API token:

Create a token at Koyeb API settings and export it:

export KOYEB_TOKEN=your_token_here
  1. Start the MCP server:

koyeb-mcp

The server will connect via stdio and expose the Koyeb API as MCP tools.

License

MIT

Available Tools

16 tools
create-appD

Create an app

Inputs: body (required).

create-serviceC

Create a new service inside an existing app

Inputs: body (required), query.

deployC

Deploy a directory to Koyeb

Inputs: path (required), appName (required), serviceName (required), definition.

execC

Execute a command in a running deployment

Inputs: instanceId (required), command (required), shell.

get-appC

Get an app by its id

Inputs: path (required).

get-deploymentB

Get a specific deployment by its id

Inputs: path (required).

get-instanceC

Get a specific instance by its id

Inputs: path (required).

get-serviceC

Get a specific service by its id

Inputs: path (required).

get-tokenB

Get the Koyeb API token

Inputs: no named parameters.

list-appsD

List apps

Inputs: query (required).

list-deploymentsC

Get the list of deployments

Inputs: query (required).

list-instancesD

Get the list of instances

Inputs: query (required).

list-one-click-appsB

List one-click apps (example applications) that can be deployed on Koyeb

Inputs: no named parameters.

list-servicesC

Get the list of services

Inputs: query (required).

query-logsC

Get the build or runtime logs

Inputs: query (required).

update-serviceC

Update a service's configuration by creating a new deployment

Inputs: path (required), body (required), query.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources and actions in the Koyeb platform. For example, create-app vs. create-service target different entities, and get-* tools are clearly scoped to individual resource types. No tools appear to overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with hyphen separation (e.g., create-app, list-apps, get-service). The pattern is applied uniformly across all 16 tools, making them predictable and easy to understand.

    Tool Count4/5

    16 tools is slightly on the higher side but reasonable for a comprehensive cloud deployment platform. It covers core operations for apps, services, deployments, instances, and logs without feeling excessively bloated. The count aligns well with the platform's scope.

    Completeness4/5

    The toolset provides strong coverage for the Koyeb domain, including CRUD operations for key resources (apps, services, deployments, instances) and essential utilities like logs and token management. Minor gaps might include operations like deleting resources or scaling services, but core workflows are well-supported.

    Related MCP Connectors

    Related MCP Servers