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
AI Context Flow
@rajan_batra3 Mostly from linkedin but some from reddit too. I am very active on linkedin and have been in the IT space for 10+ years so have a large personal network.
I did a poll that how many AI tools do you use per week, then reached out to the ones that said 3-5 per week.
Wow, I didn’t realize how much we need this until we saw it. Thank you@hira_siddiqui1 and congratulations!
We do find ourselves asking differentAI agents the same questions, wasting tokens trying to find the best prompt to use and have to explain ourselves over and over.
And we are still not using AI as a source of truth, thankfully, but having them cross reference and constructively criticize each other has been very productive. The manual copy-pasting and massaging our messaging really does take a lot of extra effort! We’re for sure going to be implementing this into our workflow.
Questions: What are your next steps for scaling? Beyond the Chrome extension, is there another platform or niche you think would be a good fit for your product?
AI Context Flow
@sb_wc_labs our bigger vision is to build an open context layer - a user-owned portable memory layer where users can take their memory with them wherever they go!
Next up is MCP servers and "Sign in with AI" SDK.
You can read about the bigger vision and our "why" in my post here
@hira_siddiqui1 The main reason I am always skeptical about integrations are that I'm not sure if my data is safe. How would you bridge this issue?
AI Context Flow
@devanshi_jhaveri we are integrating with Trusted Execution Environments and your data always stays end to end encrypted.
We also plan to open source our extension soon so everyone can audit there is nothing else happening there.
AI Context Flow
@ihatzis would love if you try it out and let me know if it helped you! :)
AI Context Flow
@ihatzis some early users are reclaiming 5+ hours a week!
This is a sweet product Hira! One question: do you see AI-natuve browsers as strong competition, especially since this is the main thing they're also aiming to do?
AI Context Flow
@pamir_sevincel2 glad you asked this! We see them as validation more than competition.
Different moats: They need users to switch browsers (huge friction). We work where people already are - Chrome, any browser, any AI tool.
We're platform-agnostic by design. Users already jump between ChatGPT, Claude, Perplexity daily. AI browsers you into one browser's AI. We give you portable memory across all of them.
Chrome has 69% share, changing browser behavior is incredibly hard. But everyone's already using multiple AI tools - that fragmentation is exactly what makes a universal memory layer valuable. Plus, if AI-native browsers take off, they'll still need memory/context infrastructure. We could easily be a partner or acquisition target for them.
@samin_asef It seems there are different buckets you can create for different memory projects
I have used this recently. I am an engineer and a doctoral student, yet a researcher. In this field as a researcher, I need to use different AI tools for different types of work. So, it is very hectic to explain all the work again and again to different AI by typing the same prompts, which is time-consuming, and you might miss some details while typing. For this, I used AI Context flow in my research. It provided a memory layer by which I can use different AI tools at the same time by giving a prompt to only one. The results were good.
It has optimised my research work. It considers all previous prompts given in AI chats and then tries to give an optimised reply. Since we need different responses from different AI chat sources, we need to explain all the previous history and data and write prompts again and again, but by using this extension, the work has been made easier. It is now easy to get an response altogether from all AI chat sources ^-^
A good initiation by great minds, but it can be improved more in terms of giving optimised responses so that it provides short, concise, yet meaningful responses.
AI Context Flow
@sehrish_shoukat exactly, different AI tools are good at different tasks. Knowledge workers and researchers know this and hence 60% of them are switching between 3-5 different AI tools per week, wasting over 5 hours per week.
We intend to give this lost time back to the people!