Skip to main content
POST
Create a read-only Qovery MCP connector

Authorizations

Authorization
string
header
required

JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Bearer $qovery_token" '

Path Parameters

organizationId
string<uuid>
required

Organization ID

Body

application/json
name
string
default:Qovery MCP
Minimum string length: 1
description
string
default:""

Response

Qovery MCP connector created

id
string<uuid>
required
read-only
created_at
string<date-time>
required
read-only
updated_at
string<date-time>
required
read-only
name
string
required
description
string
required
url
string<uri>
required

HTTPS URL of the remote MCP server

Pattern: ^https://
header_names
string[]
required

Names of the configured HTTP headers. Header values are never returned.

scope
enum<string>
required

ORGANIZATION: usable by every member who can edit an agentic workflow. USER: personal to the member who created it; only that member can attach or edit it.

Available options:
ORGANIZATION,
USER
attachable
boolean
required

Whether the member making this request may attach the connector to an agentic workflow. Computed per caller: an organization admin sees every USER connector but can attach none of them, so a picker must use this rather than scope alone.

owner_user_sub
string | null

Identity of the owning member. Null for an ORGANIZATION connector.

owner_name
string | null

Display name of the owning member. Null for an ORGANIZATION connector.