WhyNote

io.github.CoooolinzPublished by GitHub account Coooolinzv0.1.0Updated Oct 24, 2026

Read-only search, todo listing, and daily note access for a WhyNote account

VerifiedSTDIODesktop onlyProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

A local read-only MCP server that lets an assistant search and read notes and todos in one WhyNote account.

What you can do
Search note lines by case-insensitive substring match across the account's notes. List incomplete or all todo items. Read a single date's complete note together with its etag. Read existing note days around an anchor date.
When to use it
Useful when you want an assistant to look things up in your WhyNote journal — finding where something was mentioned, checking open todos, or pulling up a specific day's note — without giving it any ability to change the notes.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. Requires the NOTE_URL base URL of the WhyNote service and a read-only NOTE_TOKEN generated in WhyNote settings, both passed as environment variables. Network access to that WhyNote instance is required.
Before you install
The NOTE_TOKEN is a credential; the README warns that values written directly in a command may be retained in shell history, so editing the client configuration is safer. The token is sent as a Bearer credential to the configured NOTE_URL, so point it only at a trusted instance. The server exposes no write tools, and changing the account password revokes its read-only tokens.

Installation

In SourceWeft

  1. Open WhyNote in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

WhyNote MCP

A zero-dependency, read-only Model Context Protocol server for searching and reading the notes in one WhyNote account.

Install

Generate a read-only token in WhyNote settings, then configure your MCP client to run npx -y why-note-mcp with NOTE_URL and NOTE_TOKEN.

Generic project configuration:

json
{  "mcpServers": {    "note": {      "command": "npx",      "args": ["-y", "why-note-mcp"],      "env": {        "NOTE_URL": "https://note.example.com",        "NOTE_TOKEN": "<read-only-token>"      }    }  }}

Claude Code:

bash
claude mcp add --scope user note \  -e NOTE_URL=https://note.example.com \  -e NOTE_TOKEN='<read-only-token>' \  -- npx -y why-note-mcp

Codex CLI:

bash
codex mcp add note \  --env NOTE_URL=https://note.example.com \  --env NOTE_TOKEN='<read-only-token>' \  -- npx -y why-note-mcp

Values written directly in a command may be retained in shell history. Edit the client configuration instead if that is a concern.

Node.js 18 or newer is required.

Tools

  • search: search note lines by case-insensitive substring
  • todos: list incomplete or all todo items
  • read_day: read one date's complete note and etag
  • recent_days: read existing note days around an anchor date

Security

The server reads NOTE_URL and NOTE_TOKEN only from its environment. It sends the token only as a Bearer credential to the configured WhyNote URL. It never receives the account password and exposes no write tool.

Changing the WhyNote account password revokes its read-only tokens. Generate a new token in WhyNote settings when a token expires or is revoked.

Development

bash
npm cinpm testnpm run pack:check

The test suite uses a local fake HTTP service; it does not require a WhyNote account, network access, or third-party dependencies.

License

MIT

Source: README.md at commit a636838

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts