Juspay’s MCP integrations connect assistants to payment operations and merchant dashboard tools through distinct credential paths.
Juspay’s MCP integrations connect assistants to payment operations and merchant dashboard tools through distinct credential paths.
The Juspay repository contains a Payments server for orders, transactions, refunds, customers and cards, and a Dashboard server for gateways, reports, analytics and payment links. These are different tool surfaces. Choose the integration that matches the work and use the credentials documented for that surface.
Payments can run locally through the published Docker image with a merchant API key, merchant ID and selected environment. Dashboard has a Juspay-hosted HTTP endpoint and browser OAuth, with a Docker stdio option for clients that cannot use the remote connection. The setup tabs below preserve these distinct paths.
For Payments, retrieve an order’s status in a sandbox account before testing a state-changing action. For Dashboard, request a configured gateway or a report visible to the signed-in merchant. Compare returned identifiers and values with the merchant portal rather than relying on the assistant’s summary.
Python source deployment has its own runtime requirements; Docker supplies the packaged route. Payment actions and dashboard administration can affect a merchant account, so expose only the needed surface and retain the resulting tool trace. A successful MCP connection establishes access, not permission to apply every payment operation automatically.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| order_status_api_juspay | Retrieve order status through the Payments server. |
| create_order_juspay | Create a payment order in the selected environment. |
| create_refund_juspay | Request a refund through Payments. |
| list_configured_gateway | List configured gateways through Dashboard. |
| q_api | Run Dashboard analytics queries. |
{
"mcpServers": {
"juspay-mcp": {
"command": "docker",
"args": [
"run",
"--pull=always",
"--rm",
"-i",
"-e",
"JUSPAY_API_KEY",
"-e",
"JUSPAY_MERCHANT_ID",
"-e",
"JUSPAY_ENV",
"juspaydotin/juspay-mcp:latest"
],
"env": {
"JUSPAY_API_KEY": "YOUR_JUSPAY_API_KEY",
"JUSPAY_MERCHANT_ID": "YOUR_MERCHANT_ID",
"JUSPAY_ENV": "sandbox"
}
}
}
}Replace credentials and retain sandbox for the first trial.
A Juspay merchant account and credentials. Docker for the packaged stdio route, or an HTTP MCP client with OAuth for Dashboard.
| Variable | Description | Required |
|---|---|---|
| JUSPAY_API_KEY | Payments API key for the selected merchant environment. | Yes |
| JUSPAY_MERCHANT_ID | Merchant identifier for Payments. | Yes |
| JUSPAY_ENV | Payments environment; use sandbox for a first trial. | Yes |
Access Stripe billing and payment tools through its MCP server. Connect with OAuth or a supported agent API key and choose the intended account.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Preview the month's billing from approved time, retainers and progress, then draft invoices to send
Provider intelligence API joining NPPES, CMS Open Payments, and OIG LEIE with source provenance.
Gemini CLI
Place overdue B2B invoices for collection and track outreach, payments and remittances.