Glideapps MCP server
{
"mcpServers": {
"glideapps": {
"type": "http",
"url": "https://mcp.glideapps.dev/mcp"
}
}
}{
"mcpServers": {
"glideapps": {
"type": "http",
"url": "https://mcp.glideapps.dev/mcp"
}
}
}{
"mcpServers": {
"glideapps": {
"type": "http",
"url": "https://mcp.glideapps.dev/mcp"
}
}
}{
"servers": {
"glideapps": {
"type": "http",
"url": "https://mcp.glideapps.dev/mcp"
}
}
}{
"mcpServers": {
"glideapps": {
"type": "http",
"url": "https://mcp.glideapps.dev/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.1
What it does
Glide's official MCP server lets you build, manage, and operate GlideOS apps and workflows from AI tools like Claude, Cursor, and VS Code. It uses OAuth authentication with your Glide account and requires a Glide plan that includes MCP server access.
- List, create, and manage GlideOS projects from your AI assistant.
- Query and modify app databases, manage data sources, and handle backups programmatically.
- Run workflows, manage schedules, webhooks, and triggers, and publish or roll back app versions.
Tools this server exposes
| Tool | Does |
|---|---|
| create_project | Create a new GlideOS project. |
| list_projects | List all GlideOS projects. |
| manage_apps | Publish, promote, roll back, and manage app access and domains. |
| query_database | Query app databases and retrieve table data. |
| modify_data | Modify app database records and manage data sources. |
| manage_backups | Manage database backups. |
| run_workflows | Execute workflows from the MCP server. |
| manage_schedules | Manage workflow schedules, webhooks, and triggers. |
| read_files | Read project files and code. |
| write_files | Write and modify project files. |
| search_files | Search project files. |
| run_backend_code | Execute backend code in projects. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.