glide-client.ts), and the Python thin wrapper (glide_client.py). Paste either file into your project to make every per-tool code example on this site runnable as-is — no extra dependencies beyond fetch (built-in) for TypeScript and httpx for Python.
curl reference
Every curl example on this site follows the same pattern:{category} with read, write, or treasury depending on the tool. The per-tool pages show which endpoint to use in each example.
Environment variable: Store your grant token in GLIDE_GRANT_TOKEN. Never hard-code tokens in scripts — they appear in shell history and process listings.
Content-Type: Always application/json. The server rejects requests without this header.
Idempotency key: For tools that require one (Idempotency key required: yes in the Metadata table), add the header:
params.idempotency_key for the tool to validate it end-to-end.
Base URL: The base URL is category-prefixed. Use https://mcp.glide.co/mcp/read for read tools, https://mcp.glide.co/mcp/write for write tools, and https://mcp.glide.co/mcp/treasury for treasury tools. Calling a tool on the wrong category endpoint returns a confused-deputy error. Each per-tool page shows the correct endpoint in its curl example.
TypeScript wrapper
Save asglide-client.ts in your project. Requires Node 18+ for native fetch.
TypeScript
TypeScript
Python wrapper
Save asglide_client.py. Requires httpx (pip install httpx).
Python
Python
Idempotency keys
Set an idempotency key on any tool call that can have side effects — payments, card issuance, scheduled transfers, beneficiary mutations, and yield allocations. The key ensures that retrying a failed request never double-executes the operation. When to set one:| Tool | Idempotency key required |
|---|---|
payments.initiate | yes |
cards.issue | yes |
transfer.schedule | yes |
x402.pay | yes |
yield.allocate | yes |
beneficiary.add | yes |
payroll.run | yes |
| All read tools | no |
agent.grant.issue | no |
killSwitch.all | no |
vault.rotateSigner | no |
payment-{orderId}, sched-payroll-{date}-{recipientId}, x402-{resourceHash}-{agentRunId}. UUIDs work but don’t survive process restarts without persistence.
Scope: Keys are scoped to (agent_principal_id, tool_name) — the same key is safe to reuse across different tools.
Reading list
- OAuth flow — how to obtain a grant token using
client_credentials. - Policy envelope — the policy contract the server enforces on every call.
- Step-up flow — the full biometric approval sequence for step-up gated tools.
- Receipts — the audit trail format for every money-moving tool call.
- All 22 tools — the complete tool reference table.