Diagnose and fix PayPal MCP server initialization issues by installing a custom runner script.
This skill fixes common initialization errors with the PayPal MCP server, such as npx failures, "tools argument missing", or ESM/CommonJS conflicts.
Use this skill when:
--tools arguments.require is not defined errors.npx @paypal/agent-toolkit command does not work.The default @paypal/agent-toolkit package does not have a bin entry/executable. This skill provides a custom runner script (run-paypal-mcp.cjs) that manually initializes the toolkit and connects it to the MCP SDK.
Copy the resource file resources/run-paypal-mcp.cjs to your project root (e.g., scripts/run-paypal-mcp.cjs or just ./run-paypal-mcp.cjs).
Ensure your .env.local or MCP environment config has:
PAYPAL_ACCESS_TOKEN: A valid access token.PAYPAL_ENVIRONMENT: PRODUCTION or SANDBOX.Edit your mcp_config.json (or .cursor/mcp.json) to use the new script with node instead of npx.
"paypal-mcp-server": {
"command": "node",
"args": [
"/absolute/path/to/your/run-paypal-mcp.cjs"
],
"env": {
"PAYPAL_ACCESS_TOKEN": "...",
"PAYPAL_ENVIRONMENT": "PRODUCTION"
}
}
Restart Antigravity or the MCP server functionality.
The script requires:
@paypal/agent-toolkit@modelcontextprotocol/sdkIf you see zod errors, check for v3 export issues in the zod package and patch if necessary (add "./v3": "./lib/index.js" to node_modules/zod/package.json).