Glide MCP server

Which servers in the official MCP registry are Glide's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Glide

Whose server it is

Registry nameco.glide/banking-connectorverified in the MCP registry

The registry name sits under glide.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools4
Server calls itselfglide-banking-connector
Server version1.1.0
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 77 ms.

Tools it offers4 tools · read 2026-10-13

create_account
Sign in to Glide with a verified email and supply the Privy access token in the Authorization: Bearer header to open or reconnect your account. Returns your wallets immediately — Base and Solana, both able to receive USDC and both…
check_status
Where the person is in bank verification: awaiting_verification, in_review, approved, declined or unavailable (temporarily unavailable — tell them to contact support, do not speculate why). Call this after they open the verification link…
get_funding_details
The US bank account — account number and routing number — plus the USDC address on Base. This is the banking half, so it needs verification to be approved; before that it refuses. On and off ramps are free. For a wallet address that works…
get_wallets
The person's Base and Solana wallet addresses, plus the x402 endpoint on each chain that lets any agent pay them in USDC. Works from the moment the account exists: no verification, no fee, nothing to set up. Receiving is free and…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "banking-connector": {
      "type": "http",
      "url": "https://glide.co/api/connector/mcp"
    }
  }
}

OpenAPI spec

3 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.