Dodo Payments

Official
by dodopayments

Integrations

  • 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:

export DODO_PAYMENTS_API_KEY="My API Key" npx -y dodopayments-mcp

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:

{ "mcpServers": { "dodopayments_api": { "command": "npx", "args": ["-y", "dodopayments-mcp", "--client=claude"], "env": { "DODO_PAYMENTS_API_KEY": "My API Key" } } } }

Filtering 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

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

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 schemas
      • valid-json: Enable JSON string parsing for arguments
      • refs: Enable support for $ref pointers in schemas
      • unions: Enable support for union types (anyOf) in schemas
      • formats: 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

Examples

  1. Filter for read operations on cards:
--resource=cards --operation=read
  1. Exclude specific tools while including others:
--resource=cards --no-tool=create_cards
  1. Configure for Cursor client with custom max tool name length:
--client=cursor --capability=tool-name-length=40
  1. Complex filtering with multiple criteria:
--resource=cards,accounts --operation=read --tag=kyc --no-tool=create_cards

Importing the tools and server individually

// Import the server, generated endpoints, or the init function import { server, endpoints, init } from "dodopayments-mcp/server"; // import a specific tool import createPayments from "dodopayments-mcp/tools/payments/create-payments"; // initialize the server and all endpoints init({ server, endpoints }); // manually start server const transport = new StdioServerTransport(); await server.connect(transport); // or initialize your own server with specific tools const myServer = new McpServer(...); // define your own endpoint const myCustomEndpoint = { tool: { name: 'my_custom_tool', description: 'My custom tool', inputSchema: zodToJsonSchema(z.object({ a_property: z.string() })), }, handler: async (client: client, args: any) => { return { myResponse: 'Hello world!' }; }) }; // initialize the server with your custom endpoints init({ server: myServer, endpoints: [createPayments, myCustomEndpoint] });

Available Tools

The following tools are available in this MCP server.

Resource payments:

  • create_payments (write):
  • retrieve_payments (read):
  • list_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): If code 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 /discounts
  • delete_discounts (write): DELETE /discounts/{discount_id}

Resource addons:

  • create_addons (write):
  • retrieve_addons (read):
  • update_addons (write):
  • list_addons (read):
  • update_images_addons (write):
-
security - not tested
A
license - permissive license
-
quality - not tested

remote-capable server

The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.

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

  1. Installation
    1. Direct invocation
    2. Via MCP Client
  2. Filtering tools
    1. Specifying the MCP Client
    2. Examples
  3. Importing the tools and server individually
    1. Available Tools
      1. Resource payments:
      2. Resource subscriptions:
      3. Resource invoices.payments:
      4. Resource licenses:
      5. Resource license_keys:
      6. Resource license_key_instances:
      7. Resource customers:
      8. Resource customers.customer_portal:
      9. Resource refunds:
      10. Resource disputes:
      11. Resource payouts:
      12. Resource webhook_events:
      13. Resource products:
      14. Resource products.images:
      15. Resource misc:
      16. Resource discounts:
      17. Resource addons:

    Related MCP Servers

    • A
      security
      F
      license
      A
      quality
      An MCP server that integrates with Fewsats allowing AI agents to securely purchase anything by retrieving balances, accessing payment methods, and processing payments.
      Last updated -
      4
      11
      Python
    • A
      security
      A
      license
      A
      quality
      An MCP server providing unified access to blockchain operations, bridging, swapping, and crypto trading strategies for AI agents.
      Last updated -
      20
      182
      Python
      GPL 3.0
      • Apple
      • Linux
    • -
      security
      A
      license
      -
      quality
      An 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 -
      2
      TypeScript
      MIT License
      • Apple
    • A
      security
      A
      license
      A
      quality
      MCP Server for Google Cloud Healthcare API enables Agentic AI for a variety of FHIR-based digital health solutions, from smarter clinical workflows for Health Systems to Pre-Auth frameworks for Payers!
      Last updated -
      15
      2
      JavaScript
      MIT License
      • Apple

    View all related MCP servers

    ID: ka460b1cud