Imaginode vs Templated
A side-by-side look at the Imaginode and Templated MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Imaginode for multimedia process work over a hosted endpoint; choose Templated for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Imaginode when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_models, list_templates, get_template.
Choose Templated when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TEMPLATED_API_KEY. - You want tools like
create_render, get_render, list_renders.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 51/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | TEMPLATED_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | 25 |
| Full listing | View Imaginode | View Templated |
Tools & capabilities
Imaginode tools 6
list_modelsCatalogue of image and video models with prices in credits and billable options.list_templatesThe curated canvas templates: what each produces, its models, the approximate cost of one run.get_templateFull recipe of a template (nodes, models, prompts, wiring, example renders) and the link that opens it in the canvas.generate_imageGenerates an image and waits for the result: the URL is returned directly. Default model: Nano Banana 2.generate_videoStarts a video generation and returns a `request_id` plus the exact cost. Default model: Seedance 2.0.get_generation_statusFollows a generation (`running`, `completed` with output URLs, or `failed` with automatic refund).
Templated tools 25
create_renderRender a Templated template into an image (JPG, PNG or WebP), a PDF or an MP4 video, with new text, images and colors in its layers. Use this when the user wants a finished design from one of their templates, such as a social media post, banner, OG image, certificate or invoice. Templated fills the saved template with the exact values given: this is template rendering, not AI image generation. Pass the template ID and 'layers' keyed by the layer names from get_template_layers; names the template doesn't have are rejected before anything is rendered. Multi-page templates render every page, or only the pages listed in 'pages'. Each output counts toward the account's render usage. Returns the render with its file URL (one render per page for multi-page templates).get_renderGet one render by ID with its status, format, size and file URL. Use this to check whether a render has finished or to find its URL again.list_rendersList the renders in the connected Templated account, newest first, 25 per page by default (max 100). Use this to find a render's ID or file URL, for example to merge PDFs with merge_renders. Returns each render's id, url, status, format, size and template.delete_renderPermanently delete a render from the connected Templated account; it can't be restored. Use this when the user asks to remove a render. Takes the render ID from list_renders and returns a confirmation.merge_rendersMerge several renders into one PDF, in the order given, for example one certificate or invoice per recipient. Image renders become PDF pages. Use this after creating the individual renders. Each merge counts toward the account's render usage. Returns the URL of the merged PDF. With host set to false the PDF itself is returned inline instead, which only works for PDFs up to 100 KB.list_templatesList the templates in the connected Templated account, 25 per page by default (max 100), optionally filtered by name (query), size (width, height) or tags. Use this first to find the template ID for create_render, get_template_layers or update_template. Returns each template's id, name, size, thumbnail, folder, and layer and page counts.get_templateGet one template's details by ID: name, size, background, thumbnail, tags, folder, and layer and page counts. Use this to check a template's size or settings; get_template_layers returns its editable layers.get_template_layersList a template's layers with their names, types and current values (text, image_url, colors, fonts, position and size). Use this before create_render: the layer names are the keys create_render accepts in 'layers'. Covers every page of a multi-page template; get_template_pages groups the layers by page.get_template_pagesList the pages of a multi-page or multi-size template, each with its name, width, height and layers keyed by layer name. Use this to render specific pages with create_render ('pages') or to edit pages with update_template, which accepts the same shape.create_templateCreate a new template in the connected Templated account from layers, for example a social media post, banner, OG image, certificate or invoice. Use this when none of the existing templates fits or the account has no templates yet. Each layer has a unique name in 'layer' and a 'type': text, image, shape or rating. Shape layers draw rectangles, circles and other shapes from SVG content in 'html'. For a multi-page or multi-size template (several sizes in one template), pass 'pages' in place of 'layers'. Returns the new template; its ID can be rendered right away with create_render.update_templateChange an existing template: name, description, size, background, default video duration, layers or pages. Use this to edit a design, resize it, or add sizes to a multi-size template. Layers are matched by their 'layer' name: an existing layer is updated in place and a new name is added. Top-level 'layers' apply to the first page; 'pages' reaches the others. With replaceLayers true, layers missing from the request are deleted. To move a layer, send both x and y (a missing coordinate is set to 0). In 'pages', a page name that doesn't exist yet is added and an existing page has its layers updated. On a multi-size template, set width and height per page inside 'pages'; top-level width and height are rejected there because they would resize every page. Returns the updated template.clone_templateCopy a template, with all its layers and pages, into a new template in the same account. Use this to make a variation without changing the original. Returns the copy, which keeps the original's name unless 'name' is given.- +13 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Imaginode
{
"mcpServers": {
"imaginode": {
"url": "https://imaginode.ai/api/mcp"
}
}
}
Templated
{
"mcpServers": {
"templated": {
"command": "npx",
"args": [
"-y",
"mcp-server-templated"
],
"env": {
"TEMPLATED_API_KEY": "YOUR_TEMPLATED_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Imaginode is categorized under Multimedia Process and uses a remote HTTP/SSE transport. Templated belongs to Multimedia Process and uses a local stdio subprocess. Pick Imaginode for multimedia process work and Templated for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Imaginode has no declared pricing — check the project's own site. Templated has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add imaginode and templated as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Imaginode has a quality signal of 51/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Templated has 63/100 (Good) with 1 views, 0 installs and 3 GitHub stars.