2,500+ MCP servers ready to use
Vinkius

Coolify MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Coolify and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "coolify": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Coolify
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Coolify MCP Server

Connect your Coolify instance to any AI agent and take full control of your self-hosting and private cloud workflows through natural conversation.

GitHub Copilot Agent mode brings Coolify data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Server Monitoring — List self-hosted nodes and retrieve intricate networking parameters including IP properties and Docker swarm statuses
  • Application Management — List all managed frontend/backend apps and fetch elaborate internal topology metrics like mapped GitHub branches and Traefik proxy paths
  • Lifecycle Control — Start, stop, and restart applications natively, allowing you to recycle container states and apply configuration updates instantly
  • Deployment Automation — Trigger raw build pipelines to fetch the latest commits, rebuild Nixpacks images, and roll out updated Docker versions
  • Database Oversight — Manage PostgreSQL, MySQL, and Redis configurations and extrapolate internal connection strings for secure application linking
  • Resource Navigation — asociating Project repositories to explicit application UUIDs required for downstream mutations and operational auditing

The Coolify MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Coolify to VS Code Copilot via MCP

Follow these steps to integrate the Coolify MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Coolify

Ask Copilot: "Using Coolify, help me...". 10 tools available

Why Use VS Code Copilot with the Coolify MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Coolify through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Coolify + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Coolify MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Coolify MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Coolify to VS Code Copilot via MCP:

01

get_application

Examines mapped GitHub branches, automatic rollout toggles (push to deploy), and assigned Traefik reverse proxy FQDN paths. Fetch elaborate internal topology metrics for a given Application

02

get_database

Highly required when linking newly provisioned Web Apps to Backend Datastores. Extrapolate internal configuration arrays for a Database

03

get_server

Verifies IP properties, SSH connection validation statuses, and Docker executing ports resolving across the cluster. Get configuration schema mapped to a specific Coolify Server Node

04

list_applications

Generates the crucial map associating Project repositories to explicit application UUIDs required for downstream mutations (like restarting and stopping). List all frontend/backend Applications actively managed by Coolify

05

list_databases

Isolates database bounding boxes mapping to applications so you can properly retrieve Connection Strings and backup cadence timelines. List managed PostgreSQL, MySQL, and Redis configurations

06

list_servers

Used to identify the raw physical endpoints running Docker swarms that host subsequent applications. List all self-hosted Server Nodes attached to Coolify

07

restart_application

Ensures updated config `.env` variables injected via Coolify take effect immediately in runtime RAM. Bounce a Coolify application recycling its container states

08

start_application

Spin up containers mapped to a suspended Application UUID

09

stop_application

Used precisely for pausing billing or restricting web perimeter ingress during a cyber incident directly via the Coolify dashboard API. Halt execution algorithms suspending the mapped Application

10

trigger_deployment

Performs `git fetch`, rebuilds Nixpacks images, caches dependencies, and rolls the updated Docker image out directly over the previous active application version. Trigger a raw build pipeline fetching the latest Git commit

Example Prompts for Coolify in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Coolify immediately.

01

"List all active servers in my Coolify instance"

02

"Trigger a deployment for application 'backend-api'"

03

"What is the connection string for database 'user-db-prod'?"

Troubleshooting Coolify MCP Server with VS Code Copilot

Common issues when connecting Coolify to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Coolify + VS Code Copilot FAQ

Common questions about integrating Coolify MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Coolify to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.