ChatGPT and Codex + ReplyNodes

Read public data with ChatGPT and Codex

Use ChatGPT's GPT Action or Codex's MCP client to read public data. Neither path exposes write or mutation tools.

Canonical product boundary

ReplyNodes exposes read-only public data at https://api.replynodes.com. It does not provide write or mutation tools on this API.

Preferred remote MCP

Use the streamable HTTP MCP endpoint https://mcp.replynodes.com/mcp. Clients with native MCP OAuth can use Better Auth at https://auth.replynodes.com with scope mcp:read. For headless or manual setup, use a ReplyNodes API key beginning with rn_test_ or rn_live_ as a Bearer token. Organization context comes from the authenticated identity or key; clients do not send an organization id. Start the documented claim flow at the authentication guide if you need a key.

{
  "mcpServers": {
    "replynodes": {
      "url": "https://mcp.replynodes.com/mcp",
      "headers": { "Authorization": "Bearer ${REPLYNODES_API_KEY}" }
    }
  }
}

REST fallback

curl -sS https://api.replynodes.com/v1/capabilities \
  -H "Authorization: Bearer $REPLYNODES_API_KEY"

Use GET /v1/capabilities as the live source of truth for available providers, routes, schemas, and billing. Do not invent a route or assume a package version.

Claim a Read API key →Read the quickstart →Read the MCP guide →