Free vs paid CMS servers publishing is the unit that matters.
CMS is one of the smallest categories on Loomal, and most of its servers are free connectors to a CMS you already run — WordPress, Umbraco, Sanity. The interesting pricing question is what a publish action is worth when an agent performs it.
Content management was built around humans with logins, which is why agent access to a CMS goes through MCP servers like these: WordPress MCP Server manages posts, users, comments, and settings; Umbraco-CMS-MCP-Dev does the same for Umbraco; mcp-sanity-images handles one job — getting local images into Sanity. All free, all assuming the CMS underneath is yours.
With around a dozen live listings, this is a category where you can actually read every option. The free-versus-paid split here is less about the connectors and more about what happens when publishing itself becomes the product.
CMS MCP servers on the Loomal Index
Umbraco-CMS-MCP-Dev
A developer focused model context protocol (MCP) server for Umbraco CMS
lightcms
AI-native CMS with 41 MCP tools for managing websites through natural language.
WordPress MCP Server
MCP server for WordPress. Manage posts, users, comments, terms, metadata, and settings.
ACMS
Apple Container MCP Server (ACMS) provides access to Apple's container CLI tool on macOS
pipepost
MCP server to publish to Substack, Ghost, Dev.to, WordPress, LinkedIn + 5 more from Claude Code.
MCP Wordpress
Secure MCP server for WordPress content management
mcp-sanity-images
MCP server for uploading local images to Sanity CMS
partd-mcp
CMS Medicare Part D drug spending and prescriber data. 2024 quarterly data.
Cms
CMS Open Data MCP — US Centers for Medicare & Medicaid Services.
Npi Registry
CMS NPI Registry MCP
Neural Draft
Neural Draft MCP — CMS, blog, bookings, galleries, commerce. 38 tools.
Free connectors to content you own
If you run the CMS, the free connector is the whole answer. A WordPress site managed through WordPress MCP Server costs you exactly what WordPress always cost; the MCP layer adds agent access, not expenses. The same logic covers Umbraco-CMS-MCP-Dev for Umbraco shops and lightcms, an AI-native CMS that exposes 41 tools for managing websites in natural language.
The practical costs are familiar CMS costs wearing a new hat: credential scoping (an agent with admin on your WordPress is a one-prompt defacement risk), staging-versus-production discipline, and keeping the connector current with CMS API changes.
Distribution is where third parties enter
The moment publishing crosses into platforms you don't control, the free model gets complicated. pipepost publishes to Substack, Ghost, Dev.to, WordPress, LinkedIn, and more from one server — which means juggling one credential per destination, each with its own API quirks and quotas. Self-hosting that is free in license and expensive in upkeep, because you've made yourself the integration layer for ten platforms.
That maintenance burden — not compute — is what a hosted, paid publishing endpoint would actually be selling in this category.
What per-call pricing looks like for content
Content operations come in naturally countable units: one post published, one image uploaded and optimized, one piece syndicated to five platforms. x402 prices exactly that unit. An agent calls the endpoint, receives 402 Payment Required, pays in USDC on Base — settlement in roughly two seconds, payment cleared before the handler runs, Ed25519-signed receipt returned — and the publish happens. Prices start at $0.01 per call.
For an agent ghostwriting a weekly newsletter or syndicating posts on demand, that beats holding credentials for every destination and beats any subscription sized for daily publishing it won't do.
Where each model wins
Keep it free and self-hosted when the CMS is yours, the agent is yours, and publishing volume is whatever your own infrastructure tolerates. Look for paid per-call endpoints when the value is in maintained integrations to platforms you don't own, or when agents outside your team need a safe, narrow publish capability without touching your CMS credentials.
Maintainers in a small category have a discovery advantage: a dozen listings means yours gets seen. Claiming your listing on Loomal and pricing the publish action puts a number on the integration work you're already doing — with a 5% fee on settled transactions, currently waived.
Frequently asked questions
Should my agent use a free or paid CMS MCP server?
If the content system is yours, self-host the free connector — WordPress MCP Server against your own WordPress adds no cost and keeps credentials in your hands. Paid per-call endpoints earn their price when they maintain multi-platform integrations for you, or when you need to grant publish capability without granting CMS access.
What's the right unit to price content operations in?
The action, not the time period. One publish, one upload, one syndication fan-out — each is discrete, verifiable, and valuable on its own, which makes per-call pricing via x402 a cleaner fit than subscriptions for agents that publish irregularly. The minimum on Loomal is $0.01 per call.
Is a paid CMS server safer to use than a free one?
The safety difference comes from architecture, not price. A paid endpoint that publishes on your behalf never holds your CMS admin credentials — the trust boundary is one narrow action with a signed receipt. A free connector you self-host is equally safe only if you scope its CMS role as tightly.
Where can I compare CMS MCP servers?
Loomal's CMS category page lists every live server with its description and package details, plus x402 per-call pricing where the maintainer has claimed and priced the listing. It's a small enough category to evaluate completely in one sitting.
Run a CMS MCP server?
Claim your listing, set a per-call USDC price, and let AI agents pay for every call over x402.
List it on Loomal