Paddle MCP Server

Instructions

Implementation Reference

• src/functions.ts:551-562 (handler)

  The main handler function that executes the tool logic by calling paddle.notifications.replay(notificationId) and handling errors.
  export const replayNotification = async ( paddle: Paddle, params: z.infer<typeof Parameters.replayNotificationParameters>, ) => { try { const { notificationId } = params; const notification = await paddle.notifications.replay(notificationId); return notification; } catch (error) { return error; } };
• src/api.ts:54-54 (registration)

  Maps the tool method constant to the handler function in the toolMap used by PaddleAPI.run().
  [TOOL_METHODS.REPLAY_NOTIFICATION]: funcs.replayNotification,
• src/tools.ts:794-803 (schema)

  Tool schema definition including input parameters (params.replayNotificationParameters), description, name, and required permissions/actions.
  method: "replay_notification", name: "Replay a notification", description: prompts.replayNotificationPrompt, parameters: params.replayNotificationParameters, actions: { notifications: { write: true, create: true, }, },
• src/constants.ts:46-46 (registration)

  Constant definition for the tool method name used in registrations.
  REPLAY_NOTIFICATION: "replay_notification",
• src/prompts.ts:822-847 (helper)

  Detailed prompt/description explaining the tool's purpose, warnings, and usage details.
  export const replayNotificationPrompt = ` This tool will resend a delivered or failed notification, like a webhook notification, using its ID. ${checkBeforeWarning} Paddle creates a new notification entity for the replay, related to the same eventId. The response includes the new notificationId of the created notification. Notifications older than 90 days aren't retained. If trying to replay a notification that's no longer retained, Paddle returns an error. Only notifications with the origin of event can be replayed. Replaying a notification created for a replay isn't possible. Check the following details to understand the success or failure of the notification according to Paddle and debug issues: - status: Status of the notification. - notAttempted: Paddle hasn't yet tried to deliver this notification. - needsRetry: Paddle tried to deliver this notification, but it failed. It's scheduled to be retried. - delivered: Paddle delivered this notification successfully. - failed: Paddle tried to deliver this notification, but all attempts failed. It's not scheduled to be retried. - origin: Describes how this notification was created. - event: Notification created when a subscribed event occurred. - replay: Notification created when a notification with the origin event was replayed. - deliveredAt: RFC 3339 datetime string of when this notification was delivered. null if not yet delivered successfully. - lastAttemptAt: RFC 3339 datetime string of when this notification was last attempted. - retryAt: RFC 3339 datetime string of when this notification is scheduled to be retried. - timesAttempted: How many times delivery of this notification has been attempted. `;