DingCard — Claude Code MCP server: features and installation
The DingCard MCP server for Claude Code creates cards, posters and slide decks from templates. It checks layouts, exports files and opens designs in an editor.
MIT ★ 16 updated 2026-10-31
claude mcp add --env DINGCARD_FONTS_URL=<DINGCARD_FONTS_URL> --env DINGCARD_CHROME_PATH=<DINGCARD_CHROME_PATH> --env DINGCARD_SERVER_URL=<DINGCARD_SERVER_URL> --env DINGCARD_SERVER_TOKEN=<DINGCARD_SERVER_TOKEN> --transport stdio mcp -- npx -y dingcard-mcpWhat DingCard does
DingCard builds editable cards, posters and slide decks from templates, supplied content or an outline. Its tools can inspect and modify a document, show available assets, and open the result in a browser editor.
Layout checks flag issues such as overlapping text and low contrast. Documents can be exported as PNG, JPG, PDF or a long image. The server keeps its documents between tool calls, and images can be supplied by local file path. Node.js 22 or newer and an installed Chrome browser are required. Web fonts come from Google Fonts; set DINGCARD_FONTS_URL to use another font source if needed.
Sharing documents requires a DingCard server address and a token with images and shares permissions, or DingCard account credentials. The Claude Code setup command is included below.
What it helps with
- create a poster or slide deck from a template
- find overlapping text and low contrast in a layout
- export a document as PNG, JPG or PDF
- open a design in the browser editor
Example prompts for the agent
- Make a poster from a template and check its text layout.
- Turn this outline into slides and export them as a PDF.
- Open the finished card in the DingCard editor.
How to install DingCard
Platform CLI
claude mcp add --env DINGCARD_FONTS_URL=<DINGCARD_FONTS_URL> --env DINGCARD_CHROME_PATH=<DINGCARD_CHROME_PATH> --env DINGCARD_SERVER_URL=<DINGCARD_SERVER_URL> --env DINGCARD_SERVER_TOKEN=<DINGCARD_SERVER_TOKEN> --transport stdio mcp -- npx -y dingcard-mcpReplace <…> with your own values
Platform CLI
codex mcp add mcp --env DINGCARD_FONTS_URL=<DINGCARD_FONTS_URL> --env DINGCARD_CHROME_PATH=<DINGCARD_CHROME_PATH> --env DINGCARD_SERVER_URL=<DINGCARD_SERVER_URL> --env DINGCARD_SERVER_TOKEN=<DINGCARD_SERVER_TOKEN> -- npx -y dingcard-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"dingcard-mcp"
],
"env": {
"DINGCARD_FONTS_URL": "<DINGCARD_FONTS_URL>",
"DINGCARD_CHROME_PATH": "<DINGCARD_CHROME_PATH>",
"DINGCARD_SERVER_URL": "<DINGCARD_SERVER_URL>",
"DINGCARD_SERVER_TOKEN": "<DINGCARD_SERVER_TOKEN>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"dingcard-mcp"
],
"env": {
"DINGCARD_FONTS_URL": "<DINGCARD_FONTS_URL>",
"DINGCARD_CHROME_PATH": "<DINGCARD_CHROME_PATH>",
"DINGCARD_SERVER_URL": "<DINGCARD_SERVER_URL>",
"DINGCARD_SERVER_TOKEN": "<DINGCARD_SERVER_TOKEN>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e DINGCARD_FONTS_URL=<DINGCARD_FONTS_URL> -e DINGCARD_CHROME_PATH=<DINGCARD_CHROME_PATH> -e DINGCARD_SERVER_URL=<DINGCARD_SERVER_URL> -e DINGCARD_SERVER_TOKEN=<DINGCARD_SERVER_TOKEN> mcp npx -y dingcard-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about DingCard
How do I install DingCard in Claude Code?
Run claude mcp add dingcard -e DINGCARD_SERVER_TOKEN=<DINGCARD_SERVER_TOKEN> -- npx -y dingcard-mcp. The server also requires Node.js 22 or newer and an installed Chrome browser.
What does DingCard do?
It creates and edits cards, posters and slide decks, checks their layouts, and exports them as images or PDF files. Designs can be opened in a browser editor.
What does DingCard need to run?
It requires Node.js 22 or newer and an installed Chrome browser. Sharing documents also requires a DingCard server address and a token with images and shares permissions, or a username and password.