Dodo Agent Plugin vs Contracts Wizard

A side-by-side look at the Dodo Agent Plugin and Contracts Wizard MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Dodo Agent Plugin logoDodo Agent PluginFinance & Fintech · Local subprocess (stdio)Official Dodo Payments MCP servers — dodopayments-api for live payments, subscriptions, customers, products, refunds, license keys, and usage-based billing (browser OAuth, no API key needed) and dodo-knowledge for semantic search over Dodo Payments documentation.85ExcellentAuth: oauth 2.0Contracts Wizard logoContracts WizardFinance & Fintech · Local subprocess (stdio)A Model Context Protocol (MCP) server that allows AI agents to generate secure smart contracts in multiples languages based on OpenZeppelin Wizard templates.68GreatAuth: no auth required

Verdict: choose Dodo Agent Plugin for finance & fintech work as a local process; choose Contracts Wizard for finance & fintech as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Dodo Agent Plugin logoChoose Dodo Agent Plugin when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like execute, search_docs.
Explore Dodo Agent Plugin

Contracts Wizard logoChoose Contracts Wizard when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like solidity-erc20, solidity-erc721, solidity-erc1155.
Explore Contracts Wizard

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDodo Agent Plugin logoDodo Agent PluginContracts Wizard logoContracts Wizard
CategoryFinance & FintechFinance & Fintech
Quality signal85/100 · Excellent68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthOAuth 2.0No auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars6295
Directory activity 7 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools233

Tools & capabilities

Dodo Agent Plugin tools 2

  • executeRuns JavaScript code to interact with the Dodo Payments API. You are a skilled TypeScript programmer writing code to interface with the service. Define an async function named "run" that takes a single parameter of an initialized SDK client and it will be run. For example: ``` async function run(client) { const checkoutSessionResponse = await client.checkoutSessions.create({ product_cart: [{ product_id: 'pdt_example', quantity: 1 }] }); console.log(checkoutSessionResponse.session_id); } ``` You will be returned anything that your function returns, plus the results of any console.log statements. Do not add try-catch blocks for single API calls. The tool will handle errors for you. Do not add comments unless necessary for generating better code. Code will run in a container, and cannot interact with the network outside of the given SDK client. Variables will not persist between calls, so make sure to return or log any data you might need later. Remember that you are writing TypeScript code, so you need to be careful with your types. Always type dynamic key-value stores explicitly as Record<string, YourValueType> instead of {}.
  • search_docsSearch SDK documentation to find methods, parameters, and usage examples for interacting with the API. Use this before writing code when you need to discover the right approach.

Contracts Wizard tools 33

  • solidity-erc20Make a fungible token per the ERC-20 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • solidity-erc721Make a non-fungible token per the ERC-721 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • solidity-erc1155Make a non-fungible token per the ERC-1155 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • solidity-stablecoinMake a stablecoin token that uses the ERC-20 standard. This contract type does not support upgradeability. Experimental, some features are not audited and are subject to change. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • solidity-rwaMake a real-world asset token that uses the ERC-20 standard. This contract type does not support upgradeability. Experimental, some features are not audited and are subject to change. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • solidity-accountMake an account contract that follows the ERC-4337 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • solidity-governorMake a contract to implement governance, such as for a DAO. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • solidity-customMake a custom smart contract. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • cairo-erc20Make a fungible token per the ERC-20 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • cairo-erc721Make a non-fungible token per the ERC-721 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • cairo-erc1155Make a non-fungible token per the ERC-1155 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • cairo-erc6909Make a minimal multi-token per the ERC-6909 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
  • +21 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Dodo Agent Plugin

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dodopayments-dodo-agent-plugin": {
      "command": "npx",
      "args": [
        "-y",
        "dodopayments-mcp@latest"
      ]
    }
  }
}

Contracts Wizard

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openzeppelin-contracts-wizard": {
      "command": "npx",
      "args": [
        "-y",
        "@openzeppelin/contracts-mcp"
      ]
    }
  }
}

Frequently asked questions

Dodo Agent Plugin is categorized under Finance & Fintech and uses a local stdio subprocess. Contracts Wizard belongs to Finance & Fintech and uses a local stdio subprocess. Pick Dodo Agent Plugin for finance & fintech work and Contracts Wizard for finance & fintech.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Dodo Agent Plugin is listed as free. Auth: oauth 2.0. Contracts Wizard is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add dodopayments-dodo-agent-plugin and openzeppelin-contracts-wizard as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dodo Agent Plugin has a quality signal of 85/100 (Excellent) with 7 views, 0 installs and 6 GitHub stars. Contracts Wizard has 68/100 (Great) with 1 views, 0 installs and 295 GitHub stars.