Product facts & evidence

A human-readable view of ReplyNodes product facts. This page is rendered from the canonical source and preserves each fact's verification status and evidence without adding claims.

Version 1.4.0 · Last verified 2026-09-07 · Owner: ReplyNodes product team

Machine-readable source: /product-facts.json

The remote MCP server endpoint is https://app.replynodes.com/api/mcp

verified

https://app.replynodes.com/api/mcp

Evidence: POST without auth returns HTTP 401 (endpoint exists, auth required). Live probe 2026-08-16.

The MCP OAuth endpoint is https://app.replynodes.com/api/mcp-oauth

verified

https://app.replynodes.com/api/mcp-oauth

Evidence: GET without auth returns HTTP 401 (endpoint exists). Live probe 2026-08-16.

The REST Public API base URL is https://app.replynodes.com/api/public/v1

verified

https://app.replynodes.com/api/public/v1

Evidence: GET https://app.replynodes.com/api/public/v1/posts returns 401; backend controller @Controller('/public/v1') in apps/backend/src/public-api/routes/v1/public.integrations.controller.ts (replynodes/replynodes-app). Live probe 2026-08-16.

https://api.replynodes.com/public/v1 is NOT a valid base URL (legacy host)

removed

https://api.replynodes.com/public/v1

Evidence: Live probes 404 on /public/v1/posts, /public/v1/social/twitter, /is-connected, and the bare base. 2026-08-16.

API keys are created at app.replynodes.com → Developers (sidebar) → 'API Keys & Agents' at URL /developers

verified

app.replynodes.com/developers

Evidence: apps/frontend/src/components/layout/top.menu.tsx path '/developers'; apps/frontend/src/components/public-api/developers.page.component.tsx title 'API Keys & Agents'. The Developers page is the documented API-key location. 2026-08-16.

'Settings → Public API → Access' is NOT where API keys live (legacy docs path)

removed

Settings → Public API → Access

Evidence: No API key tab exists in the app Settings page (see api-key-location). 2026-08-16.

ReplyNodes supports 30+ social networks

verified

30+

Evidence: App social providers: 36 files in libraries/nestjs-libraries/src/integrations/social/ covering 31 distinct networks (bluesky, dev.to, discord, dribbble, facebook, farcaster, gmb, hashnode, instagram, kick, lemmy, linkedin, listmonk, mastodon, medium, mewe, moltbook, nostr, pinterest, reddit, skool, slack, telegram, threads, tiktok, twitch, vk, whop, wordpress, x, youtube). 2026-08-16.

'28+ channels' is a stale count

removed

28+

Evidence: Superseded by platform-count (30+, 31 distinct networks in app repo). 2026-08-16.

The MCP server is listed in the official MCP Registry as io.github.replynodes/mcp, version 0.1.2, npm @replynodes/mcp

verified

io.github.replynodes/mcp v0.1.2

Evidence: curl https://registry.modelcontextprotocol.io/v0.1/servers?search=replynodes returned the entry; npm registry shows @replynodes/mcp v0.1.2. 2026-08-16.

ReplyNodes uses subscription-plus-unified-credits pricing for read-only data APIs

verified

Free $0/500 one-time; Developer $19/month/10,000 credits; Pro $99/month/100,000 credits

Evidence: Canonical pricing contract at https://raw.githubusercontent.com/replynodes/.github/main/replynodes-pricing.html and source components/pricing-plans.ts in replynodes-site. 2026-09-07.

Paid plans support optional capped overage; Free has no overage

verified

Developer $20/10,000 additional credits; Pro $10/10,000 additional credits

Evidence: Canonical pricing contract at https://raw.githubusercontent.com/replynodes/.github/main/replynodes-pricing.html. Paid plans require an explicit monthly overage cap. 2026-09-07.

MCP tool names are camelCase: integrationSchedulePostTool, integrationSchema, triggerTool, uploadFromUrlTool, generateImageTool, generateVideoOptions, generateVideoTool, videoFunctionTool, groupList, integrationList, postsList, postsUpdate, postAnalytics, ask_replynodes, draftPostFromSource, planFounderDistributionAngles

verified

camelCase tool catalog

Evidence: Live MCP server tool catalog; site app/social-media-mcp-server/page.tsx uses camelCase correctly. 2026-08-16.

Remote MCP authenticates with 'Authorization: Bearer <key>' (Bearer prefix required)

verified

Authorization: Bearer <key>

Evidence: docs mcp/introduction.mdx, hermes.mdx, claude.mdx; site app/social-media-mcp-server/page.tsx. 2026-08-16.

REST Public API authenticates with the raw API key in the Authorization header (no Bearer prefix)

verified

Authorization: <raw key> (no Bearer)

Evidence: docs public-api/index.mdx and mcp/introduction.mdx. 2026-08-16.

ReplyNodes has an open-source, self-hostable edition

removed

UNVERIFIABLE

Evidence: App repo replynodes/replynodes-app is PRIVATE (gh repo view --json visibility → PRIVATE); docs repo has NO self-hosting page (find content -iname '*self*host*' → none). 2026-08-16.

Supported AI clients (verified): Claude (Claude Code, Claude Desktop, Claude.ai), Cursor, Codex, OpenClaw, and Hermes connect via the remote MCP server; ChatGPT connects via GPT Actions (REST). Each has a documented setup guide.

verified

Claude, Cursor, Codex, OpenClaw, Hermes (MCP); ChatGPT (GPT Actions)

Evidence: replynodes-mcp README.md L6 lists Claude, Cursor, Codex, OpenClaw, Hermes, ChatGPT; README setup sections for Claude Code plugin, Claude Desktop manual config, Cursor/Windsurf, Codex CLI/OpenClaw; package.json description lists the same six; docs mcp/claude.mdx, hermes.mdx, openclaw.mdx, chatgpt-codex.mdx (chatgpt-codex states ChatGPT/Custom GPTs do not run MCP directly — equivalent is a GPT Action). Verified 2026-08-16.

The MCP discovery endpoint is https://app.replynodes.com/.well-known/mcp

verified

https://app.replynodes.com/.well-known/mcp

Evidence: GET https://app.replynodes.com/.well-known/mcp returns HTTP 307 redirect to https://app.replynodes.com/auth (endpoint live, auth-gated). Live probe 2026-08-16. Docs mcp/capabilities.mdx reference discovery at .well-known/mcp.

OAuth app tokens are prefixed pos_ and authenticate the same way as API keys for REST and MCP

verified

pos_ prefixed OAuth app tokens

Evidence: docs public-api/oauth.mdx ('All OAuth tokens are prefixed with pos_'), support/faq.mdx, mcp/capabilities.mdx, cli/introduction.mdx; app repo apps/frontend/src/components/public-api/public.component.tsx: 'you will receive a pos_ prefixed token that works with the API and MCP — just like an API Key'. Verified 2026-08-16.

replynodes-cli v0.1.0 is published on npm (public), binary name 'replynodes'

verified

replynodes-cli@0.1.0

Evidence: npm registry probe https://registry.npmjs.org/replynodes-cli returns 200, dist-tags.latest 0.1.0, bin replynodes (2026-08-16).

@replynodes/node is NOT published on npm (the docs previously documented it as an SDK)

removed

E404

Evidence: npm registry probe https://registry.npmjs.org/@replynodes/node returns HTTP 404 (2026-08-16).