Every founder builds for an imagined user. The real ones never quite match.

Our vision has been the same from day one: one knowledge base that works across all your AI tools.

And to achieve that, we launched our MCP Server in February. It connected to Claude Desktop, Claude Code, LM Studio, and most major AI agents. As far as we were concerned, the MCP chapter was closed.

Then we launched on AppSumo.

Within days, users kept asking for one thing: "𝘋𝘰𝘦𝘴 𝘵𝘩𝘪𝘴 𝘸𝘰𝘳𝘬 𝘸𝘪𝘵𝘩 𝘖𝘱𝘦𝘯𝘊𝘭𝘢𝘸?"

Then came the questions about headless agents. CI scripts. n8n workflows. Users had intricate setups. They wanted a memory store for their OpenClaw agents, which they could also plug into Claude, which they could also call from a workflow runner. One memory, three completely different environments.

That's when we realized our MCP Server had a problem: it only supported OAuth. *facepalm*

(Getting a bit technical here, bear with me)
OAuth assumes there's a user sitting at a UI who can click "sign in" in a browser window. That's fine for Claude Desktop. It falls apart the moment you're running a headless agent on a server, or chaining four tools together in an automated workflow. Nobody is there to click anything!

So the team got to work. A few days later, we shipped Personal Access Tokens (PATs) for the MCP Server.

And that's how we ended up being the 𝗼𝗻𝗹𝘆 𝗺𝗲𝗺𝗼𝗿𝘆 𝗹𝗮𝘆𝗲𝗿 that works in three places at once:

→ In your browser, as a sidebar
→ Inside your chat agents, as an extension or MCP server
→ In your programmatic workflows, as an MCP with PAT-based authentication

New setup guides for everything are at docs.plurality.network.

Maybe a weekend project: give your OpenClaw or n8n agents a memory. Make them less forgetful, more intelligent, and a lot more useful.

If you are already running such setups, we have a lifetime deal going on for AI Context Flow: https://appsumo.8odi.net/m4n0da