AIPublished November 17, 2026

Claude builds it, GlideOS runs it: using the Glide MCP server

Connect Claude to GlideOS with the Glide MCP server. Claude builds your business apps, and GlideOS runs them with hosting, a database, sign-in, and permissions.

Andy Claremont
Claude builds it, GlideOS runs it: using the Glide MCP server

Ask Claude to build you an app and it'll happily oblige. The awkward part comes when the app needs somewhere to run, a way for your team to sign in, and a home for the updated data when they tap "Done" on a job.

Most AI tools leave that part to you.

It also happens to be what Glide has done for years.

With Glide's Model Context Protocol (MCP) server, you connect Claude to your GlideOS account. Claude builds the app. GlideOS runs it, with hosting, a database, sign-in, permissions, publishing, workflows, and team access already sorted.

GlideOS is Glide's AI-first platform for building business apps and agents. Your team signs in, your data lives in one place, and your apps work on any device.

If you already live in Claude, this is where the apps it builds can run. If you already run apps on GlideOS, this is how Claude can help with them.

Why not just let Claude do everything?

Claude can already make a lot on its own. For a personal tool or a one-off page, that's often all you need. An app your whole team depends on is a different job.

Code without a home isn't software your business can rely on. Somebody has to keep it running, keep it secure, and keep the right people in it.

When Claude connects to GlideOS, it works as you, inside your own organization. If you belong to more than one, you pick which one when you sign in. It can open the projects you can open, and nothing else. Everything it makes stays in GlideOS: the apps, the tables, your data, and the rules about who sees what.

It also means you're not tied to any one AI. Switch tools next year and your GlideOS apps stay where they are. As we like to say: your agent is replaceable, your software is not.

How do you connect Claude to GlideOS?

Note: The Glide MCP server is included on the Pro plan and above. New to GlideOS? Start for free, then upgrade your organization to Pro to connect Claude.

There are no developer keys to copy, paste, or lose. You just sign in with your Glide account. Here's the address you'll need:

https://mcp.glideapps.dev/mcp

In the Claude app (web or desktop)

This is the easiest route if you don't spend your days in a terminal.

  1. Open connectors: In Claude, go to Customize > Connectors.
  2. Add GlideOS: Click +, choose Add custom connector, paste the address above, and name it GlideOS.
  3. Sign in: Log in with your GlideOS account when asked.
  4. Say hello: Start a new chat and ask Claude to list your projects. If it can, you're connected.

On a Team or Enterprise plan, an owner adds GlideOS for everyone under Organization settings > Connectors. Then each person signs in with their own GlideOS account. On Claude's Free plan, you can add one custom connector.

Anthropic's help center has the full steps for each Claude plan: Get started with custom connectors using remote MCP.

The Add custom connector dialog in Claude, named GlideOS, with the Glide MCP server address filled in.
Paste one address and sign in. No developer keys.

In GlideOS, you'll find the matching settings on the Agents screen.

The GlideOS Agents screen showing the server address, a Pro badge, and teammates' connected agents.
Each teammate connects their own Claude, with their own access.

In Claude Code

If you're more at home in a terminal, it's one line:

claude mcp add --transport http glide https://mcp.glideapps.dev/mcp

Then run /mcp in Claude Code and sign in with your GlideOS account. For more options, see Anthropic's guide, Connect Claude Code to tools via MCP.

It's the same server with the same abilities, so everything in this post works from Claude Code too. If you already use it for other projects, your GlideOS work can sit right alongside them.

The same address and sign-in also work in other MCP clients, including OpenAI's clients and Codex.

What can Claude actually do in GlideOS?

Quite a lot. Here's what it can do:

  • Build and fix apps: Claude edits your app, previews it, and checks for errors. Try "Add a photo field to the job form and make it required."
  • Ask and change your data: Claude writes and runs the database queries, so you don't have to. "How many orders came in last week?" is a perfectly good question.
  • Publish and roll back: Push changes live, see past versions, and undo when you need to.
  • Run backend code: Handle logic on the server, like recalculating the totals on every open invoice.
  • Use integrations: Ask which integrations your app can use, then have Claude run an action.
  • Automate with workflows: Set up schedules, webhooks, and triggers that keep working while you get on with your day.
  • Back up your database: Take a snapshot before you try anything bold.

Claude can also handle the fiddly setup bits:

  • Create a new project, or find one you've already got.
  • Import a spreadsheet or other data source into GlideOS tables.
  • Set your app's name, icon, and color.
  • Claim a web address, or connect your own domain.
  • Decide who can open the app: invite only, anyone who signs up, sign-in optional, or fully public.

What does this look like for a small business?

Here are five everyday jobs Claude and GlideOS can take off your plate. Each one starts with a question you've probably asked yourself.

1. "Can my crew use this on their phones?"

Good for: trades and field services

Spreadsheets are great in the office and miserable on a job site. Hand Claude your jobs sheet and ask:

"Here's my jobs spreadsheet. Make an app my reps can use on their phones, staff only."

Claude brings the sheet into GlideOS, builds a mobile app around it, and keeps it invite only. Your crew signs in and sees today's jobs. Nobody has to pinch-zoom into cell C47 again.

A jobs spreadsheet on the left and the same jobs in a Crew Jobs phone app on the right.
From a jobs spreadsheet to a staff-only phone app.

2. "Can clients check in without emailing me?"

Good for: agencies, accountants, and clinics

If half your inbox is clients asking where things stand, give them somewhere to look. Ask Claude for a customer portal on your own domain, and decide whether clients sign in or just follow a link. It looks like part of your business, because it is.

3. "What actually sold last month?"

Good for: retail and restaurants

You don't need a report builder or a weekend with pivot tables. Just ask:

"What were my top 10 items last month?" or "Which stock is below par?"

Claude runs the query on your data and gives you the answer in plain English.

4. "Can it just do this every Monday?"

Good for: anyone with a weekly chore

Try asking: "Every Monday, email me last week's open jobs."

(Connect your Gmail in GlideOS first. The email comes from your own inbox.)

Claude sets up a scheduled workflow in GlideOS, so it keeps running long after you've closed the chat. Workflows can also kick off from a webhook, like when someone submits a form.

5. "What if I break something?"

Good for: everyone with a live app

Build the safety net into your request:

"Back up first, then add a discount field."

And if a change doesn't land the way you hoped:

"Roll back to the last version."

Backups and version history mean you can experiment without gambling with the app your team uses every day.

Already building in GlideOS?

GlideOS has its own agent built in, so why bring Claude into it? Because a lot of your work probably happens in Claude already. Now the plans, notes, and drafts in your Claude chats can turn into changes to your apps in the same place.

Claude works just as well on the apps you already run. A few prompts to start with:

  • Fix something that's off: "Why does the Overdue tab show jobs that are already finished?"
  • Understand what's there: "Explain what the Monday reminder workflow does, step by step."
  • Tidy your data: "Find duplicate customers in the Clients table and show me before changing anything."
  • Add a feature carefully: "Add a status filter to the Jobs screen and let me preview it before you publish."

Each person on your team connects their own Claude, and Claude gets only that person's access. If a teammate can't open a project in GlideOS, they won't find it through Claude either.

Is it safe to let an AI loose in my business?

Here's how Claude gets fenced in:

It only sees what you see. Claude signs in as you and works inside your own GlideOS organization. If you can't open a project, neither can it.

You stay in the loop. Claude asks before it uses a tool, and you choose how much to allow in Claude's own settings. For anything big, like deleting data, restoring a backup or changing who can open an app, ask Claude to check with you first, or keep approvals on for those tools.

Claude asks for approval before restoring a backup of the Crew Jobs app, with Approve and Deny buttons.
Claude asks before it restores a backup.

Back up before you experiment. Take a snapshot first, and roll back if a change doesn't land.

Your plan still applies. Claude works within the same limits you do. If your organization has hit its limit of published apps, for example, Claude can't publish another one either.

Some things still happen in GlideOS. Claude can't do everything yet. Inviting guests, for example, is still done from the GlideOS dashboard.

Ready to try it?

Claude builds it. GlideOS runs it. And your apps stay yours, whichever AI you use next.

  1. Connect: Add https://mcp.glideapps.dev/mcp as a custom connector in Claude.
  2. Sign in: Use your GlideOS account.
  3. Ask: Start with something like "Turn this Excel spreadsheet into a dashboard."

Already a GlideOS customer on the Pro plan? Follow the steps above, then try one of the prompts on an app you already run.

Upgrade to GlideOS Pro to connect Claude and start building.

For the bigger picture, learn how to bring your own agent to GlideOS.

Andy Claremont

Andy Claremont leads ecosystem and community at Glide. His no-code journey started with WYSIWYG editors in the 90’s and he's been building ever since.

Glide turns spreadsheets into beautiful, intelligent apps.