Payments Ai Mcp

io.github.szarlPublished by GitHub account szarlv1.1.3Updated Oct 24, 2026

Launch products and branded checkouts on Payments AI, the Merchant of Record for AI-built apps.

The publisher's own server: Payments Ai Mcp

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local MCP server for Payments AI, a Merchant of Record, letting an assistant launch products and branded checkouts for AI-built apps.

What you can do
  • Launch products on Payments AI, a Merchant of Record aimed at AI-built apps.
  • Set up branded checkout experiences for those products.
  • No tool list, README or server instructions are published, so the exact operations available to an assistant are not documented here.
When to use it
Consider it when you are building an app with AI assistance and want the assistant to help create products and branded checkouts through Payments AI as Merchant of Record.
Requirements
Runs as a local process over stdio, installed from the npm package @payments-ai/mcp, so a Node.js runtime is needed. Desktop client only; no web execution. No authentication, environment variables or headers are declared.
Before you install
It concerns payments and commerce: product and checkout setup can affect what customers are charged, so review changes before publishing. No credentials are declared, but a payments service will typically need an account, and the manifest does not say how that is supplied. The tool set is undocumented, so verify what it can change.

Installation

In SourceWeft

  1. Open Payments Ai Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Payments integrations