That split is unusual and it is the point: an agent connects with no credential, learns the model, generates the integration for your framework and mocks the webhook events so you can test the handler before a real payment exists — then the same connection runs the gateway you deployed. payram_doctor and check_node_sync belong to the operating half and are the ones to reach for first when something is not settling, since a chain node that has fallen behind looks exactly like a payment that never arrived.
PayRam is a self-hosted, multi-chain crypto payment gateway you run yourself. Its MCP server plays two roles: it teaches an agent how PayRam works and generates the integration code, and it operates a gateway you have already deployed. Connecting needs no API key at all — that is only required once you point it at your own instance.
- Understand it first — explain_payram_basics, explain_payram_concepts, explain_payment_flow, list_payram_docs and get_payram_doc_by_id
- Stand one up — scaffold_payram_app, generate_setup_checklist, generate_env_template, suggest_file_structure and setup_payram_agents
- Integration code written for your stack — generate_payment_route_snippet, generate_payment_sdk_snippet, generate_payment_http_snippet, generate_payment_status_snippet, snippet_nextjs_payment_route and snippet_fastapi_payment_route
- Payouts and referrals too — generate_payout_sdk_snippet, generate_payout_recipient_flow_snippet, generate_payout_status_snippet, generate_referral_route_snippet, generate_referral_sdk_snippet, generate_referral_status_snippet and generate_referral_validation_snippet
- Webhooks without waiting for a real event — generate_webhook_handler, generate_webhook_event_router and generate_mock_webhook_event
- Check it before you trust it — payram_doctor, test_payram_connection, check_payment_readiness, check_node_sync, prepare_payram_test and assess_payram_project
- Operate a live gateway — create_payment_link, lookup_payment, search_payments, get_payment_summary, get_daily_volume, get_unswept_balances, list_currencies, list_platforms and list_recipients
- Agent skills published separately for setup, auth, analytics, crypto payments, checkout, widget and webhook integration
Nothing to connect: the hosted server is registered at https://mcp.payram.com/mcp over Streamable HTTP, with an SSE endpoint for older clients, and the documentation, scaffolding and code-generation tools work without any credential. Running an actual gateway is where the requirements start — a VPS you control, on which the agent-mode installer deploys PayRam, and API keys generated locally on that instance. There is no PayRam account, no bank and no processor to register with, and no KYC to run it. The operational tools need your instance's credentials.
One command plus a key — npx -y mcp-remote https://mcp.payram.com/mcp, then supply credentials