napkin-ai-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAPKIN_API_KEY | Yes | Napkin AI API key | |
| NAPKIN_API_BASE_URL | No | Custom API base URL | |
| NAPKIN_STORAGE_TYPE | No | Storage type: local, s3, google-drive, slack, notion, telegram, discord | |
| NAPKIN_MAX_WAIT_TIME | No | Max wait time in ms (default: 300000) | |
| NAPKIN_DEFAULT_FORMAT | No | Default format: svg, png, or ppt (default: svg) | |
| NAPKIN_DEFAULT_LANGUAGE | No | Default BCP 47 language tag (default: en-GB) | |
| NAPKIN_POLLING_INTERVAL | No | Polling interval in ms (default: 2000) | |
| NAPKIN_DEFAULT_COLOR_MODE | No | Default color mode: light, dark, or both (default: light) | |
| NAPKIN_DEFAULT_ORIENTATION | No | Default orientation: auto, horizontal, vertical, or square (default: auto) |
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_visualB | Submit a visual generation request to Napkin AI. Returns a request ID for tracking. Use check_status to poll for completion. |
| check_statusA | Check the status of a visual generation request. Returns progress information and file details when completed. |
| download_visualA | Download a generated visual file as base64-encoded data. Use the URL from check_status response's generated_files array. |
| generate_and_waitA | Generate a visual and wait for completion. Combines generate_visual and polling check_status into a single operation. |
| generate_and_saveA | Generate a visual, wait for completion, and save to configured storage. Requires storage to be configured in server settings. |
| list_stylesB | Get information about available visual styles. Note: For the full list, visit https://api.napkin.ai/docs/styles/index.html |
| verify_api_keyA | Verify that the configured Napkin AI API key is valid. Use this to test your setup before generating visuals. |
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 7 tools
Most tools have distinct purposes, but generate_visual, generate_and_wait, and generate_and_save all trigger visual generation with different behaviors, which could cause confusion. Description clarifies the differences though, and the other tools (check_status, download_visual, list_styles, verify_api_key) are clearly separate.
All tool names follow a consistent snake_case verb_noun pattern (generate_visual, check_status, download_visual, list_styles, verify_api_key). The compound names generate_and_wait and generate_and_save are also consistent with this style, making the set predictable.
Seven tools is well-scoped for a visual generation service, covering submission, status polling, download, convenience wrappers, style listing, and API key verification. Each tool serves a clear function without unnecessary redundancy.
The core lifecycle of generating, checking, and downloading visuals is fully covered, plus useful extras like styles and API key verification. Minor gaps exist (e.g., no cancel request or delete operation), but these are not essential for the primary use case.