@usezanin/mcp

MCP server for Zanin, the agent-native headless blog CMS. Gives agents tools to write, edit and publish MDX posts, upload custom components and media, and read Google Search Console performance correlated with content revisions.

Setup

// .cursor/mcp.json (or any MCP client config)
{
  "mcpServers": {
    "zanin": {
      "command": "npx",
      "args": ["-y", "@usezanin/mcp"],
      "env": {
        "ZANIN_BASE_URL": "https://your-zanin-deployment",
        "ZANIN_API_KEY": "zn_..." // created in the Zanin dashboard
      }
    }
  }
}

Tools

• Content: list_sites, get_site, update_site_theme, list_posts, get_post, create_post, update_post (requires a change summary), validate_mdx (lint a body without saving), publish_post, unpublish_post, delete_post, list_revisions
• Media: upload_media
• MDX components: get_builtin_components (exact prop signatures + copy-pasteable examples for Callout, Figure, Chart, CTA, YouTube, Tweet, ComparisonTable, FAQ — call it instead of guessing props), list_components, create_component (TSX compiled server-side), delete_component
• Search performance: get_post_performance (daily metrics with revision markers inline), get_site_performance, get_top_queries

create_post/update_post responses include validation — MDX compile errors and unknown component/prop warnings from the same compiler the SDK renders with — plus post.previewUrl, a tokenized hosted preview that works for drafts. Fix validation errors and check the preview before publish_post.

Every edit requires a change summary, stored as an immutable revision. Performance tools return those revision markers inline with daily GSC metrics, so agents can see exactly what changed and what happened to clicks, impressions and position afterwards — and learn from outcomes.

MIT