Conversions across 221 color spaces, tested against cited sources: CSS strings, gamut, LUTs
DingCard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Make posters, social cards and slide decks from templates, check the layout, render PNG, JPG or PDF
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user dingcard-mcp '--' npx -y dingcard-mcp
# 2 — ask your agent for something these tools do
# get_guide, list_templates, create_document_from_template and 19 more
DingCard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts DingCard as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user dingcard-mcp '--' npx -y dingcard-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take DINGCARD_FONTS_URL (Where to download web fonts instead of https://fonts.googleapis.com, e.g. https://fonts.googleapis.cn), DINGCARD_CHROME_PATH (Path to Chrome when it is not installed in the usual place (used for checks and renders)), DINGCARD_SERVER_URL (A deployed DingCard server, for share links and saved projects), DINGCARD_SERVER_TOKEN (API token for DINGCARD_SERVER_URL (scopes: images and shares; drafts for projects)) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
按主题读一份使用指南:文档怎么写、每个动作怎么发、content / outline / 海报内容怎么填、HTML 怎么写、模板字段和检查项是什么意思、渲染导出有哪些方式。工具说明里只写了做什么;要动手写参数之前,先来这里读对应主题的完整写法。section 给主题 id(不给就列出全部主题 id 和标题):…。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | no | 主题 id,如 "actions";不给就列出全部主题 |
列出叮卡内置模板,按内容和尺寸挑模板、拿 templateId。默认每个模板一张简卡:id、标题、描述、kind、format(尺寸 id)、uses(用途)、styles(风格)。kind 是 deck(一整套,用 create_document_from_content / create_document_from_outline 生成)或 poster(单页,用 create_poster_from_content 生成)。kind / format / q 只取子集(如 kind: "poster"、format: "xhs"、q: "菜单")。挑出两三个候选后用 ids…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | 只列这一类:deck 整套卡片,poster 单页海报 |
| format | string | no | 按页面尺寸 id 筛选(不区分大小写的子串匹配,如 "xhs"、"a4") |
| q | string | no | 关键词,匹配标题、标签、用途、风格和描述(如 "菜单"、"国风") |
| ids | array | no | 要看详情的模板 id;给了就只返回这几个模板的完整信息,不看 kind / format / q |
按模板 id 实例化一份完整的可编辑文档:自由画布模板保存在服务端,返回 documentId(之后传给 inspect_document / apply_actions / check_document / render_document 等)和各页 id、名称;Markdown 模板返回 { source, platformId, themeId, fontFamily, radius, profile, images? } 信封(可用 render_markdown 无头渲染)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| templateId | string | yes | list_templates 返回的模板 id,如 "editorial-freeform" |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
把模板的页面加进一份自由画布文档,和编辑器模板面板里点一页一样:套图模板可以只加某几页(再来一张内页、换个结尾页),单页海报加进来就是新的一页。页面保留模板自己的尺寸和示例文字,之后用 inspect_document 找到图层、apply_actions 改字,check_document 会把没改的示例文字报出来。要直接按内容填好:套图的页用 create_document_from_content 每页的 templateId,海报用 create_poster_from_content 的…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| templateId | string | yes | list_templates 返回的自由画布模板 id |
| pages | array | no | 加模板的第几页,从 1 起(套图是 1 封面、2 内页、3 结尾),可以重复;不给就加全部 |
| afterSlideId | string | no | 加在这一页后面;不给就加在最后 |
| replaceSlideId | string | no | 换掉这一页(比如一张空白页),不能和 afterSlideId 同时给 |
| previews | boolean | no | 是否附上加进来的页的缩略图,默认 true |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
把你写的 HTML/CSS 网页转成在叮卡里能逐个修改的自由画布文档(v…)。适合模板排不出来的版式:直接用网页写法排版,叮卡在浏览器里排好后,把每个色块、文字、图片和 SVG 图形读成形状、文字框、图片和图形节点,位置、字号、颜色、圆角、阴影、渐变等全部照网页来,层叠顺序按 CSS(含 z-index)。返回 documentId、每页 id 和尺寸、notes(哪里没转过来),默认附缩略图。之后 check_document 检查、apply_actions 修改、render_document 出图、open_in_editor 交给人。HTML 怎么写(section…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| html | string | no | 网页源码(可以只写 <style> 和若干 <section>) |
| htmlPath | string | no | 网页文件路径,可替代 html;里面的相对路径按这个文件所在的目录找 |
| width | integer | no | 没写尺寸的页面的宽度,也是 100vw,默认 1080 |
| height | integer | no | 没写尺寸的页面的高度,也是 100vh,默认 1440 |
| previews | boolean | no | 是否附上缩略图,默认 true |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
按结构化内容生成一整套自由画布卡片(v…):封面 + 每个 page 一页 + 可选结尾页,风格沿用所选模板。适合已经整理好标题、正文、要点的内容;每页还能配一种数据元素(chart / table / timeline / progress)。content 的完整写法(页面字段、版式选择、数据元素、生成规则)见 get_guide("deck-content")。生成后建议先 check_document,再 render_document 看缩略图。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| templateId | string | yes | list_templates 返回的自由画布模板 id,如 "editorial-freeform" |
| content | object | yes | — |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
按内容生成一张海报(单页模板:小红书封面、菜单、价目表、证书、九宫格、课程表、各种海报、请柬、贺卡、封面、宣传单、数据盘点、对比表、成长记录等),尺寸跟模板走。模板里的示例文字全部换成内容,没给的连同它的底板、按钮一起删掉。不同模板吃不同的字段(菜单的 details、课程表的 table、数据盘点的 chart、证书的 recipient),content 每个字段的写法和放不下时怎么排见 get_guide("poster-content");summary.moved / unplaced / shrunk 说明文字放到了哪里、缩了多少。给 documentId…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| templateId | string | yes | list_templates 里 kind 为 poster 的模板 id,如 "talk-poster-freeform" |
| content | object | yes | — |
| documentId | string | no | 给了就把海报加成这份文档的一页(就地更新,海报保留自己的尺寸);documentId、document、documentPath 都不给就新建一份文档 |
| afterSlideId | string | no | 加进已有文档时放在这一页后面;不给就加在最后 |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
按 Markdown 大纲生成一整套自由画布卡片(v…):封面 + 每个 "## 小节" 一页 + 可选结尾页,风格沿用所选模板;小节里的 Markdown 表格也变成这一页的表格元素。大纲的完整语法(小节、要点、引文、表格、结尾页)见 get_guide("outline")。生成后建议先 check_document,再 render_document 看缩略图。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outline | string | yes | Markdown 大纲:# 总标题 + 若干 ## 小节(小节下正文行填入该页正文) |
| templateId | string | yes | list_templates 返回的自由画布模板 id,如 "editorial-freeform" |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
查内置素材与样式清单,kind 选一类:icons 内置图标(query 中文或英文搜、ids 按 id 取;example 是可直接 node/insert-children 的完整 path 节点)、decorations 装饰素材(手绘线条、贴纸、标签;category 只看一类,用 add_decorations 放置)、styles 配色与字体组合(document/restyle 一键套用)、text_styles 现成花字(patch 直接作为 node/update-style 的补丁)、collages 拼图版式(example…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | 素材类别;不给返回各类简介 |
| query | string | no | icons / decorations:中文或英文关键词,空格分隔的多个词需同时命中 |
| ids | array | no | icons / decorations:按 id 精确取 |
| category | string | no | decorations:只看一类 |
| pageWidth | number | no | collages:页面宽 px(默认 1080) |
| pageHeight | number | no | collages:页面高 px(默认 1440) |
把装饰素材放到一页上(一次可放多个,按顺序叠放;list_assets 的 decorations 查 id):每项给 decoration、x、y(盒子左上角的页面坐标)、width(不给按页面短边的默认比例),高度按装饰的宽高比算。color(#RRGGBB)换掉装饰本来的主色(手绘线条和贴纸换整体颜色,标签换底色,字色自动取黑或白);text 换标签上的字;rotation 旋转(度);below 填同页一个顶层节点的 id 或图层名,装饰就放在它下面一层(荧光笔、胶带、色块垫在文字下面时用),不给则放在最上层。用 documentId 时就地更新这份文档,返回每个装饰的…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slideId | string | no | 放在哪一页,默认文档当前页(activeSlideId) |
| items | array | yes | 要放的装饰,按顺序叠放 |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
校验文档是否为合法的自由画布 v… 文档(v1–… 自动迁移,src 是本机路径的图片读进来嵌入);合法时保存在服务端并返回 documentId(已有 documentId 的照旧),非法时返回原因:第几页、哪个节点、多了或缺了哪个键,或者该写哪个 documentVersion。 文档速写:{ documentVersion: …, slides: [{ id, name, width(128–4096), height(128–4096), background, nodes, guides? }], activeSlideId };节点 … 选一(…),公共必填键 id,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
检查文档结构:页面摘要(尺寸/背景/节点数)与递归节点树(id、name、type、几何、文本摘要;内置图标标出 icon id,装饰素材标出 decoration id,组成装饰的组也标在组上),以及整套卡片的 style:用到的颜色(按占的面积排序,附 share 和用在 background/fill/text/line/shadow 哪些地方)、字体(texts 用了几段文字、largest 最大字号)和正文字号 bodySize。改文档前先 inspect,拿到节点 id / 路径再发动作。文档怎么写见 dingcard://schema/freeform 资源或…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| documentId | string | no | 创建或修改文档的工具返回的 documentId(推荐:不必来回传整份文档) |
| document | no | 完整的 v…(或 v1–… 旧版)文档 JSON,可替代 documentId | |
| documentPath | string | no | 文档 JSON 文件的路径,可替代 documentId |
对文档应用一串编辑动作(与编辑器 UI 同一归约器,语义完全一致),返回每个动作是否生效(changes)和没生效的原因(reasons,与 changes 一一对应:没改动时是 null,被拒时写清哪个键、哪条规则)。用 documentId 时就地更新这份文档(version 加一),传 document / documentPath 时另存为一份新文档并返回它的 documentId;动作里图片 src…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| actions | array | yes | FreeformAction 数组 |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
检查自由画布文档排出来的样子:在与导出相同的页面里排版后,逐页列出读者会注意到的问题——文字放不下、叠住、被挡住或跑出页面,对比度太低,还留着示例文字,图片没加载出来,图形、二维码、表格、图表画坏了,对齐差几 px,标题和正文拉不开层级,页面上一大片空白,该放图片的色块空着。每条带 kind、page、slideId、node(图层名)、path(apply_actions 用的节点路径)和改法,每种 kind 是什么意思见 get_guide("check")。fix: true 时把放不下的文字缩到能放下的字号、把差几 px 的对齐吸齐,并保存(用 documentId…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fix | boolean | no | 把放不下的文字缩到能放下的字号、把差几 px 的对齐吸齐(改动保存回这份文档,返回 documentId 和 version) |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
把自由画布 v… 文档(v1–… 输入自动迁移)无头渲染为图片或 PDF(与编辑器导出同一管线:网页字体按字符子集嵌入、图片就绪等待、逐页导出),默认逐页 PNG 到 outputDir,另附每页小缩略图供你直接查看效果。长图、九宫格、PDF、JPEG、倍率等输出方式见 get_guide("render-export")。仅支持自由画布文档;文档中的图片 src 必须是浏览器可加载的 URL 或 data URL。文档怎么写见 dingcard://schema/freeform 资源或 get_guide("document-model")。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outputDir | string | yes | 输出目录(不存在会创建) |
| baseName | string | no | 输出文件名前缀,默认 "dingcard" |
| slideIds | array | no | 只渲染这些页(默认全部,按文档页序);长图和 PDF 也只包含这些页 |
| format | string | no | png(默认,保留透明)、jpeg(白底)或 pdf(所有页在一个文件里) |
| scale | no | 像素倍率,默认 1 | |
| quality | number | no | jpeg 和 pdf 的 JPEG 质量,默认 0.92 |
| long | boolean | no | png / jpeg:所有页拼成一张长图,代替逐页文件 |
| grid | boolean | no | png / jpeg:每个正方形页面切成九宫格(九个文件),代替逐页文件 |
| previews | boolean | no | 是否附上缩略图,默认 true |
取回一份文档的完整 JSON:给 path 时写成 JSON 文件(目录不存在会创建)并返回路径,不给时直接返回文档。写成文件的文档可以拖进叮卡「我的项目」,或之后用 documentPath 传回来。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | 写到这个 .json 文件,而不是直接返回文档 |
在叮卡编辑器里打开这份自由画布文档,方便人接着手改:服务端把文档放在本机地址上,在浏览器里打开编辑器的导入链接,编辑器读进来存成一个新项目(不登录也行,存在这台设备的浏览器里)。默认打开服务端自带的编辑器 http://127.0.0.1:5390(DINGCARD_APP_PORT 可改端口,被占用时换一个空闲端口);设了环境变量 DINGCARD_APP_URL 或传 appUrl,就在那个叮卡里打开。open: false 只返回链接(url)不打开浏览器。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | no | 项目名,默认「导入的设计」 |
| appUrl | string | no | 在这个叮卡编辑器里打开,如 http://127.0.0.1:5173 |
| open | boolean | no | 是否打开浏览器,默认 true |
把文档渲染成图片、上传到部署的叮卡服务端,生成一个不用登录就能打开的分享链接:手机扫码或点链接就能看整套卡片、长按存图——「电脑做图、手机发图」的最后一公里。自由画布文档(documentId 或 v… 文档)和 Markdown 卡片信封(source、platformId、themeId 等,与 render_markdown 的 document 相同)都可以。返回 { ok, share: { id, url, expiresAt, imageCount } } 并附上二维码图片,给用户扫即可。expiresInHours 是有效期(小时,1–720,默认…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | no | share 分享(默认)、list 列出已有分享、revoke 撤销一个 |
| id | string | no | revoke:要撤销的分享 id(list 里查) |
| title | string | no | 分享页标题,默认「叮卡分享」 |
| expiresInHours | integer | no | 链接有效期(小时),1–720,默认 24,最长一个月 |
| qr | boolean | no | 是否附上二维码图片,默认 true |
管部署的叮卡服务端账号里存的作品(人在编辑器里存的,AI 接着做):action 选操作——list 列出作品(id、标题、类型 mode、更新时间,query 按标题过滤,这是接着做已有作品的第一步)、open 按 id 载入(自由画布作品返回 documentId,之后 inspect_document / apply_actions / render_document / share_document 都能用;Markdown 作品返回 markdownDocument 信封,交给 render_markdown)、save 把一份文档存回账号(不给 projectId…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | 要做的操作 |
| query | string | no | list:按标题关键词过滤,不区分大小写;不给就列全部 |
| id | string | no | open:要打开的作品 id(list 里查) |
| projectId | string | no | save:要覆盖的服务端作品 id(open 返回的 projectId);不给就存成新作品 |
| title | string | no | save:作品名;不给时按第一页的名称自动起 |
| includeDocument | boolean | no | 同时返回完整文档 JSON(默认只返回 documentId 和 version) |
搜索在线图库的照片,给卡片配图:返回缩略图和能直接使用的图片地址,把它们填进图片字段(create_poster_from_content 的 image、图片节点的 src、页面的图片背景都接受 http(s) 地址)。配置了 DINGCARD_SERVER_URL(和账号)时走部署服务端的图库代理(Pixabay / Unsplash / Pexels / Openverse,密钥留在服务端),选中的图用 import_stock_image 转存成账号里的稳定地址;没配置时直连 Openverse(免密钥、只搜 CC0 可商用图),结果里的 url…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 搜索词,如 "咖啡馆 内景"、"city skyline night" |
| page | integer | no | 页码,默认 1;一页约 12 张 |
| source | string | no | 图库源 id(服务端模式下可换源,如 pixabay / unsplash / pexels / openverse);不填用默认源 |
把 search_images 选中的一张照片通过部署的服务端转存到账号的图片库里,得到稳定的原图地址(比缩略图清晰,也不会因为图库改链接而失效)。返回的 url 直接填进图片字段。需要 DINGCARD_SERVER_URL(和账号);没配置时不用转存,直接用 search_images 结果里的 url。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | search_images 结果里的图库源 id(如 pixabay / openverse) |
| id | string | yes | search_images 结果里这一张的 id |
自由画布 v… 文档模型与校验规则说明
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | yes | Markdown 文档信封 JSON | |
| outputDir | string | yes | PNG 输出目录(不存在会创建) |
| baseName | string | no | 输出文件名前缀,默认 "dingcard" |
| previews | boolean | no | 是否附上缩略图,默认 true |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DingCard or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.61.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish DingCard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.