Log inSubmit server
Payram Helper MCP Server logo

Payram Helper MCP Server

Plan, install, diagnose, operate, and integrate self-hosted PayRam crypto-payment deployments through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Payram Helper MCP Server

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.payram.com/

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 11/8/2026, 3:00:31 AM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.payram.com/

Overview

Payram Helper MCP Server connects MCP-aware agents to self-hosted PayRam crypto-payment deployments for installation planning, diagnosis, administration, and application integration. Its hosted endpoint provides credential-free checks and guidance, while day-two API operations use merchant credentials held by the agent. Reach for it when deploying PayRam on a VPS, troubleshooting a running instance, configuring payment flows, or generating backend integration code. The toolset also covers webhooks, payouts, referrals, wallet top-ups, chains, plugins, and operational runbooks.

Use cases

  • Plan a PayRam VPS installation with explicit human handoffs
  • Diagnose a public PayRam deployment before changing configuration
  • Generate payment, payout, webhook, and referral backend code
  • Run recurring PayRam health and payment operations
  • Troubleshoot PayRam errors and select the next remediation tool

Key features

  • Personalized installation plans with resumable stages
  • Credential-free public deployment diagnosis
  • Administrative runbooks for production PayRam instances
  • Copy-paste API recipes for day-two operations
  • Framework-specific payment route generation
  • Webhook, payout, referral, and top-up integration snippets

Tools44

What Payram Helper MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~4.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

24/26 checks healthy over the last 90d

What it can do

From the 44 tools this server returned when we ran it.

Runs commands · 1Handles credentials · 8Makes network requests · 10Read-only tools · 43
Unusual tool instructions. 1 tool description contain text aimed at the AI model rather than at you (reaches for local secrets). Read the tool descriptions before connecting.

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8/18/2026 via OSV.dev · https://mcp.payram.com/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars158Stargazers on the source repository.
Last commit9d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Tools exposed44Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Payram Helper MCP Server works

What Payram Helper MCP Server does

Payram Helper MCP Server supports the lifecycle of a self-hosted PayRam payment gateway. It can produce an ordered installation plan, identify the next action in a deployment, diagnose a public PayRam URL, explain known failures, and provide procedures for changes to a running instance. The setup flow distinguishes work an agent can perform from actions that require a human, including cold-wallet decisions, mainnet spending, and root-only settings.

For application development, the server generates PayRam payment, payout, referral, webhook, and top-up integration code. Outputs include SDK examples, raw HTTP requests, framework-specific routes and handlers, webhook event routers, mock webhook events, environment templates, integration checklists, and suggested backend structures.

How it works

The hosted MCP endpoint is available at https://mcp.payram.com/mcp. An MCP client connects to that endpoint and can use planning and diagnostic tools without first supplying a PayRam API key. payram_doctor checks a server by public URL for reachability, health, TLS, version, and worker state, and can optionally validate an API key without creating resources.

Operational requests use payram_ops_playbook. The agent calls the merchant's PayRam API directly with the selected public credential, dashboard JWT, or project API key; those credentials remain on the agent's machine. The playbook supplies commands, endpoint choices, expected responses, and cautions for tasks such as checking workers, inspecting payments, creating payment links, reviewing unswept funds, and handling webhooks.

The setup and runbook tools mark agent and human responsibilities and include hard stops. payram_troubleshoot accepts a plain-language problem or pasted error text, matches it to known issues, and points to the next tool. Pasted troubleshooting content is not stored.

Tools and capabilities

  • Create personalized VPS installation plans and resumable setup stages.
  • Diagnose public PayRam deployments and validate selected API keys.
  • Provide runbooks for domains, SSL, firewalls, upgrades, backups, restores, chains, Smart Bridge, plugins, proxies, and databases.
  • Supply day-two recipes for health checks, workers, node synchronization, payments, payouts, logs, and daily checks.
  • Generate payment routes for Next.js, Express, FastAPI, Laravel, Go, and Spring Boot.
  • Generate SDK and HTTP snippets for payments, payouts, referrals, webhooks, and top-up wallet flows.

Setup and configuration

Connect an MCP client to the hosted URL using its MCP configuration. The setup planner asks whether the agent may run server commands over SSH or whether the user will execute commands and return their output. A PayRam installation is performed on the user's VPS, followed by human actions such as claiming the root account and setting the public Site URL.

For a merchant backend, generate_env_template creates a configuration template for communicating with the self-hosted PayRam instance. The generated integration examples use PayRam's API or official JavaScript/TypeScript SDK as appropriate. Webhook handling should account for the signed X-Payram-Signature header, calculated with HMAC-SHA256 over the raw request body and the project API key.

Limitations and notes

The hosted server does not retain merchant credentials. Live operational actions depend on credentials supplied to the agent and access to the merchant's PayRam API. Public diagnosis can inspect a deployment by URL, but it is read-only. Human intervention remains required for designated security-sensitive or root-level steps, including cold-wallet handling and mainnet spending decisions.

Some live data tools and assess_payram_project are available when the MCP server is run locally rather than through the hosted endpoint.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Payram Helper MCP Server

Payram Helper MCP Server is an MCP server that connects AI agents to self-hosted PayRam crypto-payment deployments. Its main tools plan installations, diagnose public servers, troubleshoot errors, provide operational runbooks, execute API recipes with agent-held credentials, and generate payment, payout, webhook, referral, and top-up integration code.

Connect an MCP client to `https://mcp.payram.com/mcp` to use the hosted server. Then call `payram_setup_plan`, choose whether the agent can run VPS commands over SSH or you will run them manually, and follow the returned installation stages and human handoffs.

Call `payram_doctor` with the deployment's public URL. It performs a read-only check of reachability, health, TLS, installed versus latest version, and worker states without requiring credentials, and can optionally validate an API key.

Use a payment route tool that matches your framework, such as `snippet_nextjs_payment_route`, `snippet_express_payment_route`, `snippet_fastapi_payment_route`, `snippet_laravel_payment_route`, `snippet_go_payment_handler`, or `snippet_spring_payment_controller`. The server returns backend code that calls PayRam's payment API.

Yes. Cursor is named as a supported MCP-aware client for the hosted PayRam endpoint. Add `https://mcp.payram.com/mcp` to Cursor's MCP configuration, then invoke the server's planning, diagnostic, runbook, operations, or code-generation tools.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPayram Helper MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/payram-helper-mcp-server?style=directory)](https://allmcps.com/mcp/payram-helper-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/payram-helper-mcp-server"><img src="https://allmcps.com/api/badge/payram-helper-mcp-server?style=directory" alt="Payram Helper MCP Server on AllMCPs" /></a>