Add NoteMCP — hosted notes and long-term memory MCP server for Claude and ChatGPT - #3842
Open
waelmansourx wants to merge 1 commit into
Open
Add NoteMCP — hosted notes and long-term memory MCP server for Claude and ChatGPT#3842waelmansourx wants to merge 1 commit into
waelmansourx wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds NoteMCP — a hosted MCP server that gives Claude, ChatGPT and Cursor
long-term memory over your own notes.
You capture by text, voice, or your phone's share sheet; the agent then searches,
reads, writes and tags those notes in any later conversation.
https://notemcp.com/mcp(Streamable HTTP)com.notemcp/notemcp(domain-verified namespace)Two design choices that matter for agent use: lists never return note bodies,
only a label and a short preview, and embedded photos are redacted to
![photo]even in a full note — so a large collection cannot flood the context window.
Fetching an image is an explicit, bounded call.
I followed the structure proposed in #3275 (a
Featured MCP Serverssectionbefore
Community) so the two are compatible whichever lands first. Happy toreformat, move it, or drop it into a different section if you'd prefer it
elsewhere.