Integrations

MCP

Use the canonical remote server URL, https://mcp.replynodes.com/mcp, with an MCP-capable client. Interactive clients use Better Auth MCP OAuth through https://auth.replynodes.com; headless clients can use a ReplyNodes API key. See the MCP guide for the two setup paths. Organization context comes from the authenticated identity or key, never from a client-supplied organization id.

REST

Any HTTP client works. Use the base URL from the API contract, bearer authentication, and the exact operation parameters shown in the API Reference. Read Errors before adding retries.

SDKs

The monorepo has an OpenAPI Generator setup, not runtime SDK packages. Its target configurations are kept under sdk-generation/config/ and are generated from the repository's SDK input snapshot. For live route names and schemas, use the runtime capability OpenAPI contract at https://docs.replynodes.com/api/openapi.json and re-check it before installing or generating a client. The downstream package names and intended language targets are documented in sdk-generation/README.md; installation instructions, auth setup, first requests, pagination, and errors belong to each downstream repository once it is available.

Do not invent an install command or client interface for a package that has not been verified. A generated client must preserve bearer auth, GET-only operations, the { data, meta } envelope, and meta.next_cursor pagination where an endpoint exposes it.

Agent skills

The catalog under services/social-data-skills/ generates provider-specific skill packages, MCP schemas, endpoint examples, and llms.txt material. Start at its catalog/README.md, then use the provider package's SKILL.md and INSTALL.md. Generated artifacts are not hand-edited; the runtime capability OpenAPI document under services/replynodes-fetcher/internal/gateway/ is the source used for this docs app's API reference and LLM indexes.