Template Tools

Templates deploy preconfigured service stacks such as PostgreSQL, Redis, MySQL, MongoDB, Directus, observability stacks, and CI workers. A template deployment creates normal Ink services with generated credentials, endpoints, outputs, and persistent volumes when the template defines them.

template_list

List available templates, optionally filtered by search text.

Parameter	Type	Required	Default	Description
`search`	string	no	—	Search by name, slug, tag, or description

Returns: template slugs, names, descriptions, tags, author, variables, service definitions, outputs, docs URL, repo URL, and readme.

template_deploy

Deploy a template into a project.

Parameter	Type	Required	Default	Description
`workspace`	string	no	`default`	Workspace slug
`template`	string	yes	—	Template slug, such as `postgres`, `redis`, `mysql`, or `mongodb`
`name`	string	yes	—	Base name for deployed services
`project`	string	no	`default`	Project slug
`region`	string	no	`us-east-1`	Deployment region
`variables`	array	no	—	Values as `{ key, value }` pairs

Tool Call

template_deploy(
  "template": "postgres",
  "name": "my-db",
  "variables": {
    "0": "[object Object]",
    "1": "[object Object]"
  }
)

Returns: template_instance_id, project_id, deployed services, endpoints, and outputs such as connection strings or generated credentials.

template_instance_get

Get a deployed template instance, including current service status and decrypted outputs.

Parameter	Type	Required	Default	Description
`id`	string	yes	—	Template instance ID from `template_deploy`

template_instance_list

List deployed template instances for a project. Sensitive outputs are masked in list responses.

Parameter	Type	Required	Default	Description
`workspace`	string	no	`default`	Workspace slug
`project`	string	no	`default`	Project slug

Database template notes

Database templates run as Ink services with persistent volumes. They are useful when the agent needs a database, cache, queue, or supporting service without hand-writing Docker configuration.

They are not a separate managed-database product: do not assume automatic backups, failover, or managed upgrades unless a specific template documents those capabilities.