Create an approved stdio MCP template

POST/api/companies/{companyId}/tools/stdio-templates
Personal API keyConsole session
Veyra Docs TeamUpdated Version 3 · History

Create an approved stdio MCP template.

Authorization

Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.

Path parameters

companyIdstringRequiredThe organization's id.

Request body

application/json · required

templateIdstringRequired1–160 characterspattern: ^[a-z0-9][a-z0-9._:-]*$
namestringRequired1–160 characters
descriptionstring | nullOptionalat most 4000 characters
commandstringRequired1–2000 characters
argsarray<string>Optionaleach at most 2000 characters
envKeysarray<string>Optionaleach at most 160 characters
toolsarray<object>Optional
tools[].namestringRequired1–240 characters
tools[].titlestring | nullOptionalat most 240 characters
tools[].descriptionstring | nullOptionalat most 8000 characters
tools[].inputSchemaobject | nullOptional
tools[].annotationsobject | nullOptional

Responses

201SuccessCreated; the body holds the new resource.
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.
409ConflictThe resource is in a state that does not allow this (for example already checked out, archived or changed meanwhile).

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

Connectors