Mcp Server

What is Mcp Server?

It provides convenient access to the Dodo Payments REST API from server-side TypeScript or JavaScript.

How to use Mcp Server?

Install via npm install dodopayments, create a client with a bearer token and an environment option (test_mode or live_mode), then call methods like client.payments.create().

Key features of Mcp Server

• Full TypeScript definitions for request params and response fields.
• Automatic retries (2 retries by default) with exponential backoff.
• Configurable timeouts (1 minute default).
• Auto-pagination for list endpoints using async iteration.
• Customizable fetch client and HTTP(S) agent support.
• Access to raw Response data via .asResponse() and .withResponse().

Use cases of Mcp Server

• Integrate Dodo Payments payment processing into Node.js applications.
• Manage payments, customers, and product carts programmatically.
• Handle API errors with typed error classes (e.g., BadRequestError).
• Automatically paginate through large lists of payments or other resources.
• Proxy API requests through custom HTTP agents.

FAQ from Mcp Server

How is authentication handled?

The client requires a bearer token, typically set via the DODO_PAYMENTS_API_KEY environment variable, and passed in the constructor.

How does the library handle errors?

It throws subclasses of APIError (e.g., BadRequestError, RateLimitError) for non‑success status codes; connection errors raise APIConnectionError.

Does the library support pagination?

Yes. List methods are paginated; you can use for await…of to iterate over all pages automatically, or manually request pages with getNextPage().

Can I customize the HTTP agent or fetch client?

Yes. Provide an httpAgent option for proxies, or pass a custom fetch function when instantiating the client.

What are the runtime requirements?

The library is designed for server‑side TypeScript or JavaScript. It uses node-fetch in Node by default, but supports web‑standard fetch via shims.