Glide's official MCP server — build, manage, and operate GlideOS apps, data, and workflows.
One address for any MCP client. You sign in once, after adding it.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Odel could not list its tools without signing in.
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"
claude mcp add --transport http glide https://mcp.glideapps.dev/mcp
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:
{
"mcpServers": {
"glide": {
"type": "http",
"url": "https://mcp.glideapps.dev/mcp"
}
}
}
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.
code --add-mcp '{"name":"glide","type":"http","url":"https://mcp.glideapps.dev/mcp"}'
This repository is also a Gemini CLI extension:
gemini extensions install https://github.com/glideapps/mcp
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:
node scripts/validate-template.mjs
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:
{
"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):
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:
python3 scripts/generate-plugin-index.py
python3 scripts/validate-catalog.py
python3 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.
MIT