Connecting a client

Connecting has two parts: point your client at the server (https://mcp.pdfasyougo.com) and give it a wallet so it can answer the x402 payment challenge. There is no API key.

Preview & evolving clients

MCP client support for remote servers and for x402 payment is still maturing and differs between clients. The configs below are representative; check your client’s own docs for the exact keys it uses for remote servers and wallet/x402 settings. Exact values for your account come with preview access.

Clients that support remote servers natively

If your client can connect to a remote MCP server by URL, add an entry pointing at the endpoint and supply a wallet for payment:

MCP client config (representative)

{
  "mcpServers": {
    "pdf-as-you-go": {
      "url": "https://mcp.pdfasyougo.com",
      "x402": {
        "network": "base",
        "wallet": "${X402_WALLET_PRIVATE_KEY}"
      }
    }
  }
}

Provide the wallet key through an environment variable rather than inline — see Securing your wallet.

Clients that only support stdio (use a connector)

Many desktop clients today launch MCP servers as a local command over stdio. For those, run a small connector that bridges stdio to the remote server and handles the x402 payment loop, configured with your wallet:

Claude Desktop

Edit claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "pdf-as-you-go": {
      "command": "npx",
      "args": ["-y", "x402-mcp-connect", "https://mcp.pdfasyougo.com"],
      "env": {
        "X402_WALLET_PRIVATE_KEY": "0xYOUR_DEDICATED_WALLET_KEY",
        "X402_NETWORK": "base"
      }
    }
  }
}

Restart Claude Desktop. The PDF tools appear in the tools menu.

Cursor

Add the server in ~/.cursor/mcp.json (or the project’s .cursor/mcp.json):

{
  "mcpServers": {
    "pdf-as-you-go": {
      "command": "npx",
      "args": ["-y", "x402-mcp-connect", "https://mcp.pdfasyougo.com"],
      "env": {
        "X402_WALLET_PRIVATE_KEY": "0xYOUR_DEDICATED_WALLET_KEY",
        "X402_NETWORK": "base"
      }
    }
  }
}

Reload the window; the tools register for the workspace.

Custom client

Any MCP client library can connect to the remote URL. Pair it with an x402 payment handler (see Paying with x402) so 402 responses are signed and retried. The connector approach above also works for headless/server agents.

Note

x402-mcp-connect is shown as a placeholder name for the bridging connector. The exact connector package recommended for preview is shared when you request access.

Verifying the connection

1. Restart/reload your client after editing its config.
2. Confirm the PDF tools appear (e.g. merge_pdfs, add_text_watermark). The full set is in the Tools reference.
3. Ask the agent to run a simple operation against a public test PDF and confirm it returns a download URL.

If the tools don’t appear, check the client’s MCP logs for connection errors; if a call fails on payment, see Paying with x402.

Securing your wallet

The wallet key lets the client spend funds — protect it accordingly:

• Pass it via an environment variable or secret manager, never commit it to source control.
• Use a dedicated, low-balance wallet for agent spending, topped up as needed.
• See Wallets & networks for funding details.

Next

• Paying with x402 — how the client settles each tool call.
• Tools — parameters for every tool.