Connect Glide to an assistant
Use a Glide MCP connection to read your personal account balances, look up an existing transaction, and check verification or payment status. This connection reads information. It cannot send funds, execute a conversion, trade assets, or reveal full card numbers.
Before you connect
You need a Glide account. Sign in and explicitly approve read access to your personal account; business accounts are excluded. The connection requires the accounts:read permission. Available results depend on your account access and existing records.
Set up the connection
- In your assistant's connector settings, add a custom remote MCP connection named Glide using this URL:
https://mcp.glide.co/mcp/directory - Follow the sign-in and consent flow for your Glide account and approve read access to your personal account. Keep passwords and tokens out of chat messages.
- Enable Glide in the conversation and ask for your personal account balances. In Claude, choose Register automatically for the OAuth client.
If your assistant does not offer custom connections or Glide sign-in does not complete, contact support.
Connect from Codex or Claude Code
codex mcp add glide --url https://mcp.glide.co/mcp/directory
codex mcp login glide
# Or ~/.codex/config.toml
[mcp_servers.glide]
url = "https://mcp.glide.co/mcp/directory"
# Claude Code
claude mcp add --transport http glide https://mcp.glide.co/mcp/directoryComplete browser sign-in and approve accounts:read. In Claude Code, open /mcp to connect.
Try these prompts
- List my personal Glide accounts and available balances.
- Show my pending account balances.
- What is my identity verification status in Glide?
To look up a transaction or payment, provide its Glide transaction ID. A missing record does not mean a payment was sent or settled.
Your data and access
Your assistant receives the information returned by the tools you use. See our privacy policy, data retention policy, and terms. Disconnect Glide in your assistant's settings to stop using the connection. Revoke its grant inConnect with your agent to immediately stop access and refresh.
For the broader developer interfaces, see the headless setup guide and tool reference.