Your people and your agents produce context all day. MeshTale organizes it, then decides who gets which part back.
Producing raw context
One governed memory
Pulling the right context
Free tier, no card required. Source-available under FSL-1.1-MIT.
What that looks like
No new window, no copy-paste, no re-explaining the account. Your agent asks, MeshTale returns what that client’s workspace holds — and shows its working.
No hours saved, no percentage lifts, no months to payback. We have no customers yet, so we have no business claiming any of that. These are properties of the product, measured or counted.
tools to register
Most setups spend tens of thousands of tokens describing their tools before the model does any work.
tokens sent per call
Measured, not estimated — both tool definitions serialised and counted. Reproducible.
permission checks per answer
Stacked authorization filters, applied to every query on every route.
sources you can connect
Real implementations against real vendor APIs, not a roadmap slide.
retrieval recall
On a public memory benchmark, 311 questions. Measures whether the right material was found — not end-to-end answer accuracy.
model providers, your keys
Bring your own OpenAI, Anthropic or Google key and run your memory against whichever you prefer.
How it stacks up
Your people produce the context — calls, briefs, specs, contracts. Your agents consume it. Both go through the same workspace, sorted into collections, under the same permission checks. One workspace per client, and nothing crosses between them.
Same organization · no path between the two workspaces
Organization
Your company. Holds every workspace and the people in them.
Workspace
Usually one per client or team. This is where the boundary lives.
Collection
A folder inside a workspace, with its own sensitivity default.
Memory
A single piece of recallable context, carrying its own audience tags.
01 · Separate by default
Tenancy runs through the data model rather than sitting on top of it. Audience tags travel with the content, so the boundary is a property of the memory itself — not a filter someone remembered to apply.
Renewal pricing agreed at $4,200/mo, effective from the March invoice.
02 · Answerable
Every recall is logged — which agent, which workspace, how much came back, and when. Not a summary written afterwards, but the thing itself.
every recall · who, what, when, which workspace
03 · Cheap to live with
A typical setup spends tens of thousands of tokens describing its tools before the model does any work. Ours registers two, and every answer comes back with its sources attached.
What did we agree with Northwind about the renewal?
Renewal was agreed at $4,200 a month, starting from the March invoice, with the extra seats folded in rather than billed separately.
Northwind workspace only · nothing from another client
The product
Filter memories by who may see them, how sensitive they are, and where they came from. Retention and policies sit in the same navigation, not in a slide about next quarter.
Agreed pricing floor for renewal
slack #northwind-billing · 12 Jun
Who reaches it
The refusals are not a filter applied to the answer. Those two never had this memory in scope to begin with, and the attempt is recorded either way.
How it works
Point MeshTale at the places your work already lives. It parses, chunks and indexes.
Decide who and what can see each piece. Audience tags travel with the content.
Connect Cursor, Claude Code, or any MCP client. Ask; get cited answers scoped to what that agent is allowed to see.
#northwind-billing✓ Connected. 2 tools registered. recall · recall_context_bundle↳ 3 memories · Northwind workspace only slack #northwind-billing · 12 Jun drive / Northwind MSA v3.docx✓ Cited. Logged. Nothing outside this client.Underneath
Storing text is the easy half. These are the decisions that determine whether what comes back is any good — and whether you can live with it once more than one person is involved.
Choose the folders and channels worth bringing in rather than hoovering up an entire account. Fewer irrelevant results, and a smaller surface to govern.
Enforced today on Agency and Scale
Content arrives tagged by how much it should be trusted, and that tag feeds the ranking — so an approved contract outranks a passing remark in a thread. Your organization sets the rules that assign those tags.
Ranked by trust, not just by similarity
Trust tags feed the ranking score
Personal connections stay yours — your mail, your notes, visible only to you. Shared connections belong to the workspace. Both live in the same product without mixing.
Personal
Your mail
Your notes
visible to you
Shared
Client drive
Team channels
visible to the workspace
Two separate connection lanes
Exact-match and meaning-based search run separately, then get combined by rank rather than by raw score — which stops one drowning out the other when they disagree.
Exact
Meaning
Merged
MSA v3 · Renewal notes · Billing thread
Reciprocal rank fusion
Newer versions of a source supersede older ones, and recency feeds the ranking. A full decision history — what changed, when, and why — is not built yet, so we are not showing you one.
Ways in
The same governed memory behind every route — with the same permission checks on each one.
The open standard your AI clients already speak. Two tools to register, one sentence each — so connecting costs almost nothing before you have asked anything.
claude mcp add meshtale…and anything else that speaks the protocol
The honest bit
Yes. And it’s easier than people admit — free, well-documented projects stand this up in well under an hour, with a community shipping importers for every tool you use.
If you’re one person organising your own thinking, that is genuinely the right answer, and we’d rather you spent nothing. We are not going to tell you self-hosting is hard, because it isn’t.
Then you take on a second client.
A personal memory store has one owner by design. The moment you’re holding two people’s work, four questions arrive — and none of them are weekend problems.
Isolation, permissions and an audit trail aren’t features you bolt on later. They’re the reason this exists.
All 26 of them, on every plan. What changes higher up is how precisely you can choose which folders and channels come in.
MeshTale connects to 26 sources: Slack, Microsoft Teams, Discord, Gmail, Outlook, Notion, Confluence, Google Drive, Dropbox, SharePoint / OneDrive, Obsidian, Microsoft OneNote, Amazon S3, Jira, Linear, Asana, ClickUp, Trello, Monday.com, GitHub, Salesforce, HubSpot, Zendesk, Granola, Fathom, Zoom.
Writing
Without leaking one client’s context into another’s prompt.
Free tier, no card required. Source-available under FSL-1.1-MIT.
