Skip to main content
Glama
beznazwiska

@codetoimage/mcp-server

by beznazwiska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODETOIMAGE_API_KEYYesRequired. Get one at https://codetoimage.app/dashboard/keys
CODETOIMAGE_API_URLNoAPI base URL (override for dev/proxy)https://api.codetoimage.app

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
render_html_to_imageA

Render HTML (and optional CSS) into a PNG/JPEG/WebP image using codetoimage.app. Instead of raw HTML you can pass template_id (a template saved in the dashboard) plus variables to fill its {{placeholders}}, and preset for named platform sizes (og, instagram-story, ...). Returns the image inline so the conversation can display it directly. Use this when you need to see or hand back a finished image (cards, OG previews, charts, badges). If the caller needs a URL to embed elsewhere (Instagram Graph API, OpenGraph meta, Slack unfurl), use render_html_to_url instead.

render_html_to_urlA

Render HTML (and optional CSS) to an image and return a temporary hosted URL (instead of inline bytes). Supports the same template_id + variables + preset inputs as render_html_to_image. Use this when the caller needs to reference the image elsewhere – Instagram Graph API, OpenGraph meta tags, Slack unfurls, embedding in docs/posts. URL is valid for 24 hours.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one returns inline image data, the other a temporary URL. Their descriptions explicitly contrast when to use each, leaving no ambiguity.

Naming Consistency5/5

Both tool names follow the exact pattern 'render_html_to_X', where X is the output type (image vs url). The naming is perfectly consistent and descriptive.

Tool Count5/5

With only two tools, the server is tightly scoped to its single purpose of rendering HTML to images. Each tool covers a necessary output format, so the count is ideal.

Completeness5/5

For a server focused solely on rendering HTML to images, offering both inline and URL outputs covers all common use cases. There are no missing features or dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources