npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@maximem/synap-mastra

v0.1.1

Published

Synap memory integration for the Mastra ADK (Agent Development Kit)

Readme

@maximem/synap-mastra

Synap memory integration for the Mastra ADK (Agent Development Kit).

Drop Synap directly into new Agent({ memory, tools }) — two plug points, composable or used independently.

Install

npm install @maximem/synap-mastra @mastra/core zod

1. SynapMemory — Agent memory

SynapMemory extends MastraMemory so you can pass it straight to new Agent({ memory }):

import { Agent } from "@mastra/core/agent";
import { SynapMemory } from "@maximem/synap-mastra";

const agent = new Agent({
  name: "support-agent",
  instructions: "You are a helpful assistant.",
  model: /* your model */,
  memory: new SynapMemory({ sdk, userId: "alice", customerId: "acme" }),
});

Synap-backed methods:

  • recall({ threadId }) → loads prior turns from sdk.conversation.context.get_context_for_prompt
  • saveMessages({ messages }) → persists each turn via sdk.conversation.record_message
  • getSystemMessage({ threadId }) → fetches Synap context and returns it as a system-message preamble the Agent injects before the turn

Thread metadata is kept in-process via a Map — adequate for single-process apps; multi-process thread persistence is a v0.2 concern.

Working memory, message deletion, and multi-process thread sharing are not supported in v0.1. Calls log once and no-op or return null honestly.

2. synapSearchTool / synapStoreTool — Agent tools

Register them in the Agent's tools map so the model can read/write memory explicitly via tool calls:

import { synapSearchTool, synapStoreTool } from "@maximem/synap-mastra";

const agent = new Agent({
  name: "support-agent",
  instructions: "...",
  model: /* your model */,
  tools: {
    synapSearch: synapSearchTool({ sdk, userId: "alice" }),
    synapStore: synapStoreTool({ sdk, userId: "alice" }),
  },
});

Use one or both surfaces; they compose.

Error policy

  • SynapMemory.recall / getSystemMessage — read-side, degrade gracefully (empty recall / null system message) with an ERROR log on failure.
  • SynapMemory.saveMessages — write-side, throws on SDK failure (silent drops would hide ingestion outages).
  • synapSearchTool — returns { available: false } on SDK failure; the agent loop keeps going.
  • synapStoreTool — throws on SDK failure so the tool call surfaces as an error to the agent.