Skip to main content
AI

Cloud MCP

Connect your AI app to your Siteglide sites to work with content and data. No setup needed.

Written By Luke Wakefield

Last updated About 3 hours ago

Invite Only Access: If you would like to test this out drop us a message via Live Chat and we can turn it on for you. It’s important to understand this is a new feature and it gives AI tools access and control to edit your sites. Please start with Read (not Read & Write) access first.

The Cloud MCP connects your AI app to your Siteglide sites so the assistant can read and update your content and data, such as CRM users, form cases, products, orders, WebApp and Module items, categories and pages. It's a hosted connector. There's nothing to install, and you sign in with your Siteglide account.

If you want help writing site code, Liquid or GraphQL in your editor, use the Local MCP instead. See MCP overview to compare the two.

Connect

  1. In your AI app, add a custom MCP connector (it may be called a "remote MCP server" or "custom connector") with this server URL:

https://mcp.siteglide.com/mcp

  1. When your AI app asks you to sign in, sign in with your Siteglide account. The Cloud MCP uses OAuth, so you don't need an API key.

  2. Check it's working by asking your assistant: "Which Siteglide user am I connected as, and which sites can I access?"

Your sites need System Files 2.8.6.0 or later to use the site tools. Page tools need 2.9.0.0 or later.

Supported AI apps

The Cloud MCP is a standard remote MCP server (streamable HTTP, with OAuth sign-in and dynamic client registration). AI apps that support remote MCP servers with OAuth should be able to connect.

What it can do

The Cloud MCP has 41 tools: 28 read tools and 13 write tools. There are no delete tools. Site tools take a site ID or a domain.

Area

Read

Write

Your account and agency

whoami, list_sites, get_site, list_companies, get_company, list_users, get_user

none

WebApps

list_webapps, get_webapp_fields, list_webapp_items, get_webapp_item

create_webapp_item, update_webapp_item

Modules

list_modules, get_module_fields, list_module_items, get_module_item

create_module_item, update_module_item

Categories

list_categories, get_category

create_category, update_category

CRM users

list_crm_users, get_crm_user

create_crm_user, update_crm_user

Form cases

list_form_cases, get_form_case

create_form_case

eCommerce

list_products, get_product, list_orders, get_order, list_user_orders

create_product, update_product (orders are read-only)

Pages

list_pages, get_page

create_page, update_page

The Cloud MCP doesn't run Liquid or GraphQL, read logs, or sync or deploy code. Use the Local MCP for those.

Permissions and guardrails for live sites

  • It acts as you. The Cloud MCP signs in as your Siteglide user and has your full rights. It can reach every site you can access, and do whatever your user can do on those sites within the tools it offers. Siteglide-level users see everyone; agency users see their agency and its clients; client users see their own company.

  • Writes go straight to the site you name, including live sites. There's no staging-only mode and no approval step in the Cloud MCP itself.

  • 13 write tools, no deletes. The assistant can create and update, but it can't delete anything. To remove something, do it in Siteglide yourself.

  • An update can overwrite the whole item. Updating a WebApp item replaces the whole item, so any field the assistant leaves out can be cleared. Ask the assistant to read the item first and send every field back.

  • CRM user tools can set passwords. Be careful when asking the assistant to create or update CRM users.

Good practice:

  • Try changes on a staging copy of your site first.

  • Ask the assistant to tell you what it's going to change, and on which site, before it writes anything.

  • Only connect with an account whose access you're happy for the assistant to use.

  • Turn on your AI app's privacy setting, or turn off using your data for training, so your site data isn't used to train models.

Example prompts

You want to…

Example prompt

Check your connection

"Which Siteglide user am I connected as, and which sites can I access?"

Find a site

"Find the site for example.com and list its WebApps."

Look up a customer

"Find the CRM user jane@example.com on my staging site and list their orders."

Add content

"Create a new item in the Team WebApp on my staging site for Alex Smith, Head of Design. Show me the fields first."

Update a product

"On my staging site, read the product 'Blue Mug', then update its price to £12 and show me what changed."

Review form submissions

"List the latest 10 cases for the Contact form on my staging site and summarise them."

Draft a page

"Create a disabled page called 'Summer Sale' on my staging site with a short intro."

See what your AI did

Every Cloud MCP tool call is logged in Portal > MCP Audit Log. Each entry shows:

  • the user

  • how the call came in (OAuth or token)

  • the tool

  • the site

  • the outcome

  • the access

  • a run ID

You can filter the log to find a particular call.

Troubleshooting

My AI app doesn't show a sign-in prompt.Check that you added the full URL https://mcp.siteglide.com/mcp and that your AI app supports remote MCP servers with OAuth. If it can't do a browser sign-in, use a token instead (see below).

I signed in but see no sites, or the wrong sites.Ask the assistant to run whoami to check which Siteglide user it's connected as. The Cloud MCP only sees the sites that user can access. Sign out of the connector in your AI app and sign in again with the right account.

A site tool fails on one site.Site tools need System Files 2.8.6.0 or later, and page tools need 2.9.0.0 or later. Check the site's System Files version.

The connection stops working after a while.Disconnect and reconnect the connector in your AI app, then sign in again.

Something else isn't working.Tell us on the Cloud MCP Feedback board.

Using a token instead of signing in

Signing in with your Siteglide account is the recommended way to connect. If a tool can't do a browser sign-in, for example a CLI tool, an agent platform, a script or CI, you can use a token instead.

  • Create a token in Portal > MCP Tokens. The list shows each token's Access and Expires columns.

  • Send the token with each request as Authorization: Bearer <token>.

  • Service-account tokens let a tool connect without using a person's login.

Treat a token like a password. Don't paste it into chat or commit it to code.

Was this helpful?

Still need help? Ask the team