Docs / Integrations

Integrations

Use Chargly through the SDK, MCP, Stripe-powered top-ups, and deployment-friendly workflows.

Choose your integration path

Live now

  • @chargly/sdk
  • MCP support
  • Stripe integration
  • Documentation + Quickstart

Coming soon

  • Python SDK
  • Framework adapters
  • More deployment examples
  • Expanded MCP tooling

Integration summaries

JavaScript / TypeScript

Best for: SaaS apps, backends, and any Node.js/TypeScript service where you own the request flow. The SDK lets you meter events, check balances, and create checkouts directly from your code.

Install the package, initialize with your API key, and call meterEvent when an AI action occurs.

terminal
$ npm install @chargly/sdk

Next: Quickstart or SDK Reference

MCP

Best for: Agent workflows where an AI needs to check balances, meter events, or create checkout sessions. The MCP server exposes Chargly as tools (e.g. chargly.get_wallet, chargly.meter_event).

Run the Chargly MCP server alongside your agent runtime. The agent invokes tools; Chargly handles the API calls.

Next: MCP Support

Stripe

Best for: Credit purchases and top-ups. Stripe Checkout handles payment; Chargly syncs purchases to wallet balances via webhooks.

Define credit packs in Stripe, create checkout sessions via the Chargly API, and configure webhooks so Chargly receives purchase events.

Next: Stripe Integration

Docker / Deployment

Best for: Self-hosting the MCP server or running Chargly infrastructure in your own environment. Use Docker to run the MCP server and connect it to your agent stack.

The Chargly API and core services run in our cloud. Docker is for the MCP server and any local tooling you want to host yourself.

Next: MCP Support for deployment notes

Recommended paths

  • SaaS app?Use the SDK + Stripe
  • Agent workflow?Use MCP + Stripe
  • Self-hosting?Use Docker + MCP

Next