Dodo Payments Node MCP Server logo

Dodo Payments Node MCP Server

by dodopayments

The Dodo Payments Node MCP Server provides a standardized interface for interacting with the Dodo Payments API. It is generated using Stainless and allows for easy integration with AI tools and other applications.

View on GitHub

Last updated: N/A

What is Dodo Payments Node MCP Server?

The Dodo Payments Node MCP Server is a Model Context Protocol (MCP) server that exposes the Dodo Payments API as a set of tools that can be used by AI models and other applications. It allows you to interact with various Dodo Payments resources like payments, subscriptions, customers, products, and more.

How to use Dodo Payments Node MCP Server?

The server can be run directly via npx or integrated into existing MCP clients. Configuration often involves setting the DODO_PAYMENTS_API_KEY environment variable. You can filter exposed tools using command-line options to manage the context window size for your AI.

Key features of Dodo Payments Node MCP Server

  • Generated with Stainless for type safety and consistency

  • Exposes a wide range of Dodo Payments API endpoints as tools

  • Supports filtering tools by name, resource, and operation type

  • Can be integrated with existing MCP clients

  • Allows for custom endpoint definitions

Use cases of Dodo Payments Node MCP Server

  • Integrating Dodo Payments functionality into AI-powered applications

  • Automating payment processing workflows

  • Building custom payment interfaces

  • Creating AI agents that can manage subscriptions and invoices

FAQ from Dodo Payments Node MCP Server

How do I install the MCP server?

You can install it directly via npx or through an existing MCP client. Refer to the client's documentation for specific instructions.

How do I configure the server?

The primary configuration involves setting the DODO_PAYMENTS_API_KEY environment variable.

How can I filter the available tools?

Use the --tool, --resource, and --operation command-line options to include or exclude specific tools.

Can I add my own custom endpoints?

Yes, you can define your own endpoints and initialize the server with them.

What resources are available?

The server exposes resources such as payments, subscriptions, invoices.payments, licenses, license_keys, license_key_instances, customers, customers.customer_portal, refunds, disputes, payouts, webhook_events, products, products.images, misc, and discounts.