AI assistants like Claude are getting increasingly capable at taking real-world actions - browsing the web, writing code, sending emails. PayBridgeNP's MCP (Model Context Protocol) server extends this capability to payments in Nepal.
With PayBridgeNP MCP installed, you can tell Claude: "Create a payment link for Rs 5,000 for the client Rohan" - and it happens.
What is MCP?
Model Context Protocol (MCP) is an open standard created by Anthropic that lets AI assistants connect to external tools and APIs in a standardised way. Instead of writing custom integrations for each AI platform, you expose a set of "tools" via an MCP server and any compatible AI can use them.
Think of it as a plugin system for AI models - but standardised and open.
What PayBridgeNP MCP Can Do
The PayBridgeNP MCP server exposes 70 tools across several categories:
Payments and Refunds
- List and inspect individual payments with full provider detail
- Issue refunds (always asks for confirmation before executing)
- Check refund status and failure reason
Payment Links
- Create links with custom amounts and descriptions
- Update, cancel, or delete links
- View conversion stats inline
Webhooks
- Create, update, and delete webhook endpoints
- Inspect per-delivery debug info: status, response body, retry count
Billing
- Plans, customers, subscriptions, and invoices
- Coupon and promotion code management
- Tax settings
- Dunning policies and per-invoice retry control
- Metered usage reporting and proration preview
Analytics
- Revenue KPIs, success rate, provider breakdown (Khalti vs eSewa vs Fonepay) over any 1-90 day window
Built-in Prompt Templates
Beyond raw tools, the MCP server ships 6 built-in prompt templates that appear as slash commands in Claude Desktop and Cursor:
/paybridge:daily_summary- End-of-day digest: revenue, payments, refunds, checkout funnel, webhook failures/paybridge:monthly_reconciliation- Full month reconciliation table ready to share with your accountant/paybridge:investigate_failed_payment- Diagnose why payments failed and get a recommended action for each/paybridge:onboard_customer- Create a customer and subscribe them to a plan in one flow/paybridge:review_dunning- Review all past-due invoices and decide whether to retry or stop dunning/paybridge:apply_discount- Validate and apply a promo code to a subscription, with before/after price shown first
Setting Up PayBridgeNP MCP with Claude Desktop
Prerequisites
- Claude Desktop app installed
- A PayBridgeNP account with an MCP token (generate one at dashboard.paybridgenp.com/mcp)
- Node.js 18+ installed
Installation
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on Mac):
{
"mcpServers": {
"paybridge": {
"command": "npx",
"args": ["-y", "@paybridge-np/mcp@latest"],
"env": {
"PAYBRIDGENP_API_KEY": "sk_live_your_key_here"
}
}
}
}
Restart Claude Desktop. You'll see a tools icon in the chat indicating PayBridgeNP tools are available.
First Use
Ask Claude:
"Create a payment link for Rs 2,500 for a logo design project for Priya Adhikari"
Claude will call the create_payment_link tool and return:
"I've created the payment link: paybridgenp.com/pay/lnk_abc123
- Amount: NPR 2,500
- Description: Logo design project - Priya Adhikari
- Expires: never (you can change this)
Share it with Priya via WhatsApp, email, or anywhere."
Real-World Workflows
Freelance billing via chat:
You: "I finished three projects this week. Create payment links: Rs 15,000 for the website for TechNepal, Rs 8,000 for the logo for StartupKTM, Rs 3,500 for the social media package for Organic Store."
Claude: "Created all three links: [links listed]"
End-of-day summary:
You: "/paybridge:daily_summary"
Claude: "PayBridgeNP - Daily Summary Revenue: NPR 23,500 gross, NPR 22,000 net Payments: 4 succeeded, 1 failed (success rate 80%) Refunds: 1, NPR 1,500 Checkout funnel: 8 sessions started, 5 completed (63%) Webhooks: no failures"
Customer service flow:
You: "Customer Ram Bahadur says he didn't receive his refund"
Claude: "I found Ram Bahadur's transaction - pay_xyz789, NPR 1,800 paid via Khalti on April 10. There's a refund initiated on April 12 (refund_abc) for NPR 1,800. Current status: completed. The funds should have returned to his Khalti wallet by April 13-14. Ask him to check his Khalti transaction history for that date range."
Monthly reconciliation:
You: "/paybridge:monthly_reconciliation month=2026-04"
Claude pulls all April payments and refunds, then formats a clean table: gross volume by provider, net after refunds, success rate, top customers - ready to paste into a spreadsheet.
Security Considerations
Scoped MCP tokens: Generate a token at dashboard.paybridgenp.com/mcp and pick exactly which scopes to grant. Read-only by default - opt in to write scopes per category (refunds, billing, webhooks, etc.).
Confirmation on money-moving actions: For refunds and large checkout sessions, Claude shows a confirmation modal before executing. This is enforced at the server level, not just UI convention.
24-hour spend cap: Set a rolling cap on how much refunds + checkout sessions a given token can originate in 24 hours. Auto-prefilled to Rs 50,000 when any write scope is enabled.
Audit trail: Tool calls are logged against your account.
The PayBridgeNP MCP server is open source
Source lives at github.com/paybridgenp/paybridgenp-mcp. Audit exactly what runs against your key before installing.
See what it looks like on the MCP server page, or install it and start managing your Nepali payments with AI.