Add GoodMem to Memory & State

[amin3141]

Adds GoodMem to Memory & State as an agent-enabling service. Agents can store findings and task history in persistent memory spaces, retrieve relevant context in later sessions, and share selected spaces between authorized workloads.

The entry includes claim-level official sources, deployment and license information, and the following interface boundaries:

• GoodMem's built-in Streamable HTTP MCP endpoint runs at the instance's /mcp path and currently provides read-only retrieval and diagnostics in early access.
• REST, SDKs, framework integrations, and the separate stdio MCP adapter provide ingestion and management operations.
• Humans provision workload service identities, grants, and scoped keys.
• GoodMem also supports conventional RAG. The core is proprietary under the Free Binary License; the freemium pricing classification reflects ongoing free self-hosting alongside paid GoodMem Cloud.

Validation

• npm test: 71 passed on Node 24.
• npm run validate:content -- --require-submitters: passed for 16 categories, 40 tools, and 1 redirect/retirement.
• Generated the GoodMem submitter record and media metadata with the repository scripts.
• Checked the linked official documentation, pricing, license, and integration repositories.
• git diff --check: passed.

Disclosure: I am Amin Ahmad, founder of PAIR Systems, the company behind GoodMem.

[amin3141]

Hi @bradvin, this PR's CI is awaiting maintainer approval. Could you enable it when you have a chance? Happy to address any feedback. Thanks!

[bradvin]

hey @amin3141 sorry I was not getting github alerts for new PR's on this repo. I have dispatched my agent to review all PR's and will access against the policy.

[amin3141]

Okay, sounds good. I appreciate the reply.

…

On Tue, Sep 22, 2026 at 10:02 AM Brad Vincent ***@***.***> wrote: *bradvin* left a comment (bradvin/agentfirst.directory#67) <#67 (comment)> hey @amin3141 <https://github.com/amin3141> sorry I was not getting github alerts for new PR's on this repo. I have dispatched my agent to review all PR's and will access against the policy. — Reply to this email directly, view it on GitHub <#67?email_source=notifications&email_token=AEMF7BXW2DU7JG3PQRJEFFL5QKWBXA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNZYGA3DCOBYGAZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5780618803>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEMF7BRTBI6RW5D7CM6TSC35QKWBXAVCNFSNUABGKJSXA33TNF2G64TZHMYTCOJTGQ4TKMZVGE5US43TOVSTWNJUGU3TKMZVGMZTFILWAI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[foo-bender]

Outcome: meets-policy

The listing passes the inclusion test. GoodMem is agent-enabling: agents and authorized workloads can create persistent memory spaces, store and update findings, retrieve semantic context in later sessions, and share selected spaces under service identities, grants, and key ceilings. The product supplies persistence, memory operations, access control, and agent-framework tools—not just an MCP badge over retrieval. Memory & State fits the documented cross-session task/workflow-memory outcome, and no duplicate was found on current main.

First-party evidence checked: GoodMem's integrations, native MCP, service-identity, and key-ceiling documentation; the official Claude Code plugin; https://goodmem.ai/pricing; and https://goodmem.ai/license. These establish that native HTTP MCP is early-access and read-only, write/manage operations use REST/SDK/framework tools or the separate stdio adapter, self-hosting is free under a proprietary binary license, and managed Cloud starts at $15/month after a 14-day trial. The submitted first-party URLs and image returned HTTP 200.

Checks actually run on this exact head in an isolated tree with Node 24.8.0: npm run validate:content passed; npm test passed. Current GitHub enrich check is successful.

Uncertainty: this was documentation review only; the listing correctly does not claim automatic fact extraction, conflict resolution, or forgetting, and the proprietary server core was not independently tested.

@bradvin This meets the current policy; the inclusion decision is yours.

Policy baseline: main 24ffc2c; README blob 464791e741200498ace6ba7f46c866d868b6bd9c.

[foo-bender]

Outcome: meets-policy

Policy assessment

GoodMem passes as agent-enabling memory infrastructure. Its documentation supports durable memory spaces, storage and semantic retrieval, optional reranking, scoped service identities/grants/key ceilings, and agent access through REST, SDKs, framework integrations, and two distinct MCP surfaces. The listing accurately discloses that native HTTP MCP is early-access/read-only, humans provision identities, the server core is proprietary, self-hosting has infrastructure/model costs, and cloud trial access is limited. Memory & State fits and no duplicate was found. @bradvin for the inclusion decision.

Evidence checked

Validated all seven first-party sources: https://docs.goodmem.ai/docs/integrations/, https://docs.goodmem.ai/docs/reference/mcp/, https://docs.goodmem.ai/docs/how-to/access-control/service-identities/, https://docs.goodmem.ai/docs/concepts/api-keys-and-ceilings/, https://github.com/PAIR-Systems-Inc/goodmem-claude-code-plugin, https://goodmem.ai/pricing, and https://goodmem.ai/license. Together they support memory operations, MCP boundaries, workload identity/access controls, plugin operations, freemium deployment, and the proprietary free-binary licence.

Checks run

• Reviewed the body, complete diff, listing, category, duplicates, current head/checks, pricing/licence, limitations, and each submitted evidence item. GitHub enrich is successful.
• Exact final head merged with current main af5b0fc05df21cf7cff658bd64be4d01ae2b5648 in an isolated worktree, Node 24.19.0: npm run validate:content passed; npm test passed 84/84.

Reviewer-owned SEO metadata
Tool path: tools/goodmem.md

• agentSummary — written: "GoodMem gives agent builders persistent memory spaces for storing and semantically retrieving task history, research, and shared context across sessions. It supports scoped service identities and API keys for unattended workloads, plus REST, SDK, framework, and MCP access. The native HTTP MCP surface is early access and retrieval-only; ingestion uses other interfaces." Grounded in the integrations, MCP, and access-control documentation.
• seoTitle — written: "GoodMem: Persistent Memory and Retrieval for AI Agents". It states the validated agent use.
• seoDescription — written: "Explore GoodMem's persistent memory spaces, semantic retrieval, scoped workload access, and REST, SDK, framework, and MCP interfaces for agent workflows." Grounded across the seven validated sources.

Reviewer commit: d4e7a51d2598dfa1c23bc94efbf280e17210552e — amin3141@d4e7a51. The existing description was preserved byte-for-byte.