ZeroCMS

io.zerocmsPublished by zerocms.ioOfficial publisherv1.0.0Updated Oct 24, 2026

AI-native Git-based CMS for Astro. Create and publish content in the browser, without learning git.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

ZeroCMS is a remote MCP server for an AI-native, Git-based CMS for Astro, letting an assistant help create and publish content without using git directly.

What you can do
The input lists no tools, so capabilities come from the description only. It connects an assistant to a Git-based content management system built for Astro sites. It is aimed at creating and publishing content through the browser rather than working with git directly. The manifest declares no tool list, so the exact actions available are not documented here.
When to use it
Worth considering if you run an Astro site on ZeroCMS and want an assistant to help draft or publish content without touching git. Less relevant if your site is not on ZeroCMS or you need documented tool-level control.
Requirements
A remote endpoint at mcp.zerocms.io over streamable HTTP. OAuth authentication is required, so you need a ZeroCMS account and to complete the OAuth sign-in. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, granting it access to your ZeroCMS account. It is oriented toward creating and publishing content, so changes may go live on your site; review before publishing. No tool list is published, so what it can read or change is not documented here.

Installation

In SourceWeft

  1. Open ZeroCMS in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.zerocms%2Fzero/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zerocms": {
      "type": "http",
      "url": "https://mcp.zerocms.io/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.