MCP tools
Kyno exposes the following tools. Tool names and required fields below match the current server definitions.
Kyno reports the active plan, role, used and remaining app slots, idle timeout,
and enforced resource ceilings during MCP initialization and with every tool
result. Call get_account_limits before planning a deployment. Tool discovery
is role-aware, and the control plane independently enforces the same plan and
permission limits.
| Tool | Purpose |
|---|---|
get_account_limits |
Return the active plan, role, usage, remaining slots, and resource limits. |
Deploy
Section titled “Deploy”deploy_files
Section titled “deploy_files”Upload and deploy a project in one call.
Required: name, files
Optional: variables, secrets, idempotency_key
redeploy_files
Section titled “redeploy_files”Replace a ready app from local files while keeping its URL, environment, and data.
Required: app_id, files
deploy_repository
Section titled “deploy_repository”Deploy a public GitHub repository with a root Dockerfile.
Required: name, repository
Optional: ref, variables, secrets, idempotency_key
redeploy_repository
Section titled “redeploy_repository”Replace a ready app from a public GitHub repository.
Required: app_id, repository
Optional: ref
Larger uploads
Section titled “Larger uploads”begin_uploadcreates an empty upload.upload_fileadds one UTF-8 or base64 file.deploy_uploaddeploys the completed upload.
Inspect and manage
Section titled “Inspect and manage”| Tool | Purpose |
|---|---|
list_apps |
List apps and their status. |
get_app |
Get one app and its deployment status. |
get_deployment_logs |
Get recent deployment and lifecycle events. |
start_app |
Start a stopped app. |
stop_app |
Stop a running app without deleting its data. |
destroy_app |
Stop an app and retire its data. |
Environment
Section titled “Environment”| Tool | Purpose |
|---|---|
get_environment |
Return variables and redacted secret names. |
set_variables |
Replace non-secret variables. Restart to apply them. |
set_secrets |
Add or replace write-only secrets. Restart to apply them. |
Automations
Section titled “Automations”| Tool | Purpose |
|---|---|
deploy_automation_files |
Deploy a one-shot automation with one to ten triggers. |
run_automation |
Queue one manual automation run. |
Destructive tools: stop_app and destroy_app are marked destructive by the MCP server. Your coding agent may ask for approval before calling them.