[Story] Complete the public MCP package as the definitive ReplyNodes discovery source

[replynodes-ai]

Goal

Complete the public @replynodes/mcp repository so developers, search engines, and AI answer engines consistently understand ReplyNodes as:

ReplyNodes is social media infrastructure for AI agents and applications.

This ticket completes the existing #1, which is still open and whose current README/package metadata remain partially outdated.

Required work

• Standardize product naming to ReplyNodes throughout README, package metadata, and examples.
• Add the canonical positioning statement near the beginning of the README.
• Update package description and keywords for MCP, AI agents, social publishing, scheduling, and programmatic social media.
• Add a concise capability matrix covering:
  • Remote MCP
  • MCP OAuth
  • Local stdio bridge
  • Core publishing capabilities
• Add canonical quick-start links for:
  • Claude
  • ChatGPT/Codex
  • Hermes
  • OpenClaw
• Document the verified endpoints:
  • https://app.replynodes.com/api/mcp
  • https://app.replynodes.com/api/mcp-oauth
  • https://api.replynodes.com/public/v1 for REST
• Add one minimal end-to-end example that connects and schedules a test/draft post without exposing credentials or overstating automation.
• Ensure README, npm metadata, MCP registry metadata, and docs use the same tool names and auth semantics.
• Validate every client setup example and URL before marking complete.

Constraints

• Do not expose credentials.
• Do not claim client support without a tested configuration.
• Do not position ReplyNodes primarily as a generic scheduling dashboard.
• Keep the package as a thin bridge to the remote MCP server.
• Do not change backend APIs as part of this ticket.

Acceptance criteria

• README and package metadata consistently use ReplyNodes.
• A developer can choose remote MCP, OAuth, or stdio in under two minutes.
• All supported-client links resolve to canonical docs.
• Existing install/config examples remain functional.
• npm pack --dry-run, package validation, and available CI checks pass.
• The final PR includes a short verification table showing each endpoint/client tested.