Jade Note

app.jadenotePublished by jadenote.appOfficial publisherv1.0.0Updated Oct 24, 2026

MCP-native notes and memory for ChatGPT, Claude, and other AI tools.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Gives an assistant MCP-native notes and memory that persist across ChatGPT, Claude, and other AI tools.

What you can do
Jade Note is a remote MCP server that provides notes and memory for AI assistants. According to its description it is MCP-native and works with ChatGPT, Claude, and other AI tools. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Worth considering when you want an assistant to keep notes or remember context across different AI tools and sessions. Less useful if you only need memory inside a single assistant or prefer notes stored locally. Check the provider's own documentation for the available tools before installing.
Requirements
A remote MCP endpoint at over streamable HTTP. No packages, environment variables, headers, or authentication are declared in the manifest. Network access to the provider is required.
Before you install
The manifest declares no authentication, environment variables, or headers, so it is unclear how notes are protected or who can read them. Notes and memory content sent to the remote endpoint are stored by a third party; avoid putting secrets or sensitive material in them.

Installation

In SourceWeft

  1. Open Jade Note in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.jadenote%2Fjade-note/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "jade-note": {
      "type": "http",
      "url": "https://api.jadenote.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.