Glide

dev.glideappsPublished by glideapps.devOfficial publisherv1.0.1Updated Nov 2, 2026

Glide's official MCP server — build, manage, and operate GlideOS apps, data, and workflows.

VerifiedStreamable HTTPWeb executableDatabasesProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Glide's official remote MCP server that lets an assistant build, manage and operate GlideOS projects, apps, data and workflows.

What you can do
  • Create, list and manage GlideOS projects
  • Publish, promote, roll back apps and manage app access and domains
  • Query and modify app databases, ingest data sources and manage backups
  • Run workflows and manage schedules, webhooks and triggers
  • Read, write and search project files and run backend code
When to use it
Useful when you work in GlideOS and want an AI client to inspect or change projects, app data, deployments and workflows without switching tools. Suited to Glide users on a plan that includes the MCP server feature.
Requirements
A remote Streamable HTTP endpoint; no local package to install. OAuth 2.1 sign-in with a Glide account when the client prompts, and a Glide plan that includes the MCP server feature. No API keys or environment variables are declared.
Before you install
The tools can change live data and deployments: they modify app databases, publish and roll back apps, change access and domains, run workflows and execute backend code. Grant access only to accounts and projects you are willing to let an assistant alter.

Installation

In SourceWeft

  1. Open Glide in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.glideapps%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "glide": {
      "type": "http",
      "url": "https://mcp.glideapps.dev/mcp"
    }
  }
}

README

Glide MCP Server

Connect your AI tools to Glide's official MCP server and build, manage, and operate GlideOS apps, data, and workflows — from Claude, Cursor, VS Code, Gemini CLI, ChatGPT, or any MCP client.

  • Endpoint: https://mcp.glideapps.dev/mcp (Streamable HTTP)
  • Authentication: OAuth 2.1 — sign in with your Glide account when your client prompts you; no API keys to manage. Access requires a Glide plan that includes the MCP server feature.
  • Documentation: https://www.glideapps.com/docs/os/mcp

What you can do

The server exposes Glide's full MCP tool surface, including:

  • Projects — create, list, and manage GlideOS projects
  • Apps — publish, promote, roll back, and manage app access and domains
  • Data — query and modify app databases, ingest data sources, manage backups
  • Workflows — run workflows, manage schedules, webhooks, and triggers
  • Files & code — read, write, and search project files; run backend code

Ask your AI tool things like:

"List my Glide projects"

"Create a new project called Inventory Tracker"

"Show me the tables in my app's database"

Setup

Claude Code

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

Claude (web and desktop)

Go to Settings → Connectors → Add custom connector and enter https://mcp.glideapps.dev/mcp.

Cursor

Install the Glide plugin from the Cursor Marketplace: open Settings → Plugins, search for Glide, and click Install. Or run /add-plugin glide in chat.

The plugin lives in plugins/glide and requires Cursor 3.13.0 or later.

To configure the MCP server manually instead:

[Install MCP Server]

Or add to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "glide": {      "type": "http",      "url": "https://mcp.glideapps.dev/mcp"    }  }}

Grok Build

The plugins/glide directory doubles as a Grok Build plugin: .grok-plugin/plugin.json, .mcp.json, and a glideos-development skill. Install it from Grok Build's plugin marketplace once the catalog entry is merged — see Listing in the xAI plugin marketplace.

VS Code

bash
code --add-mcp '{"name":"glide","type":"http","url":"https://mcp.glideapps.dev/mcp"}'

Gemini CLI

This repository is also a Gemini CLI extension:

bash
gemini extensions install https://github.com/glideapps/mcp

Then restart Gemini CLI.

ChatGPT

In Settings → Connectors, add a custom connector with the URL https://mcp.glideapps.dev/mcp (requires a ChatGPT plan with connector support).

Repository layout

This repo packages the same MCP server for several agent ecosystems:

PathFormatUsed by
.cursor-plugin/marketplace.json, plugins/glide/Cursor pluginCursor Marketplace
plugin.json, mcp.jsonAgent PluginAgent Plugin clients
plugins/glide/.grok-plugin/plugin.json, plugins/glide/.mcp.jsonGrok Build pluginGrok Build (xAI plugin marketplace)
gemini-extension.json, GEMINI.mdGemini CLI extensionGemini CLI

Validate the Cursor plugin manifests with:

bash
node scripts/validate-template.mjs

Listing in the xAI plugin marketplace

Grok Build installs plugins from xai-org/plugin-marketplace. Listing is one PR to that repo that adds a remote entry pointing at plugins/glide in this repo, pinned to an exact commit:

json
{  "name": "glide",  "description": "Glide's official MCP server. Build, manage, and operate GlideOS apps: create and manage projects, query and modify app databases, run workflows, publish and roll back apps, and read, write, and search project files.",  "category": "development",  "source": {    "source": "url",    "url": "https://github.com/glideapps/mcp.git",    "sha": "<40-character commit SHA>",    "path": "plugins/glide"  },  "homepage": "https://www.glideapps.com/docs/os/mcp",  "keywords": ["glide", "glideos", "glide apps", "glideapps"],  "domains": ["glideapps.com"]}

Get the commit to pin (a full 40-character lowercase SHA — branches, tags, and short SHAs are rejected):

bash
git ls-remote https://github.com/glideapps/mcp.git HEAD

Then, in a fork of the marketplace repo, add the entry to .grok-plugin/marketplace.json and run what CI runs before opening the PR:

bash
python3 scripts/generate-plugin-index.pypython3 scripts/validate-catalog.pypython3 scripts/generate-plugin-index.py --check

To ship a plugin update after this repo changes, bump the pinned sha in that entry and regenerate the index — don't open a second entry.

Support

License

MIT

Source: README.md at commit 51557fe

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts