Developer · Remote MCP server
Qovery MCP Server
Deploy apps and manage Kubernetes on AWS, GCP, Azure, and On-Premise with natural language.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.qovery/mcp-server- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-02-08
- Updated
- 2026-02-08
- Publisher
- com.qovery
- Namespace
- Namespace verified by the MCP Registry via the domain qovery.com · how
- Listed under
- AWS MCP servers, Azure MCP servers, Kubernetes MCP servers, Google Cloud MCP servers
- Website
- www.qovery.com/docs/copilot/mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp-api-ai.qovery.com/mcp?token={qovery_token} | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect Qovery MCP Server
Qovery MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://mcp-api-ai.qovery.com/mcp?token={qovery_token}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {qovery_token}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| QlaneAI QA that runs your app in a browser on every pull request: projects, test targets, test cases. | Remote · HTTPLive check: sign-in required |
| qmailing.comAI agents read & send email, manage mailboxes, domains and webhooks via the QMailing API. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Qnexus MCPMCP server for Quantinuum Nexus, wrapping the qnexus SDK. Not affiliated with Quantinuum. | Local · stdio |
| Qodercli MCPMCP server mode for Qoder CLI - delegate coding tasks to local Qoder agents from any MCP client. | Local · stdio |
| QR for AgentDynamic QR codes for AI agents - custom styling, scan tracking, webhooks. | Local · stdio |
| qrvoteQR-code contests, surveys, quizzes and scavenger hunts: read results, manage your own. | Remote · HTTPLive check: ✓ handshake |
| Qsp ClientQSP - relay MCP tools to any OpenAI-compatible local LLM (llama.cpp, Ollama, vLLM) | Local · stdio |
| QTM4JMCP server for QMetry Test Management for Jira (QTM4J) Open API. | Local · stdio |