Artifex MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | API key for OpenAI provider | |
| DEFAULT_IMAGE_MODEL | No | Default model for the provider | gemini-3-pro-image |
| DEFAULT_IMAGE_PROVIDER | No | Default provider to use for image generation (antigravity or openai) | antigravity |
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 images using AI. Supports multiple providers (Antigravity/Gemini, OpenAI DALL-E, etc.). Use 'model' parameter to specify provider:model format. |
| auth_statusA | Check authentication status for an image generation provider |
| auth_loginB | Get instructions for authenticating with an image generation provider |
| auth_logoutA | Log out and delete stored credentials for an image generation provider |
| quota_statusA | Check rate limit and quota status for an image generation provider |
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: generate_image creates images, while auth_status, auth_login, auth_logout handle different aspects of authentication (status, instructions, and logout), and quota_status checks rate limits. There is minimal potential for confusion due to clear descriptions.
Tool names generally follow a pattern: action tools like generate_image and auth_login/logout use verb_noun, while status tools use domain_status (auth_status, quota_status). The only minor inconsistency is that generate_image lacks a domain prefix unlike the auth/quota tools, but the convention is still readable and predictable.
With 5 tools, the server is well-scoped for image generation. It provides essential functionality: generation, authentication management, and quota checking, without unnecessary bloat.
The core image generation workflow is covered, alongside authentication and quota monitoring. A notable gap is the lack of a tool to list available models/providers, which would help users understand the 'model' parameter for generate_image, but it is a minor omission.