Skip to main content
With Nuwa MCP Proxy, you can convert an existing MCP server (Streamable HTTP or STDIO) into a Nuwa‑Compatible MCP endpoint, enable DID authentication for the server and payment for your MCP tools, without changing the service. The proxy exposes a single JSON‑RPC endpoint (/mcp) over streamable HTTP, forwards tools, and attaches Nuwa payment semantics. NPM Package: @nuwa-ai/mcp-server-proxy - Ready to use without building from source.
Nuwa MCP Proxy is designed to be single-server, single-endpoint MCP server. For multiple MCP servers, you have to deploy multiple Nuwa MCP Proxy instances.

Quick start

Before you start: obtain a Service Key for your service DID. See the Service Key guide and use the copied value as SERVICE_KEY.

Upstream modes

Preconfigured examples

Two ready-to-run examples are included. You can use them with either the npm package or source code:
Using NPM Package:
Using Source Code:
Config reference: deployments/instances/amap-proxy/config.yaml

Relevant Docs

Railway Deployment Tutorial

Complete guide to deploying MCP Server Proxy on Railway platform

MCP Pricing

Pricing for MCP tools

Revenue

View balances, withdraw, and audit revenue history

Service Key

How to obtain and configure SERVICE_KEY

MCP Server

Build a pay‑per‑call MCP server directly using the Payment Kit.