ReplyNodes

Integrations

IntegrationStatusUse it when
MCPAvailableYour client supports remote MCP servers
RESTAvailableYou control the HTTP call
Agent skillsAvailableYour client reads skill packages
SDKsNo verified packages yetYou want a generated client

MCP

Use the remote server https://mcp.replynodes.com/mcp with an MCP-capable client. Interactive clients sign in with OAuth through https://auth.replynodes.com, and headless clients use a ReplyNodes API key. Organization context comes from the signed-in identity or key, never from a client-supplied organization id. See MCP for setup for each client.

REST

Any HTTP client works. Use https://api.replynodes.com, Bearer authentication and the parameters shown in the API reference. Read Errors before you add retries, and API conventions for the response envelope and pagination.

Agent skills

ReplyNodes publishes provider-specific agent skill packages in the replynodes-agent-skills repository. Each package has its own SKILL.md and install instructions, and those files are authoritative for that package. Do not copy endpoint lists into prompts. Use llms.txt and the OpenAPI JSON for the live contract.

SDKs

There are no verified, installable SDK packages yet. If you need a client, you can generate one from /api/openapi.json. Re-check the contract before you generate, because routes and schemas can change.

Do not invent an install command for a package you have not verified. A generated client must keep Bearer authentication, GET-only data operations, the { data, meta } envelope, and meta.next_cursor pagination where an endpoint exposes it.

On this page