Coolify Creation MCP

Overview Schema Source Related Servers Discussions Admin

create_github_app_application

Creates a private Git repository via a GitHub App using Coolify's API, returning its UUID and authenticated deploy webhook; does not deploy or enable automatic Git deployment.

Instructions

Create one private Git repository through a GitHub App application using Coolify's API. Requires read and write token permissions. Returns UUID and authenticated deploy webhook. Does not deploy. Git automatic deployment is disabled. On uncertain failure inspect inventory before retrying.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_uuid": "<project_uuid>",
      "server_uuid": "<server_uuid>",
      "environment_uuid": "<environment_uuid>",
      "name": "<name>",
      "git_repository": "<git_repository>",
      "git_branch": "<git_branch>",
      "build_pack": "<build_pack>",
      "github_app_uuid": "<github_app_uuid>"
    },
    "name": "create_github_app_application"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`is_spa`	No
`domains`	No
`redirect`	No	both
`is_static`	No
`build_pack`	Yes
`git_branch`	Yes
`server_uuid`	Yes
`project_uuid`	Yes
`build_command`	No
`ports_exposes`	No	80
`start_command`	No
`base_directory`	No	/
`git_repository`	Yes
`github_app_uuid`	Yes
`install_command`	No
`destination_uuid`	No
`environment_uuid`	Yes
`publish_directory`	No
`autogenerate_domain`	No
`dockerfile_location`	No
`health_check_enabled`	No
`docker_compose_domains`	No
`docker_compose_location`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

B3.2/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond annotations by disclosing auth requirements ('read and write token permissions'), return values ('UUID and authenticated deploy webhook'), deployment behavior ('Does not deploy. Git automatic deployment is disabled.'), and failure-handling guidance. This is exactly the kind of operational context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with the core action, followed by auth, return, deployment, and retry notes. No waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Behavioral and safety context is strong, but for a 24-parameter create tool with no output schema and no schema descriptions, the description omits all parameter guidance. An agent still cannot tell what most fields mean or how to choose values like build_pack.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 24 parameters with 0% schema description coverage, so the description must explain them. It says nothing about any parameter (project_uuid, build_pack, domains, etc.), leaving the agent with only property names and enums.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Create) and resource (GitHub App application) and adds 'private Git repository', which differentiates it from create_public_repository_application and create_deploy_key_application. Slightly ambiguous because 'Create one private Git repository' could be read as creating the repo rather than the Coolify application.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a behavioral exclusion ('Does not deploy') and retry advice ('inspect inventory before retrying'), but never names an alternative sibling tool or states when to choose this over plan_github_app_application or create_public_repository_application.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server