Replicate Designer MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPLICATE_API_TOKEN | Yes | Your Replicate API token used to access Replicate's API and run models. |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageC | Generates an image using Replicate's Flux 1.1 Pro model |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'generate_image' has a clearly distinct and singular purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'generate_image' follows a clear verb_noun pattern.
A single tool is too few for a server named 'Replicate Designer MCP', which suggests a broader scope related to design or image generation. This minimal set feels thin and incomplete for the implied domain.
The tool surface is severely incomplete for a design-oriented server. It only offers image generation, with no tools for editing, transforming, analyzing, or managing images, creating significant gaps that will limit agent functionality.