Activate a Project MCP Gateway

post

/ic/api/integration/v1/projects/{projectId}/mcp/gateways/{id}/activate

Activates an MCP gateway in a project and returns the resulting gateway resource.

Request

Path Parameters
Query Parameters
  • This is the name of the service instance. You can get this value from the About page where it is specified in the Service instance field.
    Example:
    example-instance
Supported Media Types
Request Body - application/json; charset=utf-8 ()
Root Schema : schema
Type: object
Optional tracing and authorization settings used when activating an MCP gateway.
Show Source
Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : MCPGatewayRs
Type: object
Project MCP gateway configuration, lifecycle state, resource references, and execution plan.
Show Source
Nested Schema : businessPolicies
Type: array
Policy references. On update, omitted or null retains existing policies and an empty array clears this category. A configured gateway must retain at least one security or business policy.
Show Source
Nested Schema : executionPlan
Policy execution order for gateway requests and responses.
Match All
Policy execution order for gateway requests and responses.
Show Source
Nested Schema : mcpServers
Type: array
MCP server references used by the gateway.
Show Source
Nested Schema : securityPolicies
Type: array
Policy references. On update, omitted or null retains existing policies and an empty array clears this category. A configured gateway must retain at least one security or business policy.
Show Source
Nested Schema : ResourceRefRs
Type: object
Reference to an MCP server or policy used by a gateway.
Show Source
  • Minimum Length: 1
    Pattern: [^\u0000-\u0020]
    Nonblank code of the referenced MCP server or policy. The referenced resource must exist in the current project.
  • Referenced resource version. Omitted or blank values default to 01.00.0000; other nonblank versions are rejected.
Nested Schema : ExecutionPlanRs
Type: object
Ordered policy steps applied to gateway requests and responses.
Show Source
  • request
    Ordered policy execution steps for requests. If steps are supplied, their step numbers must start at 1 and be sequential. An omitted or empty list is allowed.
  • response
    Ordered policy execution steps for responses. If steps are supplied, their step numbers must start at 1 and be sequential. An omitted or empty list is allowed.
Nested Schema : request
Type: array
Ordered policy execution steps for requests. If steps are supplied, their step numbers must start at 1 and be sequential. An omitted or empty list is allowed.
Show Source
Nested Schema : response
Type: array
Ordered policy execution steps for responses. If steps are supplied, their step numbers must start at 1 and be sequential. An omitted or empty list is allowed.
Show Source
Nested Schema : ExecutionStepRs
Type: object
One security or business policy step in the gateway execution plan.
Show Source
  • Pattern: ^[\u0000-\u0020]*([Ss][Ee][Cc][Uu][Rr][Ii][Tt][Yy]_[Pp][Oo][Ll][Ii][Cc][Yy]|[Bb][Uu][Ss][Ii][Nn][Ee][Ss][Ss]_[Pp][Oo][Ll][Ii][Cc][Yy])[\u0000-\u0020]*$
    Policy kind: SECURITY_POLICY or BUSINESS_POLICY. Requests are trimmed and normalized to uppercase by the service; conventional mixed-case forms are accepted.
  • Minimum Length: 1
    Pattern: [^\u0000-\u0020]
    Nonblank code of the policy executed in this step. The code and normalized version must match a declared securityPolicies or businessPolicies reference, according to kind.
  • Version of the policy executed in this step. Omitted or blank values default to 01.00.0000; other nonblank versions are rejected.
  • Minimum Value: 1
    Positive execution step number. Each request or response step list must be sequential, starting at 1; sequence order is validated by the service.

400 Response

Malformed parameters

401 Response

Unauthorized or insufficient design-time permissions

404 Response

Project or resource not found, or the MCP feature is not available

412 Response

Precondition failed

500 Response

Server error
Back to Top

Examples

The following example shows how to activate an MCP gateway in a project and return the resulting gateway resource by submitting a POST request on the REST resource using cURL. For more information about cURL, see Use cURL. For more information about endpoint URL structure, see Send Requests.

Example: Activate a Project MCP Gateway

curl --request POST --include \
  --url "${BASE_URL}/ic/api/integration/v1/projects/${PROJECT_ID}/mcp/gateways/${GATEWAY_ID}/activate?integrationInstance=${INTEGRATION_INSTANCE}" \
  --header "Authorization: Bearer ${ACCESS_TOKEN}" \
  --header "Accept: application/json" \
  --header "Content-Type: application/json; charset=utf-8" \
  --data-raw '{
  "traceLevel": "PRODUCTION",
  "authorizationMode": "OIC"
}'
Back to Top