Model Context Protocol

One package,
two registries,
every AI assistant.

paybito-mcp injects exact PayBito API knowledge — endpoints, auth, request shapes — into any MCP-capable assistant, so it writes integration code that works the first time. Read-only: it never touches funds, keys, or balances.

PyPI paybito-mcp 0.1.9 npm paybito-mcp 0.1.9

data flow

Get started

Three steps to a fluent assistant

Install once, connect your tool, then build in plain language.

STEP 01

Install

Python or Node — same package, your choice of registry.

pip install paybito-mcp

npx -y paybito-mcp

STEP 02

Connect

Add one entry to your assistant's MCP config.

{
  "mcpServers": {
    "paybito": {
      "command": "npx",
      "args": ["-y", "paybito-mcp"]
    }
  }
}

STEP 03

Build

Ask in your own words. The assistant pulls the right endpoints and auth.

# you, in chat
Add a PayBito crypto
payment link to my
checkout.

Routing

It asks one question, then routes

The assistant first learns what you're building, so a payments request never hits the trading API.

exchange

Trading & ICO

Spot, futures, options, market data, copy-trading.

payments

Merchant API

Invoices, billing, KYC, recurring, settlements.

gateway

Checkout

Products, catalogs, cart, payment links & buttons.

platform

Build apps

White-label exchange & apps across PayBito platforms.

“What are you building?”

The answer sets the module and the base URL — your own broker domain, or a PayBito host. The AI fills the endpoint; you keep the keys.

One package,two registries,every AI assistant.