Skip to main content
Notifly Remote MCP is a remote MCP endpoint that clients such as Claude Code and Codex call over the internet. You do not need to install a local server. Add the URL below to your client.
This guide covers the hosted Remote MCP service. Add the URL to your client, then sign in with your Notifly account.
Notifly has three AI tools. The AI Assistant runs in the console and requires Pro or above. Remote MCP connects external AI clients such as ChatGPT and Claude. Agent Skills helps AI coding agents integrate the SDK. The AI Assistant and Remote MCP support data lookups and drafting. Campaign and user journey tools do not send messages, activate resources, or delete campaigns or user journeys. Remote MCP also includes segment and CSV write tools, including saved segment deletion. Review each tool’s permissions before use. Agent Skills changes SDK integration code in your project, so review the generated code and configuration.

How it works

Remote MCP connects your client to the Notifly API through a standard interface. The client reads the tool list and calls the tools needed for your request. Project access follows the permissions of the Notifly account you sign in with. When authentication is required, the client opens the Notifly sign-in page. After sign-in, the client uses the granted access to query projects, campaigns, user journeys, and user status.

Connect Claude Code

Add a remote HTTP MCP server in Claude Code.
Before authentication, claude mcp list or claude mcp get notifly may show Needs authentication. In a Claude Code session, ask a question that requires Notifly tools or start MCP authentication. This opens the browser OAuth flow. Sign in with your Notifly account. Claude Code then calls /mcp with the issued MCP token.
If the connection works, Claude Code first calls list_products or list_projects to find the products and projects you can access.
Some Claude Code versions also let you configure .mcp.json directly. Use a remote url, not a local command. A server added through .mcp.json may initially show Pending approval. Approve it in a Claude Code session before use.

Connect Codex

Add a Streamable HTTP MCP server to Codex CLI with --url.
Recent Codex CLI versions may display a browser authentication URL immediately after codex mcp add. Sign in with your Notifly account in the browser. Codex saves the connection settings. If codex mcp add finishes without authentication, or you need a new token, run this command to sign in through OAuth.
To manage the settings file directly, add the following to ~/.codex/config.toml.
Check the settings.
For an authenticated connection, the Auth column in codex mcp list shows OAuth.

Capabilities

The main Notifly MCP capabilities fall into six categories.
create_campaign and replace_campaign only create or replace campaign drafts. create_user_journey and replace_user_journey only create or fully replace inactive user journey drafts. During journey replacement, existing nodes keep their stored id. New nodes use a request-local ref, and the server generates their IDs. These campaign and journey tools do not activate resources, send messages, or delete resources. Other Remote MCP tools can change segments, upload CSV files, and delete saved segments. Keep write tools subject to approval when required by your organization.

Replace a user journey

When you modify an existing journey, use this order. describe_user_journey_payload(operation: "replace") → describe_user_journey_node_payload(operation: "replace", ...) for each selected node schema → get_user_journey → replace_user_journey replace_user_journey replaces the entire journey. Build the request from the latest get_user_journey result. Send the stored id for each existing node and a request-local ref only for new nodes. To link to an existing node, use *_node_id. To link to a new node, use *_node_ref. The server does not persist ref values. Only inactive drafts can be replaced. Active journeys cannot be replaced.

Example prompts and responses

These examples illustrate response formats. They do not contain real account data.

Find accessible projects

Summarize campaign performance

Diagnose a user’s missing message

Create a campaign draft

Modify an inactive user journey

Troubleshooting