Pixara
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | Yes | Get one at openrouter.ai/keys | |
| OPENROUTER_IMAGE_OUTPUT_DIR | No | Where generated images are saved. Defaults to ./pixara-images | ./pixara-images |
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 |
|---|---|
| pixara_generate_imageA | Generate an image from a text prompt using any image model available on OpenRouter. This calls OpenRouter's dedicated Image API (not chat completions) and saves the resulting image(s) to disk, returning the file path(s), model used, and cost. It does NOT edit or use reference images — for image-to-image/editing, use pixara_edit_image instead. Args:
Returns: Markdown summary listing each saved file's path, media type, size in bytes, and the total cost charged by OpenRouter for the request. Examples:
Error Handling:
|
| pixara_edit_imageA | Edit or transform an existing image using a text prompt and one or more reference images, via any image-to-image-capable model on OpenRouter. This calls OpenRouter's Image API with input_references and saves the resulting image(s) to disk. Reference images can be a local file path, a remote URL, or raw base64 — this tool handles reading/encoding local files itself, so you never need to pre-encode anything. Args:
Returns: Markdown summary listing each saved file's path, media type, size in bytes, and the total cost charged by OpenRouter for the request. Examples:
Error Handling:
|
| pixara_list_image_modelsA | List image-generation models available on OpenRouter, with filtering and pagination. This is a read-only, no-cost call (no image is generated). Use it to discover model IDs before calling pixara_generate_image or pixara_edit_image, or to find models with a specific capability. Args:
Returns: For JSON: { total, count, offset, models: [...], has_more, next_offset? } For Markdown: a heading per model with id, description, and supported parameter names. Examples:
|
| pixara_get_model_detailsA | Get per-provider pricing, supported parameters, and passthrough options for one OpenRouter image model. This is a read-only, no-cost call. Use it before pixara_generate_image / pixara_edit_image to confirm exactly which parameters a model/provider supports and what it costs — unsupported parameters are silently ignored or rejected by the API, so checking first avoids wasted/failed calls. Args:
Returns: Per-provider breakdown: pricing (billable type, unit, price, tier/variant), supported parameter descriptors (enum values, numeric ranges, or plain booleans), and any allowed_passthrough_parameters for use with the generate/edit tools' provider_options field. Examples:
Error Handling:
|
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 4 tools
Each tool has a clearly distinct purpose: generation, editing, model details, and model listing. There is no overlap or ambiguity.
All tools follow a consistent 'pixara_verb_noun' snake_case pattern, making them predictable and easy to navigate.
With 4 tools, the server is well-scoped, covering the essential image generation, editing, and model exploration without unnecessary or missing tools.
The tool set covers the full lifecycle: discovery (list and get details), generation (text-to-image), and editing (image-to-image). No obvious gaps for the stated purpose.