2328 Wallet MCP Server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@2328 Wallet MCP ServerCreate an invoice for 0.05 BTC"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
2328 Wallet CLI and MCP Server
An installable Bun CLI and MCP interface for a 2328 merchant account. Running 2328 opens an interactive terminal menu; 2328 --mcp exposes the same account to a local MCP client over stdio; 2328 --serve starts the hosted OAuth-enabled Streamable HTTP service.
The implementation follows the live 2328 API documentation. Decimal amounts remain strings from input to the upstream API.
Capabilities
Area | MCP tools |
Account |
|
Market |
|
Payments |
|
Static wallets |
|
Payouts |
|
Convert |
|
Payout and conversion execution are split into prepare/confirm calls. The preparation is encrypted, bound to one connection and short-lived. A client must show the quote and obtain the exact confirmation string before execution.
The MCP also publishes wallet2328://safety and wallet2328://capabilities resources so an agent can retrieve settlement rules and the scopes actually approved for its connection.
Related MCP server: btcpay-mcp
Install the CLI
Requirements: Bun 1.3 or newer and a 2328 project ID/API key. The payout API key is separate and optional.
From the package registry after publication:
bun install --global @2328/mcp-server
2328From this checkout:
bun install --frozen-lockfile
bun run build
chmod +x dist/index.js # Linux/macOS
bun link
2328The first interactive launch verifies the ordinary API key with the balance endpoint. API keys are stored in Windows Credential Manager, macOS Keychain or Linux Secret Service through Bun.secrets; the config file contains only profile metadata. On a headless system without a credential store, provide PROJECT_ID, API_KEY and optionally PAYOUT_API_KEY through the process environment.
Local MCP
Configure a profile interactively once with 2328, then point the MCP client at:
{
"command": "2328",
"args": ["--mcp"]
}For a named profile:
{
"command": "2328",
"args": ["--mcp", "--profile", "merchant-production"]
}Environment-only configuration is also supported:
{
"command": "2328",
"args": ["--mcp"],
"env": {
"PROJECT_ID": "...",
"API_KEY": "...",
"PAYOUT_API_KEY": "..."
}
}If the payout key is absent, payout scopes are omitted from the local principal. Protocol frames are written only to stdout; diagnostics use stderr.
Hosted Streamable HTTP
The hosted mode uses OAuth Authorization Code with PKCE, short-lived encrypted access tokens and rotating refresh tokens. Ordinary read-only scopes are selected by default; payout, management and money-moving scopes require separate selection.
The production endpoint is https://mcp.2328.io/mcp. The dedicated-server deployment terminates TLS in Caddy and keeps both the MCP application and Redis off the public host network.
Production deployment:
cp .env.production.example .env.production
# Set ACME_EMAIL in .env.production.
sh deploy/init-secrets.sh
docker compose --env-file .env.production -f compose.production.yaml config
docker compose --env-file .env.production -f compose.production.yaml build --pull
docker compose --env-file .env.production -f compose.production.yaml up -dCreate an A record for mcp.2328.io before starting Caddy and allow inbound TCP 80/443 plus UDP 443. Do not expose ports 3000 or 6379. See operations for verification, upgrades and secret handling.
For local hosted-mode development:
cp .env.example .env
bun -e "console.log(crypto.getRandomValues(new Uint8Array(32)).toBase64({alphabet:'base64url',omitPadding:true}))"
# Put the value in TOKEN_ENCRYPTION_KEY and configure the public HTTPS origin.
docker compose up --build -dConnect an OAuth-capable MCP client to https://mcp.example.com/mcp. Users link a project using project keys; the service never asks for the 2328 account password. The compose port is loopback-only so a reverse proxy or ingress must own public TLS.
ChatGPT and Codex plugin
The installable plugin package is in plugins/2328-wallet. It contains the validated manifest, hosted MCP configuration and official 2328 mark. ChatGPT additionally requires the hosted MCP connection to be registered in Developer mode; after registration, add its generated plugin_asdk_app... mapping as described in the plugin README.
Commands
2328 interactive terminal account menu
2328 --mcp [--profile NAME] local MCP over stdio
2328 --serve hosted OAuth MCP service
2328 --help
2328 --versionDevelopment and verification
bun install --frozen-lockfile
bun run typecheck
bun run lint
bun test
bun run build
bun run verify:package
bun run verify:tui
# With a reachable Redis instance:
bun run verify:hosted
bun auditRead API coverage, architecture, security and operations before a public deployment.
License
Licensed under the Apache License 2.0.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceAn MCP server for FixPayment creditors that simplifies account management, status updates, and reporting through plain-English AI interactions (https://fixpayment.org/)
- AlicenseAqualityDmaintenanceAn MCP server that enables AI agents to manage merchant payment processing through the BTCPay Server Greenfield REST API. It supports tools for creating invoices, managing stores, tracking payments, and performing Lightning Network operations.21MIT

satsrail-mcpofficial
Alicense-qualityCmaintenanceAn MCP server that enables AI agents to accept Bitcoin Lightning payments. It allows agents to create orders, generate invoices, check payment status, and manage the full SatsRail merchant API through natural language.MIT- Alicense-qualityDmaintenanceMCP server for cryptocurrency payment integration, enabling payment requests, webhook verification, and payment URL building.MIT
Related MCP Connectors
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
Hosted MCP server for Mini Accountant: invoices, expenses, customers, analytics, tax estimates.
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/2328io/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server