Skip to main content

TriggerProjectMcp

POST 
/admin/v1/customers/:customer_id/projects/:project_id/mcp:trigger

TriggerProjectMcp (re)materializes the per-Project-Gateway MCP config for every gateway the (customer_id, project_id) is attached to. The dashboard MCP profile mutation path calls this after a profile create/update/delete so a freshly-created profile enters its project gateways' MCP_PROFILE config; without it the per-gateway config-gen never re-runs and /mcp/{profile} 404s on a strict-isolation gateway DP. Best-effort + dormant when the project has no gateways.

Request​

Responses​

Success