Agent Payment MCP

Agent Payment MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/Apoth3osis-ai/agent-payment-mcp/releases/download/v1.1.0/agent-payment-router-linux-amd64. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client; the entry names binary as the runtime. It reads these environment variables: x-api-key (required, secret) and x-budget-key (required, secret); set them in the client's configuration for this server.

Agent Payment MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/Apoth3osis-ai/agent-payment-mcp/releases/download/v1.1.0/agent-payment-router-darwin-amd64. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client; the entry names binary as the runtime. It reads these environment variables: x-api-key (required, secret) and x-budget-key (required, secret); set them in the client's configuration for this server.

Agent Payment MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/Apoth3osis-ai/agent-payment-mcp/releases/download/v1.1.0/agent-payment-router-darwin-arm64. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client; the entry names binary as the runtime. It reads these environment variables: x-api-key (required, secret) and x-budget-key (required, secret); set them in the client's configuration for this server.

Agent Payment MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/Apoth3osis-ai/agent-payment-mcp/releases/download/v1.1.0/agent-payment-router-windows-amd64.exe. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client; the entry names binary as the runtime. It reads these environment variables: x-api-key (required, secret) and x-budget-key (required, secret); set them in the client's configuration for this server.

Agent Payment MCP runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/Apoth3osis-ai/agent-payment-mcp/releases/download/v1.1.0/agent-payment-router-linux-arm64. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client; the entry names binary as the runtime. It reads these environment variables: x-api-key (required, secret) and x-budget-key (required, secret); set them in the client's configuration for this server.

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect