Please Remind

io.github.pozymasikaPublished by GitHub account pozymasikav1.0.1Updated Oct 24, 2026

Connects to PleaseRemind.com to allow read and write access to all your reminders.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Connects an assistant to PleaseRemind.com so it can read and write the user's reminders.

What you can do
This remote server links an assistant to a PleaseRemind.com account and gives it read and write access to all of that account's reminders. The registry description does not list individual tools, so the exact operations are not documented here. Access is authenticated with a bearer token.
When to use it
Useful when someone keeps their reminders on PleaseRemind.com and wants an assistant to view or update them without switching apps.
Requirements
A remote MCP endpoint at pleaseremind.com reached over streamable HTTP. A PleaseRemind.com account and a bearer token sent in the Authorization header are required.
Before you install
The server has read and write access to all reminders in the account, so an assistant could change or remove existing entries. The bearer token in the Authorization header is a credential; keep it private and revoke it if exposed. Reminder content is shared with the remote service.

Installation

In SourceWeft

  1. Open Please Remind in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.pozymasika%2Fplease-remind/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": {
    "please-remind": {
      "type": "http",
      "url": "https://pleaseremind.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

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 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.