P-Link

P-Link MCP Server exposes the p-link.io API as MCP tools over HTTP (streamable) and STDIO. It provides a suite of tools to manage Solana-based payments, including sending money, creating payment links, and querying wallet information. Core tools include send_money (execute transfers to wallets, emails, or phone numbers), request_payment_link (generate a 402-compliant payment link with optional webhooks or email notifications), get_wallet_info, get_wallet_history, and fund_my_wallet (instructions to fund via Solana or credit card). The manifest available at the MCP endpoint describes all available tools so clients like ChatGPT or Claude can call them directly. To use the server with your MCP client, configure the connector to point at https://mcp.p-link.io/mcp or use the STDIO/HTTP integrations described in the README, and provide your API key for authentication when using the npx install flow.

Prerequisites:

• Node.js and npm installed for local npx/npm install flow
• Docker and Docker Compose for HTTP/Docker setup
• Access to a P-Link API key (APIKEY)

1. Quick local run with npx (no build step required):

• Install and run using your API key:

npx plink-mcp-server --apikey=YOUR_APIKEY

2. Install via npm (clone and build if you prefer):

# 1) Clone the repository
git clone https://github.com/paracetamol951/P-Link-MCP.git

# 2) Install dependencies
cd P-Link-MCP
npm install

# 3) Build (if the project provides a build step)
npm run build

# 4) Run with API key
APIKEY=YOUR_APIKEY npm start

3. Run via Docker (HTTP mode):

# Use docker compose if a docker-compose.yml is provided in the repo
docker compose up

4. Environment setup

• Create a .env file in the working directory with:

APIKEY=YOUR_APIKEY

5. Verification

• Access the MCP manifest at: https://mcp.p-link.io/.well-known/mcp/manifest.json
• Verify the server is reachable and the tools are listed in the manifest.

Prerequisites summary: ensure APIKEY is available and correctly configured, and choose either the npx/CLI path or Docker for HTTP/STDIO deployments depending on your environment.

Tips and caveats:

• The APIKEY is required for authentication; do not expose it publicly. Use environment variables or secret management in production.
• The MCP manifest endpoint provides a machine-readable list of available tools and their schemas; consult it when integrating with clients like ChatGPT or Claude.
• For HTTP/STDIO usage, you can call tools via the MCP protocol over HTTP or through standard I/O streams depending on your client configuration.
• If you encounter issues with wallet provisioning or payments, verify APIKEY permissions and ensure your environment variables are loaded correctly (e.g., .env file or CI secret management).
• When using send_money or fund_my_wallet, be mindful of the 3-day unclaimed funds window and handling of wallet creation for new users.
• Docker deployment simplifies environment isolation but ensure network access to Solana and any required webhooks or payment callbacks.
• The npm package name used in npx is plink-mcp-server; use the latest version to get the newest tools and endpoints.