Siteleaf

@siteleaf list all documents in the 'blog' collection and show me which ones are still in draft status

The 'blog' collection contains 47 documents. Of these, 8 are currently in draft status: 'introducing-our-new-api' (last modified 3 days ago), 'migration-guide-v2' (last modified 1 week ago), 'performance-optimization-tips' (last modified 2 weeks ago), and 5 others. The remaining 39 documents are published. All drafts have 'visible: draft' in their metadata. This is an illustrative example showing how the MCP surfaces document visibility state across a collection.

This example uses the list/read capabilities to surface content state. Requires API key with read access to the target site. Useful for editorial workflows where you need to track unpublished content. The MCP returns metadata fields including visibility, so you can filter or prioritize drafts without opening each document individually.

@siteleaf create a new blog post titled 'Q1 Product Updates' with a summary of our recent feature releases, set it to draft, and tag it with 'product' and 'announcements'

Created document 'q1-product-updates' in the 'blog' collection with draft visibility. The document includes the provided content summary, a slug generated from the title, and taxonomy tags 'product' and 'announcements'. The document is now visible in your Siteleaf dashboard under Drafts and can be edited further before publishing. Document ID: doc_abc123xyz. This illustrative example shows the MCP creating content with metadata in a single action.

This example demonstrates the Create Document tool, which writes new content with front matter in one step. Requires API key with write permissions. The MCP sets visibility to 'draft' by default unless you specify 'visible: published'. Be aware that creating documents does not trigger a site rebuild — you'll need to publish separately to deploy changes to your live site.

@siteleaf review all blog posts published in the last 30 days and draft a short release note highlighting the three most significant topics we covered

Reviewed 12 blog posts published between March 1-31, 2024. The three most significant topics were: (1) API v2 migration guidance, covered in 4 posts with detailed code examples; (2) Performance optimization strategies, including caching and asset delivery improvements; (3) New collaboration features for multi-author workflows. Suggested release note: 'This month we focused on helping teams migrate to our v2 API, optimize site performance, and collaborate more effectively. Read our migration guide, performance tips, and workflow updates on the blog.' This illustrative example shows synthesis across multiple documents.

This example pairs Siteleaf's read capabilities with the AI's reasoning to synthesize content themes. The MCP fetches document metadata and content, then the AI identifies patterns and drafts copy. Useful for generating summaries, newsletters, or changelog entries from your CMS content. Rate limits apply when fetching many documents — the API allows 120 requests per minute per API key.

When non-technical editors need to ship content changes fast

A 6-person startup runs their marketing site on Jekyll via Siteleaf. The product manager wants to publish a new case study page without waiting for the engineer to merge a PR. This MCP is the right call if your team already uses Siteleaf and needs AI to draft pages with proper front matter, taxonomy, and metadata in one shot. The Create Page and Create Document tools handle YAML structure so the PM can say "add a case study for Acme Corp with tags SaaS and enterprise" and the AI writes valid Jekyll. The threshold: if your site has complex nested layouts or custom shortcodes, you'll still need a dev to review the output before publish. Worth it when your content velocity is 3+ pages per week and your editor knows enough to spot broken links.

This MCP handles one-time content imports at small scale

A 3-person dev tools company is moving 40 markdown docs from a legacy CMS into Siteleaf. The Create or Replace Source File tool can push each file programmatically, but the 35-tool surface means you're also paying for job cancellation, role management, and collection scaffolding you won't touch. This MCP works if you're already committed to Siteleaf and need the AI to map old front matter fields to new taxonomy during the import. The trade-off: if you're migrating more than 200 files or need to preserve git history, a direct Jekyll repo script is faster and cheaper. Use this MCP when the migration is a weekend project and you want conversational control over how metadata gets rewritten, not when you're automating a 10k-page cutover.

When you spin up 5+ Siteleaf sites per month for clients

A 10-person agency builds marketing sites for local businesses on Siteleaf. The account manager wants to say "create a site for Bakery XYZ with their timezone and grant the owner publisher access" without opening the Siteleaf dashboard. This MCP is the right tool because Create Site and Create Role let the AI handle the full onboarding flow in one conversation. The agency saves 15 minutes per client and avoids the copy-paste errors that happen when setting up defaults and permissions manually. The boundary: if your agency uses a white-label CMS or needs to template 20+ collections per site, Siteleaf's structure might be too rigid and this MCP won't fix that. Best fit when your client sites share 80% of the same scaffold and you bill hourly for setup time.