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
Great Idea! Had this issue multiple times over the past week alone. Congratulations on the launch 👏
AI Context Flow
@underdogsteve would love to know what you think when you use it :)
Klariqo AI Voice Assistants
This can save so much time. Having to re-explain the same thing over and over again is tedious af. Love this!
AI Context Flow
@ansh_deb early users are saying it's saving them 5+ hours a week! Very excited how this will evolve when we deploy our MCP servers (soon)
"like it's the first day of school"
I like this line. I wonder if you came up with it originally or used AI! Nonetheless, great concept
@hira_siddiqui1 @justin2025 @yuze_li @mujtabaidrees94 Really like this idea for folks trying to replicate but clearly running into the issues of .. why don't you remember this from our last conversation Mr. GPT.
AI Context Flow
@dzaitzow thank you! would love to know how you feel about the extension after a few days of using it!
I had the pleasure to follow the progress of this powerful tool and I could not recommend more. Strong founders also!
AI Context Flow
@marco_marchesi thank you!
Have been using this product in it's beta phase, it's a super productive tool that can help you get you solutions through AI LLMs in the quickest way possible, prompting is made easy through this.
AI Context Flow
@naveed_siddiqui thank you for being our beta user! We would love to hear how you would want the product to be improved further!
I've been using the AI Context Tool for a while now and it is capital A Awesome - and why is it awesome, because Hira and the team built it to solve a problem that both themselves and their peers were facing. It is simple and, just works. Great product from a really great team, let the unbundling begin.
AI Context Flow
@wheelsfelloff thank you so much Mark! Your mentorship has been instrumental throughout the journey!