The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Glide listing page.
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.
https://mcp.glideapps.dev/mcp (Streamable HTTP)The server exposes Glide's full MCP tool surface, including:
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"
Go to Settings → Connectors → Add custom connector and enter https://mcp.glideapps.dev/mcp.
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:
Or add to ~/.cursor/mcp.json:
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.
This repository is also a Gemini CLI extension:
Then restart Gemini CLI.
In Settings → Connectors, add a custom connector with the URL https://mcp.glideapps.dev/mcp (requires a ChatGPT plan with connector support).
This repo packages the same MCP server for several agent ecosystems:
| Path | Format | Used by |
|---|---|---|
.cursor-plugin/marketplace.json, plugins/glide/ | Cursor plugin | Cursor Marketplace |
plugin.json, mcp.json | Agent Plugin | Agent Plugin clients |
plugins/glide/.grok-plugin/plugin.json, plugins/glide/.mcp.json | Grok Build plugin | Grok Build (xAI plugin marketplace) |
gemini-extension.json, GEMINI.md | Gemini CLI extension | Gemini CLI |
Validate the Cursor plugin manifests with:
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:
Get the commit to pin (a full 40-character lowercase SHA — branches, tags, and short SHAs are rejected):
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:
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.
MIT