puterMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate an image from a text prompt using Puter's free AI image generation. Supports 30+ models including GPT Image, DALL-E 2/3, Gemini Nano Banana, Flux.1, Stable Diffusion, and more. Falls back across models on quota or availability errors. Returns the image inline as base64 content for direct rendering in MCP clients. No API keys required — uses your Puter account. |
| list_modelsA | List all available image generation models supported by puterMCP via Puter. |
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 2 tools
The two tools have clearly distinct purposes: one generates images, the other lists models. There is no overlap or confusion.
Both tools follow a consistent verb_noun pattern in snake_case (generate_image, list_models), which is predictable and clear.
With only two tools for an image generation service that supports 30+ models and includes fallback logic, the tool surface feels too sparse. Typically one would expect additional tools for quota management, image retrieval, or cancellation.
The server lacks obvious operations such as checking user quota, retrieving previously generated images, or managing model preferences. The generate_image tool's fallback behavior suggests quota tracking, but no tool exposes that information, creating a gap.