Build, manage, and operate Glide apps, projects, data, and workflows through Glide's hosted MCP server.

Use it from your agent

One ClawLink account serves every agent you run. Pick the guide for yours, or connect Glide once and call the same tools from all of them.

Glide for OpenClawInstall, pair, connect, first prompt

Glide for Hermes AgentInstall, pair, connect, first prompt MCPClaude Code, Cursor, any MCP clientCLI login or the remote MCP server

Setup

Connect Glide through ClawLink's hosted setup.

Auth: Browser login (OAuth), no API keys. The credential stays on the ClawLink server; your agent holds only a ClawLink key you can revoke.
Where: the ClawLink dashboard, or ask your agent to connect it.

What your agent can do

Glide exposes 124 tools through ClawLink. The 30 most used are listed here; your agent sees all of them.

Tool	What it does	Kind
`glide_mcp_ai_models_list`	List the AI models available to deployed apps that declare an `ai` binding	Read
`glide_mcp_ai_query_usage`	Query AI Gateway request logs for this project's deployed apps	Read
`glide_mcp_app_custom_domain_status`	Check the status of an app's custom domain: whether the SSL cert is active, still provisioning	Read
`glide_mcp_app_get`	Get details of a specific app by slug	Read
`glide_mcp_app_list`	List all apps for the project (deployed, pending, or errored — excludes deleted)	Read
`glide_mcp_app_list_versions`	Get version history for a deployed app	Read
`glide_mcp_app_request_read`	Make an authenticated HTTP request to THIS project's own app backend (the routes you write in	Read
`glide_mcp_app_runtime_errors`	Read build, client-runtime, and retained server-error history for this project	Read
`glide_mcp_auth_audit_query`	Query recent tool-dispatch audit rows for this project	Read
`glide_mcp_auth_audit_trace`	Fetch every audit entry sharing a given `traceId`, reconstructing one turn's full effect chain	Read
`glide_mcp_auth_check`	Dry-run an authorization check for the caller without executing anything	Read
`glide_mcp_auth_list_actions`	Introspect the project worker's tool registry — returns every registered tool with its	Read
`glide_mcp_auth_whoami`	Return the verified ActorContext for the caller — actorId, actorType, orgId, projectId	Read
`glide_mcp_billing_lookup`	Look up live Glide pricing and billing facts: the org's current plan and subscription, credit	Read
`glide_mcp_db_backup_connection`	Return a read-only connection string for a G3-managed backup branch	Read
`glide_mcp_db_backup_list`	List all G3-managed database backup branches for this project	Read
`glide_mcp_db_backup_status`	Show whether the project database is provisioned, the Neon history window, and the active branch	Read
`glide_mcp_db_get`	Get details for a single project database by name	Read
`glide_mcp_db_health`	Health check for the project database, read-only: compute size and suspend timeout, data size	Read
`glide_mcp_db_list`	List the databases provisioned for this project	Read
`glide_mcp_db_list_tables`	List all public tables and SQL views in the project's Postgres database (if provisioned)	Read
`glide_mcp_db_select`	Run a single read-only statement (`SELECT …` or `WITH … SELECT …`) against the project's	Read
`glide_mcp_file_history`	List the mutation history of workspace files — every write, edit, delete, move, and copy	Read
`glide_mcp_file_inspect`	Inspect a file from the workspace	Read
`glide_mcp_file_list`	List files in the project workspace	Read
`glide_mcp_file_read`	Read a file or directory from the project workspace	Read
`glide_mcp_file_search`	Search file contents in the project workspace using a text query	Read
`glide_mcp_file_stat`	Check whether a file exists in the project workspace and return its size in bytes	Read
`glide_mcp_get_workflow_run`	Inspect one workflow run — returns the run status, its `input` (the payload the run was	Read
`glide_mcp_get_workflow_step_output`	Read the FULL value of one workflow step's output — the run's final output, or the run's INPUT	Read