Payman Financial Service Connector

An MCP (Model Context Protocol) gateway designed for effortless interfacing with Payman AI's suite of financial APIs, empowering intelligent assistants to manage recipient onboarding, lookup contacts, dispatch monetary transfers, and ascertain current account standing using conversational prompts.

Core Functionality

This MCP server exposes Payman AI's financial primitives as callable functions consumable by Large Language Models (LLMs) such as Claude. It grants AI agents the capacity to perform the subsequent actions:

• Provision API credentials for secure session authorization
• Register various classes of beneficiaries (e.g., TEST_RAILS, US_ACH, CRYPTO_ADDRESS)
• Execute outgoing fund remittances to established recipients
• Perform detailed searches across the recipient database
• Retrieve real-time account monetary figures

This architecture adheres strictly to the Model Context Protocol (MCP) specification, guaranteeing interoperability across any compliant client platform.

Capabilities Overview

• Robust Credential Handling: API tokens are managed securely within the active session context.
• Diverse Recipient Types Supported:
• TEST_RAILS accounts designated for simulation and validation.
• US_ACH channels for domestic United States electronic fund transfers.
• CRYPTO_ADDRESS endpoints for distributed ledger asset movements.
• Transaction Execution: Tools for initiating payments, specifying monetary values and transactional notes.
• Information Retrieval: Mechanisms to look up recipients based on identity, contact details, or account specifics.
• Operational Safeguards: Comprehensive failure reporting for all attempted API interactions.
• Transport Flexibility: Supports standard command-line communication (stdio) and streamed updates (Server-Sent Events).

Prerequisites for Deployment

• Runtime Environment: Node.js (version 14 or later).
• Package Manager: npm or yarn.
• API Access: A valid credential key issued by Payman AI.

Deployment Instructions

Installation via Smithery

For automated setup targeting Claude Desktop using Smithery:

bash npx -y @smithery/cli install @hrishi0102/payman_mcp --client claude

1. Obtain the source repository:

bash git clone https://github.com/yourusername/payman-mcp-server.git cd payman-mcp-server

1. Install necessary libraries:

bash npm install # Alternatively yarn install

1. Compile the source code:

bash npm run build # Alternatively yarn build

Configuration

Server configuration files are not utilized. Authentication parameters (API keys) are supplied dynamically via the set-api-key function call during operation.

Server Execution

Standard I/O Operation (For Desktop Clients)

Execute the server in stdio mode, suitable for clients like Claude Desktop:

Confirm readiness:

bash node /ABSOLUTE/PATH/TO/PARENT/FOLDER/payman-mcp/build/payman-server.js

Upon successful initialization, integrate this Payman MCP server into your chosen client application.

• For Claude Desktop setup guidance: Link
• For Cursor integration details: Link

Server-Sent Events (SSE) Mode (For Web Services)

To launch the server using SSE transport (requires express and cors packages):

bash node build/payman-server-sse.js

This initiates a local HTTP server, typically on port 3001, exposing:

• /sse: The stream endpoint for server-to-client data transmission.
• /messages: The input endpoint for client-to-server communication.

Client Integration Workflow

Integration with Claude Desktop

1. Locate and open the configuration JSON for Claude Desktop:

2. macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

3. Windows: %APPDATA%\Claude\claude_desktop_config.json

4. Append the server definition:

{ "mcpServers": { "payman": { "command": "node", "args": ["/ABSOLUTE/PATH/TO/payman-mcp-server/build/payman-server.js"] } } }

1. Restart the Claude Desktop application.

Other MCP Implementations

Consult the specific documentation for other compatible environments (e.g., Cursor) regarding the procedure for adding external MCP endpoints.

Operational Guidance

Once the server connection is established with the MCP client, utilize the following callable functions:

Authorization Key Provisioning

Begin by setting the required Payman API key:

Please use the set-api-key tool with my Payman API key: YOUR_API_KEY_HERE

Recipient Account Setup

Test Rails Recipient

Register a synthetic recipient named "Test User" utilizing the tag "test"

US ACH Recipient

Establish a US ACH beneficiary profile with these attributes: - Account Holder Name: John Doe - Account Classification: checking - Account Identifier: 12345678 - Clearing Code: 123456789 - Registration Name: John Doe - Holder Capacity: individual

Cryptocurrency Recipient

Set up a CRYPTO_ADDRESS beneficiary entity: - Alias: Crypto Wallet - Destination Address: 0x1234567890abcdef - Network: ethereum - Asset Type: ETH

Transferring Funds

Transfer 100 units to the recipient identified as "pay_123abc" with the reference note "Monthly service"

Recipient Lookup

Execute a search across all registered accounts associated with the moniker "John"

Balance Inquiry

Report the current available monetary reserve.

Function Reference

set-api-key

Authenticates the session by supplying the Payman service credential.

• Arguments:
• apiKey (string): The requisite Payman API token.

create-test-rails-payee

Provisions a TEST_RAILS account for sandboxed transactions.

• Arguments:
• name (string): The designation for the new entry.
• type (string): Must be "TEST_RAILS" (default).
• tags (string[]): Optional descriptive labels.

create-us-ach-payee

Registers a US_ACH entity for standard bank transfers.

• Arguments:
• type (string): Must be "US_ACH" (default).
• accountType (enum): Must be "checking" or "savings".
• accountNumber (string): The destination bank account number.
• routingNumber (string): The ABA routing transit number.
• accountHolderName (string): The legal name of the account owner.
• accountHolderType (enum): "individual" or "business".
• name (string): The local identifier for this recipient.
• Additional optional fields (tags, contactDetails).

create-crypto-payee

Registers a CRYPTO_ADDRESS entity for digital asset disbursements.

• Arguments:
• type (string): Must be "CRYPTO_ADDRESS" (default).
• address (string): The public ledger destination address.
• chain (string): The underlying blockchain protocol.
• currency (string): The specific digital asset ticker.
• name (string): The local identifier for this recipient.
• Additional optional fields (tags, contactDetails).

send-payment

Initiates a transfer of funds to a specified recipient.

• Arguments:
• payeeId (string): Unique identifier of the recipient.
• amountDecimal (number): The precise monetary quantity to remit.
• walletId (string, optional): Specify source wallet if multiple exist.
• memo (string, optional): Transaction commentary.
• metadata (object, optional): Supplementary structured data.

search-payees

Queries the recipient repository using specific criteria.

• Arguments: Several optional search qualifiers:
• name, contactEmail, accountNumber, etc.

get-balance

Fetches the current aggregated ledger valuation.

• Arguments: None required.

Error Handling Protocols

All integrated functions incorporate robust error trapping, returning meaningful diagnostic messages in cases such as:

• Missing session credentials (API key unset).
• Failures during interaction with the remote Payman service.
• Input validation failures.
• Connectivity disruptions.

Security Posture

• API credentials are held strictly in volatile memory for the active connection period.
• No sensitive authentication data is written to persistent storage.

• All outbound communication to the Payman backend is secured using appropriate authorization headers.

• Reference Specification: Model Context Protocol

• Financial Services Provider: Payman AI
• Input Schema Validation Library: Zod

WIKIPEDIA: Corporate management solutions encompass the totality of systems, applications, control mechanisms, computational frameworks, and operational philosophies employed by enterprises to navigate evolving market dynamics, secure a competitive edge, and elevate overall organizational efficiency.

== Frameworks Synopsis == Systems can be categorized based on departmental alignment or functional aspect, such as strategic planning tools, workflow management utilities, record-keeping applications, human capital resources, mechanisms for corporate arbitration, oversight instruments, and so forth. A functional taxonomy commonly identifies:

Utilities for data ingestion and verification across functional silos. Software designed for supervising and refining operational workflows. Platforms for data aggregation and critical executive decision support. Contemporary management tools have undergone radical modernization over the past decade due to rapid technological advancements, resulting in a complex landscape where selecting optimal business solutions for any given context is challenging. This complexity is driven by continuous imperatives to reduce expenditure, maximize revenue generation, deeply understand client requirements, and deliver requisite products exactly as demanded. Against this backdrop, executives must adopt a strategic viewpoint regarding management tooling, rather than blindly adopting the newest technology, which often results in systemic instability. The selection and subsequent tailoring of business management instruments to align precisely with organizational requirements—and not vice versa—is paramount.

== Prominent Instruments == Data from a 2013 Bain & Company survey detailed the global utilization of business instruments, reflecting how their yielded results addressed regional necessities, market conditions, and corporate downturns. The top ten categories identified included:

Strategic Roadmap Development Client Relationship Ecosystems Personnel Sentiment Analysis Comparative Performance Assessment Integrated Performance Metric Dashboards Core Competency Identification External Resource Management (Outsourcing) Organizational Transformation Programs Logistics and Fulfillment Chain Oversight Foundational Mission and Vision Articulation Client Demographic Segmentation Comprehensive Quality Assurance Methodologies

== Business Software Applications == Computer programs or collections of software utilized by enterprise personnel to execute diverse operational tasks are termed business software (or applications). These applications aim to augment productivity, quantify performance metrics, and execute various corporate functions with precision. The evolution progressed from early Management Information Systems (MIS) to comprehensive Enterprise Resource Planning (ERP) suites, subsequently incorporating Customer Relationship Management (CRM), culminating in the current era of cloud-based corporate management platforms. While a verifiable relationship exists between technology investment and organizational success, two elements fundamentally contribute value: the efficacy of the deployment process and the judicious selection and customization of the chosen technological assets.

== Solutions for Mid-Sized Enterprises (SMEs) == Tools specifically tailored for SMEs are crucial as they offer pathways to conserve capital and...