2,500+ MCP servers ready to use
Vinkius

Qovery MCP Server for Cursor 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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 Qovery 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": {
    "qovery": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Qovery
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 Qovery MCP Server

Connect your Qovery infrastructure to any AI agent and bring DevOps execution directly into your coding environment.

Cursor's Agent mode turns Qovery into an in-editor superpower. Ask Cursor to generate code using live data from Qovery and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

  • Map your Infrastructure — Traverse effortlessly through your Qovery Organizations, Projects, and Environments to build a complete mental map of your deployments
  • Monitor Applications — Inspect individual microservices, check active replica counts, verify auto-deploy settings, and get real-time status updates without switching contexts to the Qovery dashboard
  • Take Action via Chat — Trigger zero-downtime rolling restarts to cycle Kubernetes pods and refresh environment variables directly inside Claude or Cursor
  • Targeted Deployments — Issue a fast-track deploy of a specific Git commit SHA for hotfixes or localized feature testing, all handled friction-free by the LLM

The Qovery MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor 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 Qovery to Cursor via MCP

Follow these steps to integrate the Qovery MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using Qovery

Open Agent mode in chat and ask: "Using Qovery, help me...". 10 tools available

Why Use Cursor with the Qovery MCP Server

Cursor AI Code Editor provides unique advantages when paired with Qovery through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Qovery + Cursor Use Cases

Practical scenarios where Cursor combined with the Qovery MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Qovery MCP Tools for Cursor (10)

These 10 tools become available when you connect Qovery to Cursor via MCP:

01

deploy_application

Triggers an immediate deployment of a specific Git commit SHA

02

get_application

Retrieves details for a specific Qovery application

03

get_environment

Retrieves details for a specific Qovery environment

04

get_organization

Retrieves details for a specific Qovery organization

05

get_project

Retrieves details for a specific Qovery project

06

list_applications

Lists all applications running in a specific environment

07

list_environments

Lists all environments (Production, Staging, etc.) in a project

08

list_organizations

Lists all Qovery organizations associated with the token

09

list_projects

Lists all projects within a Qovery organization

10

restart_application

Performs a zero-downtime rolling restart of a Qovery application

Example Prompts for Qovery in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Qovery immediately.

01

"List all Qovery projects and tell me how many there are."

02

"Check the health and limits of the application in my staging environment."

03

"Deploy commit 7a8f9b2 to the backend application immediately."

Troubleshooting Qovery MCP Server with Cursor

Common issues when connecting Qovery to Cursor through the Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Qovery + Cursor FAQ

Common questions about integrating Qovery MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect Qovery to Cursor

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