Siteglide MCP (Alpha)

Give AI the right tools, access, skills and guardrails to help you achieve top results

Written By Luke Wakefield

Last updated About 16 hours ago

Siteglide MCP is currently in Alpha and only available with CLI v1.11 onwards.

Please use caution and for testing purposes only by copying a site to Staging.

What is it?

Siteglide MCP connects your AI coding assistant to your Siteglide project. Instead of only editing files locally, the assistant can validate Liquid, run GraphQL, evaluate templates against staging, and read logs — using the same Siteglide CLI setup you already use.

Works with Cursor, Claude Code, Windsurf, and other editors that support MCP.

Why use it?

Catch mistakes before they reach staging
The assistant can validate Liquid, GraphQL, and YAML against Siteglide rules before saving — fewer broken templates after sync.

Test against real data
Run Liquid and GraphQL against your staging site from the editor, without copy-pasting API responses into chat.

Debug faster
Pull recent platform logs when something fails, instead of switching between the admin, terminal, and your IDE.

Safer by default
Credentials stay in Siteglide CLI on your machine. The assistant uses environment names (like staging) — it should never read or paste your config tokens.

Same platform as your site
MCP talks to the same staging environment you sync to with siteglide-cli sync. What the assistant validates is what you’ll see on staging.

What you need

  • Siteglide CLI installed and logged in

  • A Siteglide project pulled locally (siteglide-cli pull)

  • An MCP-capable editor (e.g. Cursor)

  • A staging environment (recommended for everyday use)

Setup

1. Pull your project

siteglide-cli pull

This downloads your site files and writes MCP configuration for your editor.

2. Turn on the MCP server in your editor

In Cursor: open Settings → Tools & MCP, enable the siteglide server, then reload the window.

Other editors: use the MCP config file CLI created in your project (for example .mcp.json or .cursor/mcp.json).

3. Confirm it’s working

Ask your assistant something like:

List my Siteglide environments and validate my homepage Liquid against staging.

If MCP is connected, it can list your sites and run validation — without you sharing API tokens.

4. Sync to staging (recommended)

siteglide-cli sync staging

Keep sync running against staging while you work with an assistant, you can then view changes without needing to deploy.

How to use it

You don’t call MCP tools yourself — you describe what you want in chat, and the assistant uses the right tool.

You want to…Example prompt

Fix or build a section

“Validate this Liquid partial and fix any Siteglide errors.”

Check a GraphQL query

“Run this GraphQL query against staging and show the record shape.”

Preview Liquid output

“Evaluate this Liquid snippet against staging data.”

Debug an error

“Fetch recent logs from staging for this page.”

Start a session

“Connect to Siteglide MCP for this project and use staging only.”

Good habits

  • Say staging when you want live tests (safest default).

  • Ask the assistant to validate before saving on larger Liquid or GraphQL changes.

  • If siteglide-cli sync is running, confirm it’s pointed at staging, not production.

What the assistant can do

Capability

What it helps with

Validate code

Check Liquid, GraphQL, and YAML before write

Run Liquid

Render templates against staging (not production)

Run GraphQL

Read or update CMS / WebApp / CRM data

Fetch logs

Inspect recent platform errors

List environments

See staging vs production URLs safely

Production is protected: Liquid evaluation on production is blocked, and production GraphQL changes require your explicit approval.

Troubleshooting

The assistant doesn’t have Siteglide tools
Enable the siteglide MCP server in your editor settings and reload.

Tools fail to start
Re-run siteglide-cli pull so MCP paths are correct for your machine.

Validation passes but staging looks wrong
Check that sync is running and pointed at the right environment, then hard-refresh the browser.

The assistant asks to read config files
Don’t paste tokens. It should use environment names and MCP tools only.

Advanced (coming soon)

A follow-up guide will cover agent rules, production sync safety, GraphQL mutations on live sites, and CI-style validation workflows.

Summary: Siteglide MCP lets your AI assistant work with your Siteglide project — validate templates, query staging, and read logs — while keeping credentials on your machine and staging as the default place to experiment.