Non-custodial Pix payment gateway on Liquid: checkouts, products, status reads, and support tickets.
Connect DePix Gateway to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Non-custodial Pix payment gateway on Liquid: checkouts, products, status reads, and support tickets. The depix gateway mcp server is what makes that connection.
The MCP (Model Context Protocol) server for DePix App — the agent-facing interface of the non-custodial Pix↔DePix payment gateway and of a non-custodial Liquid wallet.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
create_checkout — POST /api/checkoutsget_checkout — GET /api/checkouts/:idlist_checkouts — GET /api/checkoutssimulate_checkout_payment — POST /api/checkouts/:id/simulate-paymentwait_for_checkout — GET /api/checkouts/:id (server-side loop)create_product — POST /api/productslist_products — GET /api/productsget_product — GET /api/products/:idupdate_product — PATCH /api/products/:idactivate_product — POST /api/products/:id/activatedeactivate_product — POST /api/products/:id/deactivateset_featured_products — POST /api/products/featuredConfiguration is passed through the environment: DEPIX_API_KEY, DEPIX_WALLET_PASSPHRASE, DEPIX_WALLET_DIR, DEPIX_TEST_KEY, VERCEL_URL, VERCEL_BRANCH_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. DePix Gateway's toolset — create_checkout, get_checkout, list_checkouts and 11 more — is a fair guide to whether it matches your workflow. It is maintained by depixapp; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| create_checkout | POST /api/checkouts |
| get_checkout | GET /api/checkouts/:id |
| list_checkouts | GET /api/checkouts |
| simulate_checkout_payment | POST /api/checkouts/:id/simulate-payment |
| wait_for_checkout | GET /api/checkouts/:id (server-side loop) |
| create_product | POST /api/products |
| list_products | GET /api/products |
| get_product | GET /api/products/:id |
| update_product | PATCH /api/products/:id |
| activate_product | POST /api/products/:id/activate |
| deactivate_product | POST /api/products/:id/deactivate |
| set_featured_products | POST /api/products/featured |
| list_product_checkouts | GET /api/products/:id/checkouts |
| get_account | GET /api/me |
{
"mcpServers": {
"depix": {
"command": "npx",
"args": ["-y", "@depixapp/mcp"],
"env": { "DEPIX_API_KEY": "sk_test_YOUR_KEY" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DEPIX_API_KEY | Credential the server authenticates with. | Yes |
| DEPIX_WALLET_PASSPHRASE | Configuration value read at startup. | Optional |
| DEPIX_WALLET_DIR | Filesystem location the server is allowed to use. | Optional |
| DEPIX_TEST_KEY | Credential the server authenticates with. | Yes |
| VERCEL_URL | Endpoint or connection string the server talks to. | Yes |
| VERCEL_BRANCH_URL | Endpoint or connection string the server talks to. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.