The public README currently leads with scheduling, connected channels, posts, media uploads, and app.replynodes.com/api/public/v1. This conflicts with the current ReplyNodes MCP/context positioning. Decide whether this repo remains a supported legacy client; if yes, clearly label its scope and update endpoint/auth links, otherwise prepare an archive/redirect proposal. Do not delete, rename, or archive without owner approval.
The public README currently leads with scheduling, connected channels, posts, media uploads, and app.replynodes.com/api/public/v1. This conflicts with the current ReplyNodes MCP/context positioning. Decide whether this repo remains a supported legacy client; if yes, clearly label its scope and update endpoint/auth links, otherwise prepare an archive/redirect proposal. Do not delete, rename, or archive without owner approval.