Read-only search, todo listing, and daily note access for a WhyNote account
A zero-dependency, read-only Model Context Protocol server for searching and reading the notes in one WhyNote account.
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:
{
"mcpServers": {
"note": {
"command": "npx",
"args": ["-y", "why-note-mcp"],
"env": {
"NOTE_URL": "https://note.example.com",
"NOTE_TOKEN": "<read-only-token>"
}
}
}
}
Claude Code:
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:
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.
search: search note lines by case-insensitive substringtodos: list incomplete or all todo itemsread_day: read one date's complete note and etagrecent_days: read existing note days around an anchor dateThe 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.
npm ci
npm test
npm 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.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y why-note-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-coooolinz-why-note": {
"command": "npx",
"args": [
"-y",
"why-note-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceWhyNote works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.