Handle named MCP gateway protocol requests

POST/api/tool-gateway/gateways/{gatewayId}/mcp
No API key
Veyra Docs TeamUpdated Version 3 · History

Handle named MCP gateway protocol requests.

Authorization

No API key is needed: the token or id in the path, or the request's own signature, authenticates the call. How keys work.

Path parameters

gatewayIdstringRequiredThe gateway's id.

Request body

application/json · required

Any JSON object.

Responses

200SuccessThe request worked; the body holds the result.
202SuccessAccepted; the work continues in the background.
400Bad requestThe request is malformed or failed validation. details names each field that failed.
401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.
429SuccessToo many requests; wait for Retry-After seconds.

Errors return {"error": "..."}, often with a code and details. See errors and limits.

MCP gateway