Glide MCP

Tools

• Add app assets

  Promote user attachments into the project's public app-asset storage and return an app-local path — `/assets/<sha256>/<filename>` — for each. Use that value as-is in `src` / `href`: it resolves on the app's own origin, so it survives a clon

• Ai models list

  List the AI models available to deployed apps that declare an `ai` binding. Each entry returns an `id`, a provider, and a tier. Pass the `id` verbatim — the compound `provider/model` form (e.g. anthropic/claude-haiku-4-5). Default to anthro

• Ai query usage

  Query AI Gateway request logs for this project's deployed apps. Returns recent calls made through the `ai` binding — model, provider, success, tokens, cost, duration — with per-app attribution via metadata. Useful for diagnosing customer AI

• App authenticated link

  Create a pre-authenticated link to an app. Use this to test/verify/screenshot.

• App bind custom domain

  Bind a custom domain to a published app (e.g. `mycoolapp.dev` or `app.example.com`). Platform subdomains (*.glideapps.dev, *.glideos.app, etc.) are not allowed — use app_claim_vanity_slug instead. Registers the hostname with Cloudflare for

• App claim vanity slug

  Claim a globally unique vanity subdomain for an app (e.g. `myapp.glideapps.dev`). The slug must follow DNS naming rules and be unique across all organizations.

• App custom domain status

  Check the status of an app's custom domain: whether the SSL cert is active, still provisioning, or blocked. When blocked, returns the exact issue (commonly the customer's DNS CAA records not permitting the issuing CA — the message says whic

• App delete

  destructive

  Delete an app. Soft-deletes the app record, removes the deployed worker (or dispatch-namespace script), and clears the production KV route. Best-effort cleanup — missing CF resources are ignored.

• App get

  Get details of a specific app by slug. Returns user-facing name, latest deploy description, URL, status, version, script name, bindings, and timestamps.

• App list

  List all apps for the project (deployed, pending, or errored — excludes deleted). Each app includes app slug, user-facing name, latest deploy description, deployed URL, status, version, script name, and bindings.

• App list versions

  Get version history for a deployed app. Shows all past deploys with version numbers, titles/descriptions, and URLs.

• App promote

  Promote a specific version of an app to production. Verifies the target version script exists in the dispatch namespace, updates the production KV pointer, and updates the app's production URL.

• App publish

  Promote a version of an app to production. After update_preview succeeds, pass its returned publishable content hash as this tool's `version`. Only available when Workers for Platforms is configured.

• App release vanity slug

  Release a vanity subdomain so it can be claimed by another app. The app's long-form production URL continues to work.

• App request read

  Make an authenticated HTTP request to THIS project's own app backend (the routes you write in server.ts) and get the response back — use it to verify an endpoint returns what you expect, walk a multi-step flow, or build a test suite against

• App request write

  Make an authenticated HTTP request to THIS project's own app backend (the routes you write in server.ts) and get the response back — use it to verify an endpoint returns what you expect, walk a multi-step flow, or build a test suite against

• App rollback

  Roll an app back to a previous version. The target version must already exist in the app's version history. Updates the app record + production KV pointer so the public URL serves the older build. IMPORTANT: this changes ONLY what productio

• App runtime errors

  Read build, client-runtime, and retained server-error history for this project. Read the top-level `verificationStatus` first: it is the canonical, server-authored interpretation of the current preview's build, reachability, and exact-versi

• App set access

  Set the app's access level — the same setting the user sees in the Share dialog. When you describe org access to the user, always call it their "Glide org" / "Glide organization", never a bare "org". Three options: `org-member` = "Members w

• App set icon

  Set the icon for one of the project's apps. Provide `name` (the app to retint) and EITHER a short `description` of what the icon should evoke — e.g. 'task tracker', 'expense reports', 'rocket' — OR `path` (the `attachments/...` path of an i

• App set name

  Rename an app's user-facing name when the user explicitly asks to rename it. This does not change the app slug, dispatch script names, or production URLs.

• App set presentation

  Set how one of the project's apps presents itself when installed, shared, or indexed: the web-manifest and <head> fields the platform otherwise fills with defaults. Pass `name` (the app) and `presentation`, a partial object — only the field

• App unbind custom domain

  Unbind a custom domain from an app. Removes the CF for SaaS hostname registration, deletes the KV routing pointer, and clears the domain from the app. The app's production URL and any vanity URL continue to work.

• Auth audit query

  Query recent tool-dispatch audit rows for this project. Every mutating tool call (and every denied call of any kind) produces an audit entry with the verified actor, delegation chain, traceId, decisionId, and truncated input/result. Javascr

• Auth audit trace

  Fetch every audit entry sharing a given `traceId`, reconstructing one turn's full effect chain. A traceId is carried end-to-end on every ActorContext, so this surfaces every tool the agent called on behalf of a user within a single chat tur

• Auth check

  Dry-run an authorization check for the caller without executing anything. Returns `{ allowed, decisionId, reason? }` — same shape the registry's dispatch() uses to gate every tool call. Useful for 'can I do X?' questions ahead of time, and

• Auth list actions

  Introspect the project worker's tool registry — returns every registered tool with its authz-relevant metadata: name, domain, scope, readOnly, destructive, idempotent, supportsDryRun, and whether it declares a custom `authz.action`/`authz.r

• Auth whoami

  Return the verified ActorContext for the caller — actorId, actorType, orgId, projectId, delegation chain (if any), and correlation IDs (requestId, traceId) — enriched with the organization name from project metadata. Use this to confirm a t

• Bash

  Run a short Bash script in a sandboxed shell. Use this for shell-style text and data work: pipes, heredocs, grep/sed/awk/jq, sorting, diffs, checksums, zip/unzip for .zip archives, and quick text/CSV/JSON transforms. The bundled `zip` / `

• Billing lookup

  Look up live Glide pricing and billing facts: the org's current plan and subscription, credit balance and quota usage, the full plan catalog with current prices, per-plan baseline features, and the official billing/credits docs. Call this f

• Cancel workflow run

  Stop an in-flight workflow run (running / paused / waiting) by its run id — the same Stop the dashboard offers. Terminates execution at the current step; completed steps are NOT rolled back, and a finished run (complete / errored / stopped)

• Create workflow app trigger

  Register that a deployed app in this project may start a workflow from its own server code — the way a button in the app kicks off a run. Then the app's server route calls `workflows(c.env).start("<workflow slug>", { data })` from the injec

• Create workflow data trigger

  Start a workflow whenever rows in one of this project's tables are inserted, updated or deleted — by the app's users (a form submit), in the Data Editor, by agent SQL, or by another workflow. The run gets the change as `event.payload.change

• Create workflow schedule

  Schedule a deployed workflow to run automatically — either RECURRING or ONE-TIME. Use this after the workflow is deployed; actually create the schedule, do NOT just tell the user how. Provide EXACTLY ONE of: `cron` (recurring), `delaySecond

• Create workflow webhook

  Give a deployed workflow a PUBLIC URL that an external POST fires a run on — for EXTERNAL systems only (Stripe, Zapier, partner callbacks, curl). An app in THIS project must NEVER call the webhook: a deployed app's server code cannot reach

• Db backup connection

  Return a read-only connection string for a G3-managed backup branch. Requires editor access even though the branch endpoint is read-only.

• Db backup create

  Create a read-only backup branch from a timestamp or Postgres LSN within the Neon history window.

• Db backup delete

  destructive

  Delete a G3-managed database backup branch. Refuses non-G3 branches and the active branch.

• Db backup list

  List all G3-managed database backup branches for this project. Backup metadata is parsed from branch names.

• Db backup status

  Show whether the project database is provisioned, the Neon history window, and the active branch.

• Db compute

  Read or change the project database's compute ceiling. With no input it reports the current autoscaling range (min and max CU), the suspend timeout, the compute state, and the largest ceiling this organization's plan allows. With maxCu it r

• Db execute

  Run any SQL statement against the project's Postgres database — SELECT, INSERT, UPDATE, DELETE, or DDL. When creating or materially changing a table or view, also add/update a Postgres relation comment with COMMENT ON TABLE or COMMENT ON VI

• Db get

  Get details for a single project database by name. Returns engine, provisioning state, and Neon project ID. Does not return the connection string — that stays inside the worker.

• Db health

  Health check for the project database, read-only: compute size and suspend timeout, data size, largest tables, tables read by full scans, dead-row bloat, open connections against the limit, the slowest statements when statistics are availab

• Db ingest data source

  Bulk-load a CSV/JSON/XLSX attachment into a Postgres table in one step. The destination table must already exist — create it first with db_execute. `columns` is REQUIRED and acts as the inclusion list: only source columns named as keys in t

• Db list

  List the databases provisioned for this project. Each project currently has at most one Neon Postgres database (`project-db`), auto-provisioned on first deploy; the return shape is an array to stay forward-compatible with multi-DB projects.

• Db list tables

  List all public tables and SQL views in the project's Postgres database (if provisioned), including relation comments plus column schemas or view definitions. Prefer relevant views over raw tables when building read-only screens.

• Db restore from backup

  Restore the live project database from a G3-managed backup branch. The current state is first preserved as a backup branch.

• Db restore to point

  Restore the live project database to a timestamp or LSN. The current state is first preserved as a backup branch.

• Db select

  Run a single read-only statement (`SELECT …` or `WITH … SELECT …`) against the project's Postgres database, inside a `SET TRANSACTION READ ONLY` envelope. Use this for dashboard questions, summaries, comparisons, charts, and analysis that n

Works well with

How Switchy teams use it

Starter prompts

More developer tools MCPs

• GongGong
• Google Address ValidationGoogle Address Validation
• Google AnalyticsGoogle Analytics
• Google PhotosGoogle Photos
• Google Search ConsoleGoogle Search Console
• GosquaredGosquared
• GrafanaGrafana
• GrafbaseGrafbase
• GTmetrixGTmetrix
• GustoGusto
• HackerRank WorkHackerRank Work
• HarnessHarness

See all developer tools MCPs →