Used for schema validation in custom endpoints, allowing developers to define input schemas for tools using Zod's type system which are then converted to JSON Schema through the zodToJsonSchema function.
Dodo Payments Node MCP Server
It is generated with Stainless.
Installation
Direct invocation
You can run the MCP Server directly via npx
:
Via MCP Client
There is a partial list of existing clients at modelcontextprotocol.io. If you already have a client, consult their documentation to install the MCP server.
For clients with a configuration JSON, it might look something like this:
Exposing endpoints to your MCP Client
There are two ways to expose endpoints as tools in the MCP server:
- Exposing one tool per endpoint, and filtering as necessary
- Exposing a set of tools to dynamically discover and invoke endpoints from the API
Filtering endpoints and tools
You can run the package on the command line to discover and filter the set of tools that are exposed by the MCP Server. This can be helpful for large APIs where including all endpoints at once is too much for your AI's context window.
You can filter by multiple aspects:
--tool
includes a specific tool by name--resource
includes all tools under a specific resource, and can have wildcards, e.g.my.resource*
--operation
includes just read (get/list) or just write operations
Dynamic tools
If you specify --tools=dynamic
to the MCP server, instead of exposing one tool per endpoint in the API, it will
expose the following tools:
list_api_endpoints
- Discovers available endpoints, with optional filtering by search queryget_api_endpoint_schema
- Gets detailed schema information for a specific endpointinvoke_api_endpoint
- Executes any endpoint with the appropriate parameters
This allows you to have the full set of API endpoints available to your MCP Client, while not requiring that all of their schemas be loaded into context at once. Instead, the LLM will automatically use these tools together to search for, look up, and invoke endpoints dynamically. However, due to the indirect nature of the schemas, it can struggle to provide the correct properties a bit more than when tools are imported explicitly. Therefore, you can opt-in to explicit tools, the dynamic tools, or both.
See more information with --help
.
All of these command-line options can be repeated, combined together, and have corresponding exclusion versions (e.g. --no-tool
).
Use --list
to see the list of available tools, or see below.
Specifying the MCP Client
Different clients have varying abilities to handle arbitrary tools and schemas.
You can specify the client you are using with the --client
argument, and the MCP server will automatically
serve tools and schemas that are more compatible with that client.
--client=<type>
: Set all capabilities based on a known MCP client- Valid values:
openai-agents
,claude
,claude-code
,cursor
- Example:
--client=cursor
- Valid values:
Additionally, if you have a client not on the above list, or the client has gotten better over time, you can manually enable or disable certain capabilities:
--capability=<name>
: Specify individual client capabilities- Available capabilities:
top-level-unions
: Enable support for top-level unions in tool schemasvalid-json
: Enable JSON string parsing for argumentsrefs
: Enable support for $ref pointers in schemasunions
: Enable support for union types (anyOf) in schemasformats
: Enable support for format validations in schemas (e.g. date-time, email)tool-name-length=N
: Set maximum tool name length to N characters
- Example:
--capability=top-level-unions --capability=tool-name-length=40
- Example:
--capability=top-level-unions,tool-name-length=40
- Available capabilities:
Examples
- Filter for read operations on cards:
- Exclude specific tools while including others:
- Configure for Cursor client with custom max tool name length:
- Complex filtering with multiple criteria:
Importing the tools and server individually
Available Tools
The following tools are available in this MCP server.
Resource payments
:
create_payments
(write
):retrieve_payments
(read
):list_payments
(read
):retrieve_line_items_payments
(read
):
Resource subscriptions
:
create_subscriptions
(write
):retrieve_subscriptions
(read
):update_subscriptions
(write
):list_subscriptions
(read
):change_plan_subscriptions
(write
):charge_subscriptions
(write
):
Resource invoices.payments
:
retrieve_invoices_payments
(read
):
Resource licenses
:
activate_licenses
(write
):deactivate_licenses
(write
):validate_licenses
(write
):
Resource license_keys
:
retrieve_license_keys
(read
):update_license_keys
(write
):list_license_keys
(read
):
Resource license_key_instances
:
retrieve_license_key_instances
(read
):update_license_key_instances
(write
):list_license_key_instances
(read
):
Resource customers
:
create_customers
(write
):retrieve_customers
(read
):update_customers
(write
):list_customers
(read
):
Resource customers.customer_portal
:
create_customers_customer_portal
(write
):
Resource refunds
:
create_refunds
(write
):retrieve_refunds
(read
):list_refunds
(read
):
Resource disputes
:
retrieve_disputes
(read
):list_disputes
(read
):
Resource payouts
:
list_payouts
(read
):
Resource webhook_events
:
retrieve_webhook_events
(read
):list_webhook_events
(read
):
Resource products
:
create_products
(write
):retrieve_products
(read
):update_products
(write
):list_products
(read
):delete_products
(write
):unarchive_products
(write
):
Resource products.images
:
update_products_images
(write
):
Resource misc
:
list_supported_countries_misc
(read
):
Resource discounts
:
create_discounts
(write
): Ifcode
is omitted or empty, a random 16-char uppercase code is generated.retrieve_discounts
(read
): GET /discounts/{discount_id}update_discounts
(write
): PATCH /discounts/{discount_id}list_discounts
(read
): GET /discountsdelete_discounts
(write
): DELETE /discounts/{discount_id}
Resource addons
:
create_addons
(write
):retrieve_addons
(read
):update_addons
(write
):list_addons
(read
):update_images_addons
(write
):
Resource brands
:
create_brands
(write
):retrieve_brands
(read
): Thin handler just callsget_brand
and wraps inJson(...)
update_brands
(write
):list_brands
(read
):update_images_brands
(write
):
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
The Dodo Payments MCP Server integrates with agentic frameworks to provide a lightweight, serverless-compatible interface for AI-driven payment operations like billing, subscriptions, and customer management. It enables autonomous agents to securely act on behalf of users using the Dodo Payments
- Installation
- Exposing endpoints to your MCP Client
- Importing the tools and server individually
- Available Tools
- Resource payments:
- Resource subscriptions:
- Resource invoices.payments:
- Resource licenses:
- Resource license_keys:
- Resource license_key_instances:
- Resource customers:
- Resource customers.customer_portal:
- Resource refunds:
- Resource disputes:
- Resource payouts:
- Resource webhook_events:
- Resource products:
- Resource products.images:
- Resource misc:
- Resource discounts:
- Resource addons:
- Resource brands:
Related MCP Servers
- AsecurityFlicenseAqualityAn MCP server that integrates with Fewsats allowing AI agents to securely purchase anything by retrieving balances, accessing payment methods, and processing payments.Last updated -413Python
Armor Crypto MCPofficial
AsecurityAlicenseAqualityAn MCP server providing unified access to blockchain operations, bridging, swapping, and crypto trading strategies for AI agents.Last updated -20128PythonGPL 3.0- -securityAlicense-qualityAn MCP server that enables secure, PCI-compliant payment processing during voice calls via Twilio API, providing asynchronous callbacks and guided workflow for agent-assisted payments.Last updated -2TypeScriptMIT License
- -security-license-qualityZero Trust Access AI Agent - MCP ServerLast updated -Python