NudgeBell

app.nudgebellPublished by nudgebell.appOfficial publisherv1.0.1Updated Oct 24, 2026

Reminders your agent creates: email, WhatsApp, SMS or call, in steps you set. Stops on acknowledge.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

NudgeBell is a remote MCP server that lets an assistant create multi-step reminders delivered by email, WhatsApp, SMS or call, stopping when acknowledged.

What you can do
Create reminders that an assistant schedules for a person or contact, delivered by email, WhatsApp, SMS or call, in steps you set. Reminders stop once the recipient acknowledges them. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant should follow up with people over time through real messaging channels, such as nudging someone until they confirm they have seen or done something.
Requirements
A remote endpoint at nudgebell.app over streamable HTTP. A NudgeBell API key (nb_live_...) from the account settings page, sent in the X-API-Key header. No packages or environment variables are declared.
Before you install
Requires a live API key sent as the X-API-Key header; keep it secret. Reminders send real email, WhatsApp, SMS or call messages to recipients, which may incur costs and cannot be unsent. Review who is contacted and how often before enabling.

Installation

In SourceWeft

  1. Open NudgeBell in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.nudgebell%2Freminders/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nudgebell": {
      "type": "http",
      "url": "https://nudgebell.app/api/v1/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 17, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.