Jotter

fyi.jotterPublished by jotter.fyiOfficial publisherv1.0.3Updated Oct 24, 2026

Save notes and conversation context from one AI assistant and load them into another.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Lets an assistant save notes and conversation context so they can be loaded into a different AI assistant.

What you can do
Jotter is a remote MCP endpoint that lets an assistant save notes and conversation context, and later load that saved material into another AI assistant. The manifest does not list individual tools, so the exact operations are not documented here. Its stated purpose is moving context between assistants rather than working with files or databases directly.
When to use it
Worth considering when you regularly switch between AI assistants and want notes or conversation context to carry over instead of being retyped. Less useful if you only ever use one assistant or do not need to preserve context across sessions.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the Jotter endpoint. Authentication is required via OAuth, so you need a Jotter account and a client that can complete the OAuth flow. No environment variables or headers are declared.
Before you install
Saved notes and conversation context are sent to a third-party service and stored there, so avoid saving sensitive or confidential material. Access is tied to an OAuth sign-in, so review which account you authorize and what data the service retains.

Installation

In SourceWeft

  1. Open Jotter 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/fyi.jotter%2Fjot/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": {
    "jotter": {
      "type": "http",
      "url": "https://jotter.fyi/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

2
  1. v1.0.3LatestSep 19, 2026
  2. v1.0.2Sep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.