Glide MCP integration
Developer tools connector, available on Zeplik
Glide MCP is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Glide MCP and Zeplik can act on your software development for you: Build, manage, and operate Glide apps, projects, data, and workflows through Glide's hosted MCP server. You stay in the conversation while the assistant does the work in Glide MCP directly.
Zeplik exposes 10 read actions and 90 write actions for Glide MCP. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Glide MCP without your consent.
Try Glide MCP on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
What Zeplik can do with Glide MCP
Read from Glide MCP (10)
Runs automatically in any conversation.
Get workflow run
Inspect one workflow run — returns the run status, its `input` (the payload the run was triggered with — `event.payload` in the workflow's run(event, step); for a trigger this is `{ triggerSlug, toolkit, data }`, i.e. WHICH event fired and the provider's raw event data, so you can see what message/record came in), the run-level error, a `failedSteps` summary, and every step's success + error (with retry-attempt count) AND a bounded preview of each step's output value plus the run's final output. This is the only way to see why a step failed (run errors are recorded only here, never in the logs), what triggered the run, and what each step returned. Values are previewed (large ones are summarized — `inputTruncated`/`outputTruncated` flag this, `inputBytes`/`outputBytes` give the full size; `*Unparsed` means the engine cut a value off mid-JSON so it's incomplete); call get_workflow_step_output to read a full / specific value (pass `runInput: true` for the full input). Get the run id from list_workflow_runs.
Get workflow step output
Read the FULL value of one workflow step's output — the run's final output, or the run's INPUT (the trigger payload / `event.payload`; pass `runInput: true`) — when get_workflow_run's bounded preview wasn't enough (e.g. a trigger's raw `data` was clamped). Pass the runId and the step's `name` (from get_workflow_run); omit `stepName` and `runInput` to get the run's final output. Pass an optional `path` (e.g. `[0]`, `rows[0].id`, `data.transactions[2].merchant`) to drill into a specific part of a large value. The result is still size-capped — if it reports `truncated`, narrow the `path`.
List active triggers
List this project's LIVE integration triggers (the ones enable_trigger created) — each with its `triggerId` (needed for set_trigger_enabled / delete_trigger), toolkit, trigger slug, config filters, title, enabled state, and the workflow it starts. Call this before changing or removing a trigger, and to answer "what triggers does this workflow have?". Distinct from list_triggers, which is the CATALOG of available trigger types for a toolkit.
List triggers
List the event triggers available for a connected toolkit — call this to find the exact trigger slug BEFORE enable_trigger. Returns `[{ slug, name, description, payload, config }]`: `description` is what the trigger fires on (pick by this — don't guess from the slug), `payload` is the JSON Schema of the event, which your workflow's `event.payload.data` matches — read the right fields up front instead of deploying a probe — and `config` is the JSON Schema of the trigger's UPSTREAM FILTERS (e.g. Slack's `channel_id`, `is_bot_message`): read it, elicit the filter values from the user, and pass them as enable_trigger's `config` so non-matching events never start a run at all (no billed steps, no run-history noise). Deprecated triggers are hidden. Triggers are a separate catalog from actions: integration_search does NOT return them, so never guess a trigger slug. The result also carries the toolkit's Glide `guidance` — follow it for how this service's triggers behave. Use the toolkit you connected.
List workflow app triggers
List this project's app triggers — each with its id, the UI app that fires it, the workflow it starts, its label, and enabled state. Pass `appName` to scope to one UI app, or omit for all.
List workflow apps
List this project's workflows with their WORKFLOW-LEVEL enabled state — the app master switch (set_workflow_enabled) that decides whether the workflow runs at all. Use THIS to answer 'is this workflow enabled / running?'. A workflow only runs when `enabled` is true here; a schedule or webhook trigger being enabled does NOT mean the workflow runs — the app switch must be on too (do not infer workflow state from list_workflow_schedules). When `enabled` is false, `disabledReason` says why: 'manual' (turned off), 'plan_limit' (a draft over the org's plan limit — enabling needs a slot freed or an upgrade), or 'error_loop' (auto-disabled after repeated failures).
List workflow data triggers
List this project's data triggers — each with its id, the workflow it starts, the table and changes it watches, its label, and whether it is on. Pass `workflowName` to scope to one workflow.
List workflow runs
List recent runs of this project's workflows — each with its run id, status (complete / errored / running / paused / …), source, and a top-level error if any. Use this to find a failed run, then call get_workflow_run with its id to see which step failed and why. Pass appName to scope to a single workflow.
List workflow schedules
List cron schedules for this project's workflows — each with its id (needed to pause or remove it), cron, timezone (null = UTC), enabled state, and next fire time. Pass `appName` to scope to one workflow, or omit for all. A schedule's `enabled` is the SCHEDULE's own on/off, NOT the workflow's: a workflow with an enabled schedule still won't run if the workflow itself is disabled. To check whether a workflow is enabled/running, use list_workflow_apps.
List workflow webhooks
List this project's workflow webhook triggers — each with its id (needed to rotate/enable/delete it), label, enabled state, and URL. Pass `appName` to scope to one workflow, or omit for all.
Act in Glide MCP (90)
Runs only after you enable write access.
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 clone or a change of asset origin untouched. To read one from SERVER code, `import { assets } from "./assets"` (server-only — importing it from client code fails the build) and call `assets(env).fetch(<that same app-local path>)` — never construct or fetch the canonical app-assets URL, which is refused without the helper's capability. Pass an `assets` array; a single upload is just an array of one, and a 93-image batch is a single call. Each path is content-addressed, immutable, and cached for a year. 100 MB each. Images, audio and video whose bytes match a known container (PNG/JPEG/WEBP/GIF, MP3/WAV/FLAC/OGG/M4A, MP4/MOV/WebM) are served under their real content type; anything else is served as generic binary, which a browser will download rather than play. Every asset is stored with a visibility class — see `visibility`, which defaults to `private`; only mark bytes `public` when they are meant to be world-readable forever. Returns `{ results }` — one entry per input asset, in order: a success is `{ path, id, url, sha256, bytes, alreadyExisted }` (`url` is that app-local path), a failure is `{ path, error }`. One bad file does NOT fail the rest of the batch. WIRING ASSETS TO DATA ROWS: when each asset belongs to a record in a table (one asset per record), set `writeUrlsToTable` and give each asset a `row: { key, column }`. The worker then writes every resulting app-local path straight into the table — do NOT, and do not need to, follow up with a `db_execute` UPDATE to store them. Emitting dozens of long content-addressed references as inline SQL is slow and burns output tokens; let this tool bind them server-side instead. What lands in the column is a PATH, not an absolute URL, so it resolves only on the app's own origin — anything reading those columns from outside the app (an export, a webhook payload) must join it to the app's origin itself.
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 anthropic/claude-sonnet-4-6 unless you have a reason otherwise. Load the `ai` skill for the call patterns (`complete()`, `stream().toResponse()`), the server-side-only boundary, and the build-fail anti-patterns.
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 binding issues (401s, rate limits, unexpected models, quota consumption). Results are scoped to this project by filtering on metadata.projectId, so it never leaks other projects' usage. Requires CF_API_TOKEN to have the 'AI Gateway Read' permission.
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 SaaS, writes the KV routing pointer, and stores the domain on the app. The customer must point a CNAME at the platform's custom hostname target for SSL to provision. BEFORE the first bind of a domain, the customer must also PROVE they control it by publishing a TXT record at `_glide-verify.<hostname>` (the required value is derived per organization). Without it the bind is refused with `code: "ownership_unverified"` and a `verification` object naming the exact record — relay those values to the user and wait for them to publish the record; do NOT retry blindly, retries cannot succeed until the record is live. `code: "ownership_check_unavailable"` means DNS could not be reached and IS worth retrying.
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 which authority to allow). Use this to answer "is my domain live yet?" or to diagnose why a bound custom domain isn't working.
App delete
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 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.
and 78 more.
How to connect Glide MCP
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Glide MCP immediately.
Connect Glide MCP
Open Settings and go to Connectors, then press Connect on Glide MCP. You can also connect from the Glide MCP page in the app.
Approve access to Glide MCP
Approve access on Glide MCP's secure consent screen. You are returned to Zeplik and can start giving instructions that use Glide MCP.
Frequently asked questions
- Can I use Glide MCP with Zeplik?
- Yes. Glide MCP is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Glide MCP account inside any conversation.
- What can Zeplik do with Glide MCP?
- Once connected, Zeplik has 10 read and 90 write actions for Glide MCP. Build, manage, and operate Glide apps, projects, data, and workflows through Glide's hosted MCP server.
- How do I connect Glide MCP to Zeplik?
- You connect Glide MCP with a secure one-click sign-in (OAuth): press Connect in Settings under Connectors and approve access on Glide MCP's consent screen.
- Does Zeplik change things in Glide MCP without asking?
- No. Zeplik reads from Glide MCP by default. Any action that changes data in Glide MCP requires write access, which stays off until you enable it in Settings under Connectors.
- How much does connecting Glide MCP cost?
- Connecting Glide MCP is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.
Related developer tools integrations
- GlobalpingGlobalping is a global network of probes that allows users to run network tests like ping, traceroute, and DNS resolve from various locations.
- Google Address ValidationThe Address Validation API allows developers to verify the accuracy of addresses by validating and standardizing them, and determining their geocode.
- Google MapsIntegrate Google Maps to access location data, geocoding, directions, and mapping services in your application.
- GrafanaOpen and composable observability platform for metrics, logs, and traces
- GrafbaseGrafbase is a platform that accelerates the development of GraphQL APIs, offering features like edge caching, unified data access, and seamless.
- GraphHopperGraphHopper Directions API provides enterprise-grade routing services, including route planning, optimization, geocoding, and more, for various.
More on Zeplik
Connect Glide MCP to your AI assistant
Every model, one chat. Bring Glide MCP into Zeplik and let the assistant do the work.