RendrKit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENDRKIT_API_KEY | Yes | Your RendrKit API key (starts with rk_) | |
| RENDRKIT_BASE_URL | No | API base URL (for self-hosted or development) | https://api.rendrkit.dev |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate a marketing image. Two modes: (1) Prompt mode — provide a text prompt and AI picks the template. (2) Direct mode (recommended) — provide templateId + slots for precise control. Use list_templates to see available templates. |
| get_imageA | Get details of a previously generated image |
| list_brand_kitsA | List all saved brand kits. Brand kits contain colors, fonts, and logos for consistent image generation. |
| get_usageA | Check current usage statistics including images generated this month and plan limits |
| list_templatesA | List all available image templates with their slot definitions. Use this to discover which templates exist and what slots they accept for direct rendering with generate_image. |
| upload_imageA | Upload an image to get a hosted URL that can be used as photo_url in templates. Provide either a public URL to re-upload or base64-encoded image data. |
| batch_renderA | Generate multiple images from the same template with different data. Perfect for e-commerce catalogs, certificates, social media series. Up to 20 items per batch. |
| clone_templateA | Clone a template with custom default values. Creates a reusable preset (e.g., your brand's product card template). Use the returned ut_ID for future generations. |
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 8 tools
Each tool has a clearly distinct purpose: batch rendering, cloning templates, generating images, fetching details, usage, listing brand kits, listing templates, and uploading images. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using lowercase and underscores, making them predictable and easy to understand.
With 8 tools, the server covers the essential operations for image generation (listing templates, generating, batching, fetching, usage, uploading, cloning templates, and listing brand kits) without being bloated or too sparse.
The core workflow of generating images from templates is well-covered, but the lack of tools to create or update brand kits and delete images are noticeable gaps that limit the agent's ability to manage assets fully.