Skip to main content

Documentation Index

Fetch the complete documentation index at: https://glide-9da73dea.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Glide implements the open Model Context Protocol (MCP) for agent banking. That means a single Glide skill works across every MCP-compliant runtime — you install once, you run anywhere.

​
Currently supported

Claude Desktop

Anthropic’s official desktop client. The simplest setup; native MCP support. See the quickstart for the JSON config.

ChatGPT Apps

OpenAI’s app surface. Glide is a published ChatGPT App; install from the Apps catalog and approve the Glide tool list.

Google Vertex

Google Cloud’s agent runtime. Add Glide as an external tool source in your Vertex agent configuration.

OpenClaw

The open-source agent orchestrator. Configure Glide as an MCP server in your OpenClaw runtime config.

Hermes

Hermes-based agent runtime. Glide’s MCP endpoints work directly via Hermes’s standard tool integration.

​
Same skill, every runtime

When you install a Glide skill, the install is bound to your account, not to a specific runtime. The OAuth grant, the policy envelope, the audit feed — all live on Glide. The runtime is just the chat surface where you talk to the agent. That means:
  • Install the AP agent skill once.
  • Use it in Claude Desktop on your laptop.
  • Use it in ChatGPT Apps on your phone.
  • Use it in Google Vertex from a teammate’s instance.
  • Every call lands in the same audit feed.
  • Every step-up appears in the same dashboard.
If you replace one runtime with another, your skill keeps working. There’s no re-onboarding cost when AI surfaces shift.

​
Runtime-specific install instructions

​
Claude Desktop

{
  "mcpServers": {
    "glide": {
      "url": "https://mcp.glide.co",
      "auth": {
        "clientId": "<from-skill-install>",
        "clientSecret": "<from-skill-install>"
      }
    }
  }
}
Add this to your Claude Desktop config under Settings → Developer → Edit Config. Restart Claude Desktop.

​
ChatGPT Apps

In ChatGPT, go to Settings → Apps → Add app. Search for “Glide.” Approve the Glide tool list when prompted; the OAuth handoff completes inside the app sheet.

​
Google Vertex

In your Vertex agent config, add Glide as an external tool source: 
tools:
  - source: mcp
    url: https://mcp.glide.co
    auth:
      type: oauth_2.1
      client_id: <from-skill-install>
      client_secret: <from-skill-install>
      authorization_server: https://auth.glide.co

​
OpenClaw

In your OpenClaw runtime config: 
mcp_servers:
  - name: glide
    transport:
      type: http
      url: https://mcp.glide.co
    auth:
      type: oauth
      client_id: <from-skill-install>
      client_secret: <from-skill-install>

​
Hermes

Glide’s MCP endpoint works as a standard Hermes tool source. Use the same URL and OAuth client credentials Glide showed you at skill install time.

​
Runtime feature differences

Most runtimes support every Glide tool. A few feature-level differences worth knowing:
FeatureClaudeChatGPTVertexOpenClawHermes
Inline step-up promptsYesYesYesYesYes
URL-mode step-up fallbackn/an/an/ayesyes
Voice-mode tool callsn/aYesn/aYesn/a
Long-context skill chainingYesPartialYesYesYes
URL-mode step-up is used when the runtime can’t render an interactive prompt — you tap a link to approve in the Glide dashboard or app instead.

​
Adding a new runtime

If you’re using an MCP-compliant runtime that’s not on this list, Glide’s MCP endpoints are public-spec. Configure your runtime to point at https://mcp.glide.co with OAuth 2.1 + PKCE; everything else follows the standard. If you’re building a runtime and want to make sure Glide skills work first-class on it, talk to us at hi@glide.co.

​
Next