MCP server for Napkin AI visual generation API with multi-storage support
Connect Napkin Ai MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Napkin AI visual generation API with multi-storage support. The napkin ai mcp mcp server is what makes that connection.
An MCP (Model Context Protocol) server for generating infographics and visuals using the Napkin AI API. This server enables AI assistants like Claude to generate professional visuals from text content.
The server ships on npm as napkin-ai-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
generate_visual — Submit a visual generation request (async)check_status — Check the status of a generation requestdownload_visual — Download a generated visual as base64generate_and_wait — Generate and wait for completiongenerate_and_save — Generate and save to configured storagelist_styles — Get information about available stylesverify_api_key — Verify your API key is valid and workingInstallation — The Installation tool exposed by this serverCursor — The Cursor tool exposed by this serverWindsurf — The Windsurf tool exposed by this serverSlack — 1. Go to Slack API and create a new app 2. Under "OAuth & Permissions", add these Bot Token Scopes: - files:write -Notion — 1. Go to Notion Integrations and create a new integration 2. Copy the "Internal Integration Token" (startsConfiguration is passed through the environment: NAPKIN_API_KEY, NAPKIN_STORAGE_TYPE, NAPKIN_STORAGE_LOCAL_DIR, NAPKIN_API_BASE_URL, NAPKIN_STORAGE_S3_REGION, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, NAPKIN_STORAGE_GDRIVE_FOLDER_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Napkin Ai MCP's toolset — generate_visual, check_status, download_visual and 11 more — is a fair guide to whether it matches your workflow. It is maintained by louischancly; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| generate_visual | Submit a visual generation request (async) |
| check_status | Check the status of a generation request |
| download_visual | Download a generated visual as base64 |
| generate_and_wait | Generate and wait for completion |
| generate_and_save | Generate and save to configured storage |
| list_styles | Get information about available styles |
| verify_api_key | Verify your API key is valid and working |
| Installation | The Installation tool exposed by this server. |
| Cursor | The Cursor tool exposed by this server. |
| Windsurf | The Windsurf tool exposed by this server. |
| Slack | 1. Go to [Slack API](https://api.slack.com/apps) and create a new app 2. Under "OAuth & Permissions", add these Bot Token Scopes: - files:write - Upload files - chat:write - Post messages (optional) 3. Install the app to |
| Notion | 1. Go to [Notion Integrations](https://www.notion.so/my-integrations) and create a new integration 2. Copy the "Internal Integration Token" (starts with secret_) 3. Open the target Notion page and click "..." → "Add conn |
| Telegram | The Telegram tool exposed by this server. |
| Discord | 1. Open Discord and go to the channel where you want to receive visuals 2. Click the gear icon (Edit Channel) → Integrations → Webhooks → New Webhook 3. Give it a name and optionally upload an avatar 4. Click "Copy Webho |
{
"mcpServers": {
"napkin-ai": {
"command": "npx",
"args": ["-y", "napkin-ai-mcp"],
"env": {
"NAPKIN_API_KEY": "your-api-key-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NAPKIN_API_KEY | Credential the server authenticates with. | Yes |
| NAPKIN_STORAGE_TYPE | Configuration value read at startup. | Optional |
| NAPKIN_STORAGE_LOCAL_DIR | Filesystem location the server is allowed to use. | Optional |
| NAPKIN_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| NAPKIN_STORAGE_S3_REGION | Configuration value read at startup. | Optional |
| AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
| NAPKIN_STORAGE_GDRIVE_FOLDER_ID | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.