Skip to main content
No SDK, no build step. This recipe uses curl and jq to call the Glide MCP gateway directly. You will authenticate with an HMAC-signed JWT, call payments.initiate, and inspect the returned receipt. Audience: backend engineers evaluating Glide before committing to an SDK.

Prerequisites

  • curl and jq installed (brew install jq on macOS).
  • Glide running locally per the main quickstart, or access to a hosted Glide instance.
  • A dev secret: MCP_TOKEN_VERIFIER_DEV_SECRET set in your environment (32-byte hex string).
If you haven’t set a dev secret yet, generate one now:

Steps

1. Set environment variables

2. Mint a short-lived dev JWT

The dev verifier accepts HMAC-SHA256 JWTs signed with the shared secret. Use the glide CLI to mint one:
In production, tokens come from your Ory Hydra deployment via client_credentials. See the OAuth flow for the full RFC 7591 walk-through.

3. Verify the gateway is reachable

Expected output:

4. Inspect available tools

Expected output (abbreviated):

5. Check an account balance

6. Initiate a payment

7. Parse the receipt

A successful call returns a Receipt object:
The txHash field is the on-chain transaction hash. You can verify it independently at basescan.org/tx/<txHash>.

Run it

The full sequence above as a single script:
Expected stdout:

Extend it

  • Add --header "Idempotency-Key: ..." to make the payment call safe to retry.
  • Pipe the receiptId into audit.stream to watch event delivery in real time.
  • Replace the HMAC dev token with a production Ory JWT — no other change needed.
  • Wire the receipt into a Slack webhook for payment confirmation alerts.
  • Try a call that should fail policy (amount above cap) and inspect the -32003 error body.

Source

github.com/darshanbathija/axtior-neobank/tree/main/examples/curl-quickstart

Reading list