Alternatives
Products that do what Waggle MCP does
External Memory Layer for AI agents
- 1
- 2
An OKF-backed Model Context Protocol (MCP) server delivering persistent long-term memory and SQLite FTS5 search for AI agents. - fellowgeek/mcp-memory
25d ago · github.com
- 3
- 4
- 5OS
Large Language Models (LLMs) are powerful, but they’re limited by fixed context windows and outdated knowledge. What if your AI could access live search, structured data extraction, OCR, and more—all through a standardized interface? We built the JigsawStack MCP Server, an open-source implementation of the Model Context Protocol (MCP) that lets any AI model call external tools effortlessly. Here’s what it unlocks: - Web Search & Scraping: Fetch live information and extract structured data from web pages. - OCR & Structured Data Extraction: Process images, receipts, invoices, and handwritten…
2025
- 6AM
This is an open‑source Model Context Protocol (MCP) server that gives any LLM a sense of the passage of time. Most MCP demos wire LLMs to external data stores. That’s useful, but MCP is also a chance to give models perception — extra senses beyond the prompt text. Six functions (`current_datetime`, `time_difference`, `timestamp_context`, etc.) give Claude/GPT real temporal awareness: It can spot pauses, reason about rhythms, and even label a chat’s “three‑act structure”. Runs locally in <60 s (Python) or via a hosted demo. If time works, what else could we surface? - Location /…
2025 · github.com
- 7
- 8
- 9
- 10MS
2025 · github.com
- 11
Open-source MCP server. #5 on LoCoMo. 100% local. MIT.
May 2026 · totalmemory.dev
- 12RA
Hey HN! A few months ago we shared mcp-agent (https://github.com/lastmile-ai/mcp-agent) [1][2], a lightweight framework that implements every agent pattern from Anthropic’s Building Effective Agents blog [3] and handles MCP server/client management seamlessly. Our core bet is that connecting LLMs to tools, resources, and external systems will soon be MCP-native by default. Today we're launching a significant update: Agents as MCP servers. Currently "agentic" behavior exists only on the MCP client side – clients like Claude or Cursor use MCP servers to solve tasks.…
2025 · github.com
- 13IM
Store memories, auto-extract entities and relationships, search semantically. MCP server + REST API + SDKs. Self-hostable, cloud option, MIT license.
May 2026 · agentrecall.cloud
- 14
- 15AU
2025 · github.com
- 16RM
We’ve open-sourced the Robot MCP Server, a tool that lets large language models (LLMs) talk directly to robots running ROS1 or ROS2. What it does - Connects any LLM to existing ROS robots via the Model Context Protocol (MCP) - Natural language → ROS topics, services, and actions (And the ability to read any of them back) - Works without changing robot source code Why it matters - Makes robots accessible from natural language interfaces - Opens the door to rapid prototyping of AI-robot applications - We are trying to create a common interface for safe AI ↔ robot communication This is too big…
Sep 2025 · github.com
- 17DS
Apr 2026 · github.com
- 18HM
We built a Rust MCP server, which wraps the excellent headless terminal (HT)[1] to makes it available for agentic coding tools. Most agentic coding tools struggle with blocking, interactive terminal tools (all the boilerplate generator, infra CLI tools etc). This is because many existing CLI dev tools are built for humans and require interactive input. We built this so agentic coding tools (Claude Code, Cursor, Memex, etc) can “see” and “interact” with terminals exactly like humans do. In our demo video [2], you'll see it operating vim/emacs just as a human would - selecting options,…
2025 · github.com
- 19
- 20
- 21
- 22BA
Tired of AI coding tools that forget everything between sessions? Every time I open a new chat with Claude or fire up Copilot, I'm back to square one explaining my codebase structure. So I built something to fix this. It's called In Memoria. Its an MCP server that gives AI tools persistent memory. Instead of starting fresh every conversation, the AI remembers your coding patterns, architectural decisions, and all the context you've built up. The setup is dead simple: `npx in-memoria server` then connect your AI tool. No accounts, no data leaves your machine. Under the hood it's TypeScript +…
2025 · github.com
- 23
Hi HN, for about a year now I've been experimenting with AI agents and building my own home ecosystem; from the start I set out with the idea of an agent that behaves like a member of the family, not as a personal agent, and this made me clash very early first with OpenClaw's builtin memory, then I tested dozens of memory plugins without ever finding one that fit my purpose, so like any good builder I made my own. First on OpenClaw, as a plugin, then the idea matured and since the beginning of this year the memory plugin has evolved into an agent agnostic MCP server. It has been running my…
Jul 2026 · github.com
- 24WA
2025 · web-agent-memory.github.io
Ranked by how close each launch is in meaning, then by votes. Refine with a description →