Evernote MCP Server

A secure MCP server for Evernote integration with OAuth 1.0a authentication and automatic token expiration handling

Local serverstdio

What is the Evernote MCP server?

Most developer tooling work still happens through a UI a human drives. Evernote MCP server moves it into the conversation instead. A secure MCP server for Evernote integration with OAuth 1.0a authentication and automatic token expiration handling.

The short version

A local MCP server that connects Claude Desktop (or any MCP-compatible LLM) with your Evernote account, allowing contextual queries and searches over your notes using natural language.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Dockerfile — Multi-stage build process: - Builder stage: Uses cgr.dev/chainguard/node:latest-dev with git and openssl for setup - Production stage: Uses

What it needs from you

Configuration is passed through the environment: EVERNOTE_CONSUMER_KEY, EVERNOTE_CONSUMER_SECRET, NODE_TLS_REJECT_UNAUTHORIZED, DEV_MODE, GITHUB_REPO_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

The server ships on npm as node, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Evernote's toolset — Dockerfile — is a fair guide to whether it matches your workflow. It is maintained by brentmid; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
DockerfileMulti-stage build process: - **Builder stage**: Uses cgr.dev/chainguard/node:latest-dev with git and openssl for setup - **Production stage**: Uses minimal cgr.dev/chainguard/node:latest for runtime - **GitHub integratio

How to install the Evernote MCP server

{
  "mcpServers": {
    "evernote": {
      "command": "npx",
      "args": ["-y", "node"],
      "env": {
        "EVERNOTE_CONSUMER_KEY": "your-value",
        "EVERNOTE_CONSUMER_SECRET": "your-value",
        "NODE_TLS_REJECT_UNAUTHORIZED": "your-value",
        "DEV_MODE": "your-value",
        "GITHUB_REPO_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
EVERNOTE_CONSUMER_KEYCredential the server authenticates with.Yes
EVERNOTE_CONSUMER_SECRETCredential the server authenticates with.Yes
NODE_TLS_REJECT_UNAUTHORIZEDConfiguration value read at startup.Optional
DEV_MODEConfiguration value read at startup.Optional
GITHUB_REPO_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Evernote to Dockerfile.

Frequently asked questions

It connects Evernote to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Dockerfile) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Evernote directly.