> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notifly.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Notifly to Claude

> Add Notifly Remote MCP as a custom connector in Claude and connect with OAuth.

Claude connectors connect remote MCP servers to the Claude web app. Add the Notifly connector to look up projects, campaigns, user journeys, and user status, and create drafts within a Claude conversation.

```text theme={null}
https://api.notifly.tech/mcp
```

> [!NOTE]
>
> Use the Notifly Remote MCP URL for the custom connector. You do not need a manually registered OAuth client ID or secret.

## Connect

1. In Claude, open **Plugins**. Earlier versions show **Customize > Connectors**.
2. Select **Add > Add custom connector**. Earlier versions show **+ Add**.
3. Enter these values.

| Field | Value |
| - | - |
| Name | `Notifly` |
| MCP server URL | `https://api.notifly.tech/mcp` |

If your version shows **OAuth client ID** and **OAuth client secret**, leave both blank.

4. If Claude displays **Continue**, continue through the detected authentication settings. Use OAuth sign-in and **Register automatically** if an OAuth client choice appears.
5. Select **Add** if your version displays this button.
6. Select **Notifly** in the connector list, then select **Connect** if sign-in has not started.
7. Sign in with your Notifly account when the sign-in page opens.
8. Return to Claude and check for **Connected** under **Overview**. Open **Permissions** to review the available tools. Earlier versions show **Disconnect** and the tool list together.

For a managed organization, an authorized owner or administrator must make the connector available before members connect their own accounts. See [Claude's custom connector setup](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for current role requirements.

![The connected Notifly custom connector in Claude](https://mintcdn.com/notifly/dcFO7QF5JScPffiH/images/i18n/en/developer-guide/devtools/claude-notifly-connector-connected.png?fit=max\&auto=format\&n=dcFO7QF5JScPffiH\&q=85\&s=6199e3ef40caa8e90c9471c422b950bc)

## OAuth authentication flow

Claude reads Notifly's OAuth discovery metadata when it connects to `https://api.notifly.tech/mcp`. Notifly supports dynamic client registration and PKCE, so you do not need to enter an OAuth client ID or secret manually.

The authentication flow usually follows these steps.

1. Claude accesses `/mcp`.
2. Notifly tells Claude that sign-in is required.
3. Claude opens the Notifly sign-in page in the browser.
4. You sign in with your Notifly account.
5. Claude reads the tool list and calls tools with the permissions of the connected account.

## Tool permissions

Claude groups Notifly tools as **Read-only tools** and **Write/delete tools**. Check the discovered tool list when you connect. The available tools can change as the service is updated.

| Permission group | Examples | Effect |
| - | - | - |
| Read-only tools | Lookup and search tools | Read project, campaign, user, and documentation data. |
| Write/delete tools | Draft, segment, and CSV write tools | Create or replace campaign and inactive user journey drafts, change saved segments, or upload CSV files. Segment tools include deletion. |

Set the policy for each tool group in Claude, such as **Ask for approval**. If your organization handles sensitive projects, keep write tools subject to approval.

> [!WARNING]
>
> Claude's **Write/delete tools** label covers different effects. Notifly's campaign tools create or replace drafts only, and its user journey tools only create or replace inactive drafts that can be edited. These tools do not send messages, activate resources, or delete campaigns or user journeys. Other MCP tools can change or delete saved segments and upload CSV files. Review the specific tool and its input before approving a write.

## Capabilities

| Category | Example tools | Description |
| - | - | - |
| Products and projects | `list_products` and related tools | Find products and projects within your account permissions. |
| Campaigns | Lookup and statistics tools | Read campaign lists, details, statistics, and variants. |
| Campaign drafts | `create_campaign` and related tools | Create or replace campaign drafts that you can open in the Notifly console. |
| User diagnostics | `identify_user` and related tools | Check a user's channel status, events, eligibility, and delivery records. |
| User journeys | Journey lookup tools | Read journey lists, details, performance, and user sessions. |
| User journey drafts | Journey draft tools | Create or replace inactive user journey drafts. |
| Documentation | Official documentation search tools | Search official documentation and read page contents. |

## Example prompts and responses

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

### Find projects and campaigns

```text theme={null}
Use the Notifly connector to find the projects I can access,
then show recent campaigns in the first project.
```

```text theme={null}
I found the following accessible projects.

- commerce-prod
- onboarding-demo

Recent campaigns in commerce-prod:

- June retention notification: active, app_push, scheduled
- Cart reminder: draft, app_push, event_based
```

### Diagnose a user's missing message

```text theme={null}
Check why user@example.com did not receive the Cart reminder campaign.
Separate actual query results from assumptions.
```

```text theme={null}
Actual query results:

1. User identity: Used `identify_user` to find the canonical Notifly user ID.
2. Channel status: App push notifications were disabled for this user.
3. Campaign eligibility: The user passed the segment conditions but failed the channel eligibility requirement.
4. Delivery records: No delivery record exists for this campaign and user.

Conclusion: The evidence points to an app push consent issue,
rather than a segment mismatch. Token status needs a separate check if it has not been queried.
```

### Create an inactive user journey draft

```text theme={null}
Create a user journey draft that waits 1 day after a sign-up event,
then sends an app push notification.
Do not activate it. Explain the structure of the draft you create.
```

```text theme={null}
I created an inactive user journey draft.

- Status: inactive draft
- entry: entry based on the sign-up event
- nodes:
  1. delay node: wait 1 day
  2. message node: app push message
- Activated or sent: no

Open the draft in the Notifly console.
Review the message and entry conditions before activating it.
```

## Disconnect and reconnect

* To disconnect, open the Notifly connector and select **Disconnect** in its connection controls. Earlier versions use **Customize > Connectors > Notifly > Disconnect**.
* To switch accounts, select **Disconnect**, then **Connect** again.
* If tools are missing or OAuth fails, remove the custom connector and add it again with the same URL.

## Troubleshooting

| Symptom | What to check |
| - | - |
| **Connect** is missing after **Add** | Check the name and remote MCP server URL. The URL is `https://api.notifly.tech/mcp`. If you already signed in during setup, check whether **Disconnect** is displayed. |
| OAuth client ID or secret appears to be required | Notifly supports dynamic client registration. Leave both fields blank, or select **Register automatically** if the OAuth client selector is shown. |
| The browser does not return to Claude after sign-in | Check whether the browser blocks pop-ups or redirects, then select **Connect** again. |
| Every tool call requires approval | This follows Claude's **Tool permissions** policy. If appropriate, adjust only the **Read-only tools** policy. |
| No projects are returned | Check the connected Notifly account's product and project permissions. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.