Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/SanNw/Indesign-MCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/sannw/indesign-mcp/mcp-indesign)<a href="https://agentmods.dev/mcp/sannw/indesign-mcp/mcp-indesign"><img src="https://agentmods.dev/badge/mcp/sannw/indesign-mcp/mcp-indesign/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/sannw/indesign-mcp/mcp-indesign"><img src="https://agentmods.dev/badge/mcp/sannw/indesign-mcp/mcp-indesign.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-indesign scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "mcp-indesign": { "command": "npx", "args": [ "-y", "mcp-indesign" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 4cb886de7e19
mcp-indesign is an MCP server published in the GitHub repository SanNw/Indesign-MCP (0 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
photoshop-mcp
MCP server for Adobe Photoshop — 118 tools (generative AI + recipes), standalone web UI. Control Ph… Runs locally from the @alisaitteke/photoshop-mcp npm package.
indesign-nutria-mcp
The most comprehensive MCP server for Adobe InDesign: 197 tools, AI-native, full DOM control. Runs locally from the indesign-nutria-mcp npm package.
adobe-mcp
Drive Adobe CC (AE, Photoshop, Illustrator, Premiere, Character Animator) from any MCP client. Runs locally from the @ajsmonty/adobe-mcp npm package. Needs 1 environment variable to run.
premiere-pro
MCP server for Adobe Premiere Pro with 384 core AI video editing tools, a guarded After Effects MOGRT studio, and a capability-aware UXP bridge for supported Premiere workflows. Runs locally from the premiere-pro-mcp npm package.
premiere-pro
Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check. Runs locally from the premiere-pro-mcp npm package.
after-effects
Control Adobe After Effects with AI — describe the animation you want and it gets built: layers, keyframes, effects, expressions and text, all editable afterwards. Runs locally from the @engine-room/after-effects-mcp npm package.