PaymentsNZ MCP Server

Created By
apimatica year ago
Overview

what is PaymentsNZ MCP Server?

PaymentsNZ MCP Server is a server designed to facilitate payment processing and API integration for PaymentsNZ services.

how to use PaymentsNZ MCP Server?

To use the PaymentsNZ MCP Server, you need to build the server using Node.js and configure it with your access token and server path in the Claude Desktop configuration.

key features of PaymentsNZ MCP Server?

  • Easy setup with Node.js
  • Integration with PaymentsNZ API for transaction processing
  • Configuration through Claude Desktop for seamless operation

use cases of PaymentsNZ MCP Server?

  1. Processing payments through PaymentsNZ API.
  2. Integrating payment services into applications.
  3. Managing transaction data securely.

FAQ from PaymentsNZ MCP Server?

  • How do I build the server?

You can build the server by installing Node.js and running the provided npm commands in the SDK and MCP server directories.

  • How do I obtain an access token?

You can obtain an access token by visiting the PaymentsNZ application and following the authentication steps outlined in the documentation.

  • How long does the access token last?

The access token is valid for one hour and should be used within that time frame.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
apimatic
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago