Cachejay

com.cachejayPublished by cachejay.comOfficial publisherv1.0.0Updated Oct 28, 2026

Memory for your AI: what you saw on screen, said in calls and worked on, searchable by agents.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Cachejay is a remote MCP memory service that lets an assistant search what you saw on screen, said in calls, and worked on.

What you can do
  • Search a personal memory store of screen activity, call conversations and work sessions.
  • Recall context from past activity so an assistant can answer questions about what you did or discussed.
  • Access is provided through a hosted remote endpoint rather than local tools; no individual tools are listed in the supplied material.
When to use it
Useful when you want an assistant to remember and look up your past screen activity, meetings and work, for example to recall what was discussed on a call or what you were working on earlier.
Requirements
A remote MCP endpoint at cachejay.com over streamable HTTP. OAuth authentication is required, so you need a Cachejay account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The service indexes what you see on screen and say in calls, which is sensitive personal data; consider what is captured and who can access it. OAuth grants the assistant access to your account's memory store. Review the provider's privacy and retention terms before connecting.

Installation

In SourceWeft

  1. Open Cachejay 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/com.cachejay%2Fcachejay/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": {
    "cachejay": {
      "type": "http",
      "url": "https://cachejay.com/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.0LatestOct 22, 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.