CDN.MN Review: The Image CDN Your AI Coding Agent Can Install

Every mainstream image CDN — Cloudinary, imgix, Bunny Optimizer, Cloudflare Images — was designed for a human developer to install by hand: read the docs, generate API keys, wire up a URL rewriter, update the CMS, run through a staging QA pass, flip DNS. That flow works if you have a spare afternoon and a developer to spend on it. It falls over the moment you try to hand it to an AI coding agent, because the agent needs a master API key it should not have, a manual DNS change it cannot verify, and a series of approval decisions that only exist in a human head. CDN.MN is the first image CDN that inverts that assumption. The primary interface is an AI agent, and the whole product surface — MCP server, agent SKILL, OpenAPI, CLI, SDK — is designed to be discovered and driven by a Claude Desktop, Cursor, or other MCP-capable client. The dashboard exists for human-driven workflows, but it is not the differentiator. The differentiator is that a coding agent can analyse a public site, provision a temporary workspace, configure and verify the origin, activate a delivery hostname, and prepare the integration on a branch — all before the site owner even signs in.

In practice, the agent-install flow is one prompt away. Point an MCP-capable agent at CDN.MN and ask it to add image optimization to your site. The agent connects through the MCP server (or reads the SKILL.md instruction file), parses your project's framework configuration, prepares the integration on a branch, and verifies that images resolve, formats convert correctly (WebP, AVIF), caching behaves as expected, and existing tests still pass. All of that happens against a preview environment, not production. When the preview looks right, the agent presents a small set of production actions — the billing change to move from evaluation to a paid plan, the DNS switch to route real traffic through the delivery hostname — as an approval gate. A human clicks approve, and the change goes live. Roll back if the metrics look off. Nothing about that flow requires the agent to hold a long-lived master API key or make an irreversible decision unsupervised. For a solo developer or a small web team where the AI agent is already the primary interface for touching infrastructure, the cost of 'add an image CDN' changes from a project scoped in hours to a prompt scoped in minutes.

The obvious objection to letting an agent install a piece of infrastructure is: what stops the agent from making expensive or irreversible decisions? CDN.MN's answer is a set of concrete guardrails that are visible from the moment the agent starts a workspace. Credentials are short-lived and task-scoped, not master keys. If an agent needs to provision an endpoint, it gets a credential scoped to that action, valid for the duration of the task. Anything billing-related — moving from evaluation to a paid plan, upgrading tiers, adding a payment method — always requires a human approval gate; the agent cannot spend on your behalf without an explicit click. Production DNS, origin changes, and destructive actions are permission-scoped: the owner chooses, per permission, whether a trusted agent acts on its own or waits for approval, with sensible defaults that keep the sharp edges gated until they're explicitly delegated. Every action the agent takes is written to an audit log the owner can inspect and, if needed, roll back. That combination — scoped short-lived credentials, always-gated billing, per-permission control over production changes, preview-before-production, and full audit logs — is what makes 'agent-installable infra' something a security-conscious team can actually accept, rather than a marketing bullet.

The second reason CDN.MN is easy for an agent to install is that nothing has to move. It's a pull-through CDN: your images stay wherever they are today — S3, your CMS, a static site's build output, WordPress uploads — and CDN.MN fetches them on demand from a verified origin, converts to WebP or AVIF as appropriate for the requesting browser, resizes and compresses per request, caches the optimized variant at the edge, and serves it globally. That matters for two reasons. First, it means no CMS rewrite, no re-upload, no bulk migration script, and no risk of breaking existing image URLs — the integration is additive rather than destructive. Second, it means an agent can install CDN.MN without ever touching your source files, which sharply narrows the blast radius of anything the agent gets wrong. On the optimization side, the actual work is standard-issue for modern image CDNs but complete: WebP and AVIF conversion, resize and compression per request, global edge caching, and a dashboard for requests, bytes delivered, cache hit rate, and transformation counts. Nothing surprising — which is the point. The novelty is in how it gets installed, not what it does at runtime.

The pricing ladder maps cleanly to how a real site scales up. Pay-as-you-go starts free with $5 in credits at signup (no card required) plus another $5 when you add a payment method. That covers 1 endpoint, a cdn.mn subdomain, and images up to 50 MB per file — enough to prove the integration end-to-end on a real site before spending a dollar. Growth, at $39/mo, is the first production tier: 3 endpoints, images up to 150 MB, 60 GB delivery, and 50,000 transformations per month, plus automated cache management. It's priced for a growing production site running a small number of hostnames. Business, at $149/mo, is the tier the vendor points teams toward (marked POPULAR on the pricing page): 10 endpoints, 250 MB per image, 250 GB delivery, 150,000 transforms, team members, and logs export — the right size for agencies and teams with multiple sites. Video, at $299/mo, is still marked early access: 3 endpoints, files up to 5 GB, 800 GB delivery included, with own-domain delivery coming soon. Enterprise is a custom contract with unlimited endpoints, custom domains, volume delivery rates, SSO, and dedicated support with SLA options. Agencies with five or more paid workspaces get a 20% discount across all paid plans. The honest read: Pay-as-you-go is a genuine evaluation on-ramp, Growth is priced for a real production site, and Business is where multi-hostname or multi-site teams should size themselves from the start rather than upgrading under load.