Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Glide's official MCP server — build, manage, and operate GlideOS apps, data, and workflows.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.glideapps.dev/mcp在终端中运行这条命令
claude mcp add --transport http glideapps https://mcp.glideapps.dev/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"glideapps": {
"url": "https://mcp.glideapps.dev/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"glideapps": {
"type": "http",
"url": "https://mcp.glideapps.dev/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.glideapps.dev/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 glideapps.dev 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Apify MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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