Payments Ai Mcp

ai.payments.morPublished by mor.payments.aiOfficial publisherv2.7.0Updated Nov 7, 2026

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

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Payments AI server that lets an assistant launch products and branded checkouts on a Merchant of Record platform for AI-built apps.

What you can do
  • Launch products on Payments AI, a Merchant of Record for AI-built apps
  • Set up branded checkouts for those products
  • No tool list, instructions or README is published, so the exact operations an assistant can perform are not documented here.
When to use it
Consider it if you build apps with AI assistance and want an assistant to help set up products and branded checkout through Payments AI instead of doing it by hand in the dashboard.
Requirements
A remote server reached over streamable HTTP at the provider's endpoint; no local package or environment variables are declared. OAuth authentication is required, so you need a Payments AI account and must complete the OAuth sign-in flow.
Before you install
It is a payments platform, so actions may create live products and checkouts that handle real money and customer transactions. OAuth grants the assistant access to your Payments AI account; review the scopes requested. No tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Payments Ai Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.payments.mor%2Fpayments-ai-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "payments-ai": {
      "type": "http",
      "url": "https://mor.payments.ai/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v2.7.0LatestNov 7, 2026
  2. v2.6.0Nov 3, 2026
  3. v2.5.0Oct 22, 2026
  4. v2.4.1Oct 15, 2026

Score

56% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.