payport

payport gives an agent a working doorway into a Stripe account: open a customer record, put a product and a price in the catalog, hand a buyer a hosted payment link, draft an invoice and finalize it, check the balance, refund a payment, issue a coupon, answer a dispute, and manage subscriptions. Each operation is one call against the Stripe REST API, and the API's JSON answer comes back as-is. It runs from the command line or as an MCP server for agents.

A Stripe secret key is required. Put it in the STRIPE_SECRET_KEY environment variable; the key is sent to the API as a Bearer token and never appears in output. When the variable is missing, every operation fails with an error that names it.

Install

npx @reneturcios/payport list-customers --limit 5

Or run the container image:

docker run -i -e STRIPE_SECRET_KEY ghcr.io/cloudcorprecords/payport

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

export STRIPE_SECRET_KEY="your secret key"

payport create-customer --name "Ada Lovelace" --email ada@example.com
payport list-customers --email ada@example.com --limit 5
payport create-product --name "Trail Guide" --description "A field guide"
payport list-products --limit 10
payport retrieve-balance

payport --version

Exit codes: 0 on success, 1 when an API call fails (including a missing STRIPE_SECRET_KEY), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

npx -y @reneturcios/payport mcp

MCP client configuration:

{
  "mcpServers": {
    "payport": {
      "command": "npx",
      "args": ["-y", "@reneturcios/payport", "mcp"],
      "env": { "STRIPE_SECRET_KEY": "your secret key" }
    }
  }
}

Tools

... View full README on GitHub