Templated MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEMPLATED_API_KEY | Yes | Your Templated API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_renderA | Create a render (image, video, or PDF) from a template. This is the main tool for generating content. Supports formats: jpg, png, webp, pdf, mp4. |
| get_renderA | Retrieve a specific render by its ID to get the status and file URL |
| list_rendersC | List all renders in the account |
| delete_renderC | Delete a specific render |
| merge_rendersB | Merge multiple PDF renders into a single PDF document |
| list_templatesA | List all templates in the account. Use this to find template IDs for rendering. |
| get_templateB | Retrieve a specific template by ID |
| get_template_layersA | Get all layers of a template. Use this to understand what layers can be modified when creating a render. |
| get_template_pagesB | Get all pages of a multi-page template |
| create_templateA | Create a new template programmatically with layers. IMPORTANT: Each layer must have a 'layer' field (unique identifier/name), not 'name'. Valid layer types are: 'text', 'image', 'shape', 'rating'. Use 'shape' for rectangles, circles, and other shapes - shapes require an 'html' field with SVG content. For a multi-page or multi-size template (several sizes in one template), pass 'pages' instead of 'layers': each page carries its own width/height and its layers as an object keyed by layer name. |
| update_templateA | Update an existing template. IMPORTANT: Each layer must have a 'layer' field (unique identifier), not 'name'. Valid types: 'text', 'image', 'shape', 'rating'. For multi-page templates use 'pages': a page name that does not exist yet is ADDED to the template, an existing one has its layers merged (or replaced with replaceLayers). To change page sizes on a multi-size template set width/height per page inside 'pages'; top-level width/height are rejected there because they would resize every page. |
| clone_templateC | Create a copy of an existing template |
| delete_templateC | Delete a template |
| list_template_rendersB | List all renders created from a specific template |
| list_foldersB | List all folders in the account |
| create_folderB | Create a new folder to organize templates |
| update_folderC | Update a folder's name |
| delete_folderC | Delete a folder |
| list_uploadsB | List all uploaded assets (images, videos) |
| create_uploadC | Upload a file from a URL |
| delete_uploadC | Delete an uploaded asset |
| list_fontsB | List all custom fonts uploaded to the account |
| upload_fontB | Upload a custom font from a URL |
| delete_fontB | Delete a custom font |
| get_accountA | Get the connected account's render usage for the current period (renders used and renders included) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Each tool targets a distinct resource+action (renders, templates, folders, uploads, fonts, account). No two tools appear to do the same thing; create_render vs merge_renders vs list_template_renders are clearly separated. Minor potential overlap between list_renders and list_template_renders, but descriptions distinguish them.
Mostly consistent verb_noun snake_case (create_render, list_templates, delete_folder). Minor deviations: create_upload vs upload_font use different verbs for upload actions, and pluralization varies (get_render vs list_renders). Still highly readable and predictable.
25 tools is heavy for a single MCP server; the surface spans six sub-domains. While each tool is distinct, the set could likely be consolidated (e.g., folder CRUD, font CRUD). At the 25-tool threshold, it is borderline rather than well-scoped.
Core lifecycle for templates (create/get/update/delete/clone) and renders (create/get/list/delete/merge) is covered. Gaps exist for uploads and fonts (no get/update, only list/create/delete) and folders lack a get tool, but agents can work around via list calls.