- Home
- MCP servers
- MCP Evernote Server
MCP Evernote Server
- javascript
3
GitHub Stars
javascript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"verygoodplugins-mcp-evernote": {
"command": "npx",
"args": [
"-y",
"-p",
"@verygoodplugins/mcp-evernote",
"mcp-evernote"
],
"env": {
"OAUTH_CALLBACK_PORT": "3000",
"EVERNOTE_ENVIRONMENT": "production",
"EVERNOTE_CONSUMER_KEY": "your-consumer-key",
"EVERNOTE_CONSUMER_SECRET": "your-consumer-secret"
}
}
}
}You can run and configure an MCP server that integrates Evernote, enabling note creation, retrieval, organization, and search from Claude Code or Claude Desktop. This guide provides practical steps to install, authenticate, and use the Evernote MCP server in common workflows.
How to use
You will interact with the Evernote MCP server through an MCP client by starting the server command, authenticating with Evernote, and then issuing endpoints like create_note, search_notes, get_note, update_note, delete_note, and various notebook/tag operations. When your environment is set up, you can automate common tasks, such as capturing meeting notes to a specific notebook, organizing notes with tags, and performing full-text searches with Evernote query syntax. If you enable polling or webhooks, you will receive notifications about note changes to a configured endpoint.
How to install
Prerequisites: you need Node.js and npm installed on your system. You will run commands either without a global installation or with a global installation, depending on your preference. You will authenticate with Evernote using OAuth, either interactively or automatically via your MCP client.
Step by step you can install and run the Evernote MCP server using NPX to avoid global installation for quick start.
Configuration and usage notes
Key configuration involves Evernote API credentials and environment settings. You can provide credentials interactively or via environment variables. Once authenticated, you configure your MCP client to point at the Evernote MCP server using the recommended start command shown below.
Configuration details
OAuth credentials and environment setup are required for Evernote access. You will provide or store keys and environment settings to enable tokens and API access. The server can store tokens locally and refresh them automatically.
Security considerations
Store OAuth tokens securely on your machine (they are kept in a local file). Do not commit tokens to version control. Use environment variables for automation and consider separate production and sandbox environments. Tokens have a defined expiry and will require re-authentication when needed.
Troubleshooting
If you encounter authentication or connectivity issues, re-authenticate with the Evernote integration, verify environment settings, and check that the correct Evernote environment (production or sandbox) is configured. If you see “Not connected” errors, try reconnecting, validating health, and re-authenticating if necessary.
Development and testing
For contributing, you can clone the project, install dependencies, run development commands, and execute tests and linting as described in the development workflow. Use the provided tooling to build and test the MCP server locally.
Note operations
The server supports creating, reading, updating, and deleting notes, along with Markdown to ENML conversion and back, enabling safe round-tripping of content and attachments.
Notebook and tag operations
You can list notebooks, create new notebooks, organize with stacks, and manage tags with hierarchical support. These operations help structure your Evernote data from the MCP server.
Account and health checks
Use health and diagnostic endpoints to verify server status, authentication state, and configuration details. You can also revoke authentication when needed.
Polling and webhooks
Configure auto-polling to detect changes in Evernote and send webhook notifications to your endpoint. You can start, stop, or trigger immediate polls and inspect current polling status.
Claude Automation Hub and memory service
This MCP server is designed to integrate with Claude Automation Hub for workflow automation and can synchronize selected notes with a memory service to support long-term retention.
Markdown support and content handling
Markdown content is converted to ENML with support for GFM features like task lists and images. Attachments are uploaded as Evernote resources and generated references are preserved for safe round-tripping.
Search syntax
Use Evernote's advanced search operators to locate notes by title, notebook, tag, date, and content. The MCP server passes your queries to Evernote and returns matching results in a structured format.
Memory service integration
To enable synchronization with a memory service, set the memory service URL in your environment and use the provided sync tools to persist important notes to memory.
Connection resilience
The server includes automatic recovery features such as auto-retry, proactive token validation, graceful degradation, and clear error messaging to help you maintain uptime even during transient issues.
Code snippets and commands
{
"mcpServers": {
"evernote": {
"command": "npx",
"args": ["-y", "-p", "@verygoodplugins/mcp-evernote", "mcp-evernote"],
"env": {
"EVERNOTE_CONSUMER_KEY": "your-consumer-key",
"EVERNOTE_CONSUMER_SECRET": "your-consumer-secret",
"EVERNOTE_ENVIRONMENT": "production"
}
}
}
}
Examples and usage notes
You can authenticate with Claude Desktop or Claude Code, add the Evernote MCP server to your Claude configuration, and begin creating notes programmatically or via Claude prompts. Use the start command pattern shown to initialize the MCP server in your environment.
Note end of life and roadmap
The roadmap includes enhancements to tag management, ENML–Markdown conversion improvements, real-time sync hooks, and additional export/import capabilities. You can track progress and plan integrations accordingly.
Appendix: available tools and actions
The MCP server exposes a comprehensive set of actions for Evernote management, including creating, reading, updating, deleting notes; listing, creating, and organizing notebooks; listing and creating tags; retrieving user info; health checks; and polling control. Refer to the action names in your client to perform these tasks.
Available tools
evernote_create_note
Create a new note in Evernote with a title and content, optionally specifying notebook and tags.
evernote_search_notes
Search for notes using Evernote's syntax, with optional notebook and max results.
evernote_get_note
Retrieve a note by GUID, with optional content inclusion, returning Markdown with resource references.
evernote_update_note
Update an existing note by GUID with a new title, content, or tags.
evernote_delete_note
Delete a note by GUID.
evernote_list_notebooks
List all notebooks in the Evernote account.
evernote_create_notebook
Create a new notebook, with an optional stack for organization.
evernote_list_tags
List all tags in the Evernote account.
evernote_create_tag
Create a new tag, with optional parent tag for hierarchy.
evernote_get_user_info
Retrieve current user information and quota usage.
evernote_revoke_auth
Revoke the stored authentication token.
evernote_health_check
Check the health and status of the MCP server and authentication.
evernote_reconnect
Force reconnection to Evernote to recover from connection issues.
evernote_start_polling
Start polling for Evernote changes and send notifications to the webhook URL.
evernote_stop_polling
Stop the polling process.
evernote_poll_now
Immediately check for changes and return detected updates.
evernote_polling_status
Return the current polling configuration and status.