AuraImage MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AURA_SECRET_KEY | No | Your project's Secret Key for AuraImage, needed by the migrate_assets tool. | |
| GOOGLE_GENERATIVE_AI_API_KEY | No | Your Google AI API key, needed by the generate_alt tool. |
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 |
|---|---|
| audit_lcpA | Scan a project directory for unoptimized images and estimate LCP savings. |
| migrate_assetsA | Upload local image assets to AuraImage. Use dryRun=true to preview. |
| generate_altB | Generate accessible alt text for an image URL using vision AI. |
| generate_responsive_tagB | Generate a element with AVIF and WebP srcsets for an AuraImage URL. |
| smart_crop_previewC | Return crop variant URLs for a given image at specified dimensions. |
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 5 tools
Each tool has a clearly distinct purpose: auditing, migrating, generating alt text, generating responsive tags, and previewing crops. There is no overlap or ambiguity between them.
Most tools follow a verb_noun pattern (audit_lcp, migrate_assets, generate_alt, generate_responsive_tag), but 'smart_crop_preview' breaks the pattern with an adjective-noun compound. Overall the naming remains clear and predictable.
With 5 tools, the set is well-scoped and each earns its place for an image optimization workflow. It is neither too thin nor overly heavy.
The core workflow (audit, migrate, generate alt text, generate responsive tags, preview crops) is well covered. Minor gaps like asset deletion or direct URL transformation exist, but the major workflow is complete.