Dijin Memory

co.dijinPublished by dijin.coOfficial publisherv1.0.0Updated Oct 24, 2026

Dijin is a Memory Layer: recall notes, decisions, and evidence-backed answers across every AI.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Dijin Memory is a remote memory layer that lets an assistant recall notes, decisions, and evidence-backed answers across different AI tools.

What you can do
  • Recall stored notes and decisions from a shared memory layer
  • Retrieve evidence-backed answers that other AI tools can reuse
  • Keep context consistent across multiple AI assistants through one hosted endpoint
When to use it
Worth adding when you want an assistant to remember notes and past decisions across several AI tools instead of starting from scratch in each one.
Requirements
A remote MCP endpoint at mcp.dijin.co over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
The server stores notes and decisions in a third-party hosted service, so anything recalled or saved leaves your machine. OAuth grants access to your Dijin account; review what data the service retains before connecting.

Installation

In SourceWeft

  1. Open Dijin Memory 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/co.dijin%2Fmemory/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": {
    "dijin-memory": {
      "type": "http",
      "url": "https://mcp.dijin.co/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.