Developer Tools & Devops · Siteleaf + Claude
Siteleaf MCP with Claude: Manage Static Site Content Through Natural Language
The short answer
Claude works with Siteleaf through the Model Context Protocol (MCP), an open standard that acts as a secure adapter between the two. Once connected, Claude can list your sites, read and update pages and posts, and publish static content when you ask. Access is limited to the permissions you set, and sensitive changes can require human approval.
What is Siteleaf?
Siteleaf is a content management system for static websites built with Jekyll and synced with GitHub. It gives editors a clean, friendly writing interface while the site itself stays fast, versioned and simple to host. It is used by developers, technical content teams and small businesses that run documentation sites, blogs, marketing pages and company websites built on static site generators.
How Claude connects to Siteleaf through MCP
The Model Context Protocol is an open standard that lets Claude use other software securely, reading information and taking actions with permissions the organisation controls. Think of it as a universal adapter between Claude and the tool. For Siteleaf, the connection can use the Siteleaf MCP server or a direct API link, signed in with the API key or Basic sign-in method that Siteleaf supports.
Once connected, Claude can typically list the sites in your account, find pages and posts, read their content, and draft or update text on request. A content editor might ask in plain English to update a product page or add a new post, and Claude carries out the change inside Siteleaf.
Permissions and approvals keep people in charge. Access is granted with least-privilege settings, so Claude only sees the sites and actions you allow. Consequential steps such as publishing can be set to wait for a named person to approve, and every action is recorded in an audit log for review.
What you can automate
Refreshing product and pricing pages
When prices or product details change, a marketing manager can ask Claude to find the affected pages and update the wording. Claude drafts the changes, shows the revised text, and waits for approval before anything goes live. This removes the manual hunt through dozens of pages and reduces the chance of an outdated price staying online.
Publishing blog posts from briefs
Content teams often write briefs in a shared document. Claude can take an approved brief, create a draft post in the correct Jekyll format, add the title, date and tags, and place it in Siteleaf for editorial review. Editors keep final control over tone and publishing, so the team spends its time on quality rather than formatting.
Keeping documentation sites current
Engineering teams can ask Claude to update installation guides or release notes after each software version. Claude reads the existing pages, adds the new information and flags sections that may now be out of date. A developer reviews the changes before they are published, which keeps technical documentation accurate.
Auditing content across many sites
Agencies and multi-site organisations can ask Claude to list all sites and pages, check for missing metadata, broken titles or outdated dates, and produce a summary report. This gives operations leads a clear picture of where content needs attention, without opening each site by hand.
Answering routine editing requests
Customer support or communications staff often receive small change requests, such as correcting a phone number on a contact page or adding a new office opening. Claude can make these edits from a short instruction, log what it changed, and send the update for sign-off, which shortens turnaround times for everyday fixes.
An end-to-end workflow: Product launch page update with approval
TriggerA product manager posts an approved launch note in the team's project channel.
Claude reads the launch note and lists the Siteleaf pages that mention the product.
Claude drafts updated copy for the product page, the homepage banner and the news post.
The content lead reviews the drafts and approves the changes in the approval step.
Claude publishes the approved pages to the site and records each change in the audit log.
A summary of the updated pages is sent to the marketing team's shared workspace in Microsoft 365.
OutcomeLaunch content goes live consistently across several pages on the same day, with a clear record of who approved what. Typically this saves the team hours of manual editing per launch.
How we set it up
Book a free automation audit
We review how your team creates and publishes content in Siteleaf and identify the workflows worth automating, such as page updates, post creation or publishing approvals.
Choose the connection method
We set up the connection using the Siteleaf MCP server or a direct API link. Access is signed in with an API key or Basic sign-in, depending on what your account and security policy allow.
Design the workflow and approvals
We map the end-to-end process across Siteleaf and your other systems, such as Microsoft 365 or your ticketing tool. We define which actions Claude may take alone and which need a named approver.
Test against real past cases
We run the workflow against real past edits and posts to check accuracy, formatting and tone. We refine the instructions until results meet your editorial standards.
Launch, monitor and train
We go live with monitoring and audit logs in place, then train your editors and managers on how to make requests and review changes safely.
Who benefits
- Marketing managers
- Update campaign and product pages quickly while keeping approval control over every live change.
- Content editors
- Spend less time on repetitive formatting and more time on quality and storytelling.
- Developers and technical writers
- Keep documentation sites accurate after each release without manual copying between tools.
- Operations and IT leads
- Gain an audit trail and least-privilege access across static sites in one place.
Security and control
- Least-privilege access so Claude only reaches the sites and actions you approve.
- Human approval required before publishing or any change you classify as consequential.
- Full audit logs of every read, draft and publish action for review.
- Credentials such as API keys stored securely and rotated on your schedule.
- Regular checks after launch to confirm the workflow behaves as designed.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude integration in their chosen region to meet internal data handling standards. Indian organisations can align the workflow with the Digital Personal Data Protection Act, 2023, and businesses in the UAE and Saudi Arabia can follow their local data protection laws. We select the hosting region for each deployment to meet your specific legal and contractual requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Siteleaf MCP server do?
The Siteleaf MCP server acts as a secure bridge between AI tools like Claude and your Siteleaf account. It lets approved AI tools list sites, read pages and posts, and make updates through a defined set of actions. The server only exposes what the connection is permitted to do, so it does not give open access to your whole account.
Is it secure to connect Claude to Siteleaf?
Security depends on how the connection is set up. We use least-privilege access, sign in with the API key or Basic method Siteleaf supports, and require approval for publishing. Every action is logged, and credentials are stored and rotated securely. We cannot guarantee security in every case, but we design each connection around these safeguards.
What can Claude actually do with Siteleaf?
Typically, Claude can list your sites, find pages and posts, read content, draft new text, update existing pages and prepare content for publishing. Exactly which actions are enabled is decided during setup, based on your workflow and the permissions you approve.
How long does setup take?
Setup time depends on how many sites you run and how complex your approval process is. A single-site connection with a simple workflow is often ready within a few weeks, including testing and training. Larger, multi-site setups usually take longer. We confirm a realistic timeline during the free audit.
Which plan or permissions do I need?
You need a Siteleaf account with the access level that allows the actions you want to automate, and an API key or Basic sign-in that your account supports. The exact requirements depend on your current plan and team roles, so we check these during the free audit before any connection is made.