MCP.so
ログイン

authorize-net-mcp

@zmarty

authorize-net-mcp について

Experimental Authorize.net Node.js TypeScript MCP Server

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

zmarty

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is authorize-net-mcp?

authorize-net-mcp is a Model Context Protocol (MCP) server that integrates with the Authorize.net Node SDK to expose two primary payment operations—takePayment (immediate charge) and createInvoice (hosted payment page)—as MCP tools. It is designed for AI agents and automation platforms that communicate via the MCP protocol.

How to use authorize-net-mcp?

Install dependencies with npm install, set environment variables (AUTHORIZE_NET_API_LOGIN_ID, AUTHORIZE_NET_TRANSACTION_KEY, optionally AUTHORIZE_NET_SANDBOX), build with npm run build, then start the MCP server with npm start. The server listens on stdio and can be configured in Claude Desktop’s config.json.

Key features of authorize-net-mcp

  • Provides takePayment and createInvoice MCP tools.
  • Uses Authorize.net Node SDK for payment processing.
  • Supports sandbox mode for testing.
  • Designed for AI assistants and automation tools.
  • Communicates via stdio transport (MCP protocol).
  • Input/output schemas are advertised via MCP discovery.

Use cases of authorize-net-mcp

  • AI assistant charges a credit card on behalf of a user.
  • Generate a hosted payment page invoice for a customer to pay online.
  • Automate payment workflows without custom payment logic.
  • Integrate Authorize.net payments into MCP-compatible platforms (e.g., AI chat).

FAQ from authorize-net-mcp

What tools does authorize-net-mcp provide?

It provides two tools: takePayment (charges a credit card immediately) and createInvoice (generates a hosted payment page URL).

What environment variables are required?

You must set AUTHORIZE_NET_API_LOGIN_ID, AUTHORIZE_NET_TRANSACTION_KEY, and optionally AUTHORIZE_NET_SANDBOX (set to "true" for sandbox mode).

How does sandbox vs production work?

Sandbox testing uses Authorize.net sandbox credentials and the AUTHORIZE_NET_SANDBOX env variable. For production, switch the base URL in authorizeNetHandlers.ts and use live credentials.

Where is security discussed?

The README advises never committing API keys to source control, use environment variables or secret management, and use HTTPS/secure tunnels in production.

What runtime dependencies does it have?

Node.js with the MCP Node SDK and the authorizenet package. It uses TypeScript and builds to JavaScript.

コメント

「その他」の他のコンテンツ