AgentPay

Provides an MCP server to coordinate secure AgentPay transactions locally with human approvals and automated execution within AI workflows.

javascript

2

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "kar69-96-useagentpay": {
      "command": "npx",
      "args": [
        "@useagentpay/mcp-server"
      ]
    }
  }
}

You can run an MCP server for AgentPay to manage secure, local payments interactions within your AI agents. This server coordinates purchase proposals, approvals, and execution while keeping sensitive data on your machine, helping you automate workflows without exposing credentials.

How to use

Set up the MCP server in your environment to accept and manage AgentPay transactions through your preferred MCP client. The server runs locally and exposes an endpoint your MCP client can communicate with, coordinating the lifecycle of a purchase from proposal to execution.

How to install

Prerequisites you need before starting:

Install the MCP server package and run it using the provided command.

Steps to install and run the MCP server:

node -v
npm -v

npx @useagentpay/mcp-server

Or configure the server in your host configuration as shown below.

## Configuration and usage notes

Configuring the MCP host to launch AgentPay MCP server allows your MCP client to connect automatically. You can also insert the server into your host’s MCP configuration for centralized management.

{ "mcpServers": { "agentpay": { "command": "npx", "args": ["@useagentpay/mcp-server"] } } }

## Security and privacy notes

All sensitive credentials stay on your machine. The MCP server coordinates transactions without transmitting unencrypted credentials externally. Human approvals remain cryptographically signed locally as part of the purchase workflow. This setup minimizes exposure while enabling automated interactions via MCP clients.

## Examples and best practices

Use a dedicated environment or container for the MCP server to isolate it from your main development environment. When integrating with Browserbase or other UI components, ensure your browsers or headless sessions run with proper security measures and restricted scopes.

## Troubleshooting

If the MCP server fails to start, verify Node.js and npm are correctly installed, then confirm no other process is binding the default MCP port. Check the console for any errors related to missing packages and run npm install if necessary.