Summary

Read-only Evernote access that never leaves your machine.

OAuth happens directly between you and Evernote, tokens sit in a local .env file, and note content goes nowhere except Evernote and your client. The first run is the awkward part — you start the HTTPS server on its own, accept a self-signed certificate warning in the browser, and finish the OAuth flow before the MCP client will see any tools.

What it is

A Node server that connects Claude Desktop, or any MCP client, to your Evernote account over Evernote's OAuth 1.0a API. Access is read-only: it searches, inspects and reads notes, and does not create or edit them.

What you get

`createSearch` — search your notes with a natural-language query
`getSearch` — retrieve cached results from an earlier search
`getNote` — metadata for one specific note
`getNoteContent` — the full note body as text, HTML or ENML
Two ways to connect: local stdio, or an HTTPS JSON-RPC endpoint for containerised setups on Windows and Linux

Requirements

Node.js 18+ and an Evernote developer account. Set `EVERNOTE_CONSUMER_KEY` and `EVERNOTE_CONSUMER_SECRET` from a registered Evernote app whose callback URL is https://localhost:3443/oauth/callback. The server listens over HTTPS on port 3443 and needs a self-signed certificate, which the Docker Compose path generates for you. Access tokens are written back to .env after the first browser sign-in.

Setup effort

One command plus a key — npm install, then supply credentials