Create an approved stdio MCP template
POST
/api/companies/{companyId}/tools/stdio-templatesPersonal API keyConsole session
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
templateIdstringRequired
1–160 characterspattern: ^[a-z0-9][a-z0-9._:-]*$namestringRequired
1–160 charactersdescriptionstring | nullOptional
at most 4000 characterscommandstringRequired
1–2000 charactersargsarray<string>Optional
each at most 2000 charactersenvKeysarray<string>Optional
each at most 160 characterstoolsarray<object>Optional
tools[].namestringRequired
1–240 characterstools[].titlestring | nullOptional
at most 240 characterstools[].descriptionstring | nullOptional
at most 8000 characterstools[].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.