Koyeb MCP Server
Enables programmatic management of Koyeb resources, allowing users to list, create, and update apps and services, manage deployments and instances, and query build and runtime logs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Koyeb MCP Server list all my apps and their current status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Koyeb MCP Server
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
Install the package from npmjs:
npm install -g @koyeb/mcp-serverSet your Koyeb API token:
Create a token at Koyeb API settings and export it:
export KOYEB_TOKEN=your_token_hereStart the MCP server:
koyeb-mcpThe server will connect via stdio and expose the Koyeb API as MCP tools.
License
MIT
Available Tools
16 toolscreate-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
Scored across 16 tools
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.
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.
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.
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
Deploy applications and manage governed Kubernetes preview spaces and capacity.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with Linear's API for managing issues, teams, and projects programmatically through the Model Context Protocol.783 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with FireHydrant's incident management API through the Model Context Protocol. Provides programmatic access to FireHydrant's features for managing incidents, retrospectives, and operational workflows.385 npm5MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with the Edgee API for managing organizations, projects, domains, components, users, invitations, and API tokens through the Model Context Protocol.Apache 2.0
- AlicenseBqualityNot gradedmaintenanceEnables comprehensive management of DuploCloud infrastructure, including tenants, services, hosts, databases, and storage. It provides tools for lifecycle operations on cloud resources like ECS tasks and S3 buckets through the Model Context Protocol.31MIT