Works in Claude Code, Cursor, Codex and any MCP tool See how

Your team and their agents,one shared memory.Never the wrong client.

Your people and your agents produce context all day. MeshTale gives each of them the right context for the client they’re on, and never the wrong one’s.

Start freeTalk to us

Free tier, no card required.

NNorthwind Live
Example data
Memories in Northwind1,284+0 today
Recalls today312all cited
Refused3out of scope
Recalls by hourNorthwind only
Incoming memories people + AIwritten by your team and your agents
    Recall logevery recall recorded
      Northwind workspace · Ardent Co and Kestrel are separateIllustrative product animation

      Separate by default,and on the record when it isn't.

      Each client gets its own workspace. An agent bound to one workspace never has another client's memories in scope, and every attempt to reach them is logged.

      Who is askingExample data
      ClaudeClaude Codebound to Northwind
      PriyaArdent Co team
      CursorCursorbound to Kestrel
      RequestWaiting for a request
      Your organization3 workspaces
      NNorthwind
      Client comms
      Renewal terms agreed
      Kickoff decisions
      Contracts
      MSA v3
      AArdent Co
      Briefs
      Spring campaign brief
      Tone of voice notes
      Delivery
      Launch checklist
      KKestrel
      Support
      Escalation policy
      SOWs
      Phase 2 scope
      Data migration plan
      Same organization. No path between workspaces.
      Results appear here.
      Recall log

      The refusal is not a filter on the answer. The out-of-scope memory was never in that agent's reach, and the attempt is recorded either way.

      How a memory is held. Four layers, one wall that holds.

      Every memory sits in a collection, inside a workspace, inside your organization. A recall passes each layer on the way in, and the workspace wall is where the wrong client gets stopped.

      • Claude Code, bound to Northwind: recalled one memory from Contracts, cited in its answer.
      • Cursor, bound to Kestrel: asked for Northwind, refused at the workspace wall, logged.
      Example data

      A stack of four layers. The organization is the base. On it sit three walled workspaces: Northwind, Ardent Co and Kestrel. Inside Northwind are three collections: Client comms, Contracts and Delivery. Memories sit on top, each showing who created it: people such as Dana, Marco and Priya, or AI tools such as Claude Code, Codex and Cursor.

      Northwind renewal terms

      Northwind / Contracts

      by Marco · Granola call

      Account teamLegalapproved

      Cited in Claude Code's answer

      Stopped at Northwind
      refused · logged

      Cursor is bound to Kestrel. Northwind is out of its scope.

      ClaudeClaude Codebound to Northwind
      CursorCursorbound to Kestrel

      One memory,three ways to reach it.

      Plug it into the assistant you already use, call it from your own code, or sync coding-agent sessions from the command line. Same scoping and the same log, whichever door you use.

      ClaudeClaudeOpenAI (Codex)Gemini~/northwind-siteExample data

      Ask in the tool you're in,and get the right context for that client.

      No new window and no re-explaining the account. The agent asks, MeshTale answers from one workspace, cites the sources and logs the recall.

      NNorthwind Claude
      Example data
      You, in Claude
      • recall · workspace northwind
      • permission checks passed
      • 3 memories returned, cited
      Northwind only

      Recall logged

      Ask the built-in chat,and see where every answer came from.

      Tela, the chat inside MeshTale, searches the sources connected to a workspace and cites the memory behind each sentence. Point at a number to see it.

      Northwind / Chat
      Example data

      Northwind chat

      Ask Tela

      What do you want to know about Northwind?

      Tela answers from your connected sources with citations.

      Ask Tela about your workspace...

      Press Enter to send

      Tela searches Slack Google Drive Gmail G Notion Claude Code Codex Manage
      What did we promise Northwind about onboarding?
      10:42 AM

      Reading workspace memory…

      Northwind gets a two-week guided onboarding, starting Monday 2 November. Priya runs the kickoff in week one and opens a shared Slack channel for their team.

      Moving data from their old CRM covers contacts and deals only, not email history. A named support contact for the first 30 days is on the welcome checklist.

      • Granola call · by Dana Human · Oct 21

        Dana: We run a two-week guided onboarding, starting Monday the 2nd. Priya owns week one: the kickoff call, then a shared channel so their team can ask us anything.

        Said in the kickoff callSource quality details
        TrustHighwhy?
        RecencyHighwhy?

        Captured 8 days ago

      • Slack · by Priya Human · Oct 22

        Priya: Kickoff is booked for week one. I'll open a shared channel with their ops team the same day.

      • Coding session · by Codex AI · Oct 23

        Codex: Import scope follows the SOW: contacts and deals only. Email history is excluded, so the script skips the activities table.

      • Coding session · by Claude Code AI · Oct 24, 4:12 PM

        Claude Code: Added step 6 to the welcome checklist: a named support contact for the first 30 days after go-live.

      Also searched 5 files
      Northwind: 7 sources connectedRecall logged: Dana asked Tela in Northwind 4 cited: 2 by people, 2 by AI tools
      1. 1
        Sees what is connectedEvery source the workspace can search, shown above the question.
      2. 2
        Searches each sourceTela checks every connection and marks the ones that hold an answer.
      3. 3
        Cites the memory it usedEach number opens the memory and who made it, a person or an AI tool. The recall is logged.

      Quick to ask,light on every session.

      Your assistant calls MeshTale only when it needs context, and gets back just the cited pieces that answer the question. Your session stays fast and keeps its room for the actual work.

      Loaded before your assistant startstools
      A typical tool setuptens of thousands of tokens
      MeshTaleunder 1,000 tokens

      Two small tools, not a toolbox

      MeshTale adds two tools, described in under 1,000 tokens. Many setups spend tens of thousands before the model does any work.

      recall · northwindwithin budget
      • 1Renewal call notesGranola
      • 2#northwind-billingSlack
      • 3Northwind SOW v2Drive
      • +5 less relevant pieces left out, and counted

      Answers sized to fit

      Each recall comes back within a size budget: the most relevant cited pieces first, never whole documents pasted into your chat.

      Recall logExample data
      14:02:41recall · northwindfetched
      14:06:12recall · northwindfrom cache
      14:09:55recall · northwindfrom cache

      Repeat questions come back from cache

      Ask the same thing again and the answer comes straight from cache, still scoped to the same workspace and still logged.

      Governance you can point at,not a slide about next quarter.

      Who may see a memory, how guarded it is, how long it stays and whether a person has approved it all travel with the memory itself.

      New memory · Granola · Renewal callNorthwind data policy
      Dana asked us to send the revised SOW to dana.reyes@example.test[email masked] and to call her on +1 555 0142 881[phone masked] before Friday. Billing contact ID 482-19-7730[ID number masked] stays with finance.
      Detected 3 personal data itemsMasked before storing
      Mask emailsMask phone numbersMask ID numbersRestricted to account team
      Illustrative

      Sensitive data, caught before it is stored

      Personal data such as emails, phone numbers and ID numbers is detected on the way in and can be masked before it ever becomes a memory. Each workspace sets its own data policy and restrictions.

      Review queue3 waiting
      Renewal call notesWaitingApproved
      Pricing thread #billingWaitingApproved
      Draft SOW v3WaitingApproved
      Approved by Sam · now recallable

      Review before recall

      New memories can wait for a person to say yes before any agent can see them. Trust rules auto-approve the sources you already trust, so the queue only holds what needs a look.

      Agreed pricing floor for renewal
      audience: account-teamnorthwind
      Claude Code · NorthwindAllowed
      Sam · account teamAllowed
      Support assistantOut of scope

      Audience access

      Audience tags ride on the content, so the boundary belongs to the memory itself.

      Audit loglive
      14:02claude-code3 from Northwind
      14:02sam5 from Northwind
      13:58cursorrefused, out of scope
      13:51api · reports8 from Ardent Co
      13:44priya2 from Ardent Co

      Audit log

      Who asked, where, and what came back, and when. The record itself, not a summary.

      Collection defaultContracts
      Public
      Internal
      Confidential
      Restricted
      MSA v3.docxrestricted
      Kickoff notesinternal

      Sensitivity labels

      Every collection has a default, and any memory can be marked more guarded than its neighbours.

      Retentionper collection
      Contracts24 months
      Client comms12 months
      Coding sessions6 months

      Retention

      Decide how long each kind of context stays, in the same place you set who sees it.

      Personal

      Dana's Gmailonly Dana
      Dana's Granolaonly Dana

      Shared

      #northwind Slackaccount team
      Client Driveworkspace

      Personal and shared connections

      Connect your own inbox for yourself, or a team channel for everyone in the workspace.

      Exact

      "MSA v3" clause 4
      #northwind-billing

      Meaning

      renewal pricing call
      agreed discount

      Merged by rank

      1Renewal call notes
      2MSA v3, clause 4
      3#northwind-billing

      Exact and meaning search

      Keyword hits and similar-meaning hits, merged into one ranked list.

      When two memories disagree,a person decides.

      MeshTale notices when a new memory contradicts one you already hold, and asks the right person which one is accurate. Answers follow their decision.

      Northwind / Memories
      Example data
      New memories2 sources
      Google Drive
      Google DriveNorthwind SOW v2 · 3 Jun

      "Onboarding is two weeks, with a named contact."

      by Dana · uploaded the SOWHuman
      New memory Disagrees with 1 memory Accurate · confirmed by Priya OutdatedNo longer used in answers Kept · note from Priya
      Slack
      Slack#northwind-kickoff · 6 Jun

      "We agreed three weeks of onboarding."

      by Claude Code · session summaryAI
      New memory Disagrees with 1 memory Accurate · confirmed by Priya OutdatedNo longer used in answers Kept · note from Priya
      PriyaWorkspace admin · Northwind
      Needs review
      Nothing waiting for review
      ConflictResolvedNorthwindjust now

      These two memories disagree

      Onboarding length: 2 weeks vs 3 weeks

      • Google DriveNorthwind SOW v22 weeks
      • Slack#northwind-kickoff3 weeks
      Kept SOW v2Slack message marked Outdated

      Agent answers about Northwind will follow whatever Priya decides.

      ClaudeClaude Codeasks MeshTale

      Onboarding is two weeks, with a named contact.1

      Google Drive1 Northwind SOW v2 · AccurateNot used: #northwind-kickoff (Outdated)

      Onboarding is three weeks, as agreed at kickoff.1

      Slack1 #northwind-kickoff · AccurateNot used: Northwind SOW v2 (Outdated)

      Three weeks. The SOW says two, and Priya notes the kickoff added a week.1,2

      Google Drive1 Northwind SOW v2Slack2 #northwind-kickoff
      14:02 Conflict resolved · Priya · Northwindkept SOW v2 Audit log

      • Flagged automatically

        When a new memory contradicts one already in the workspace, both are marked and nothing is silently overwritten.

      • Decided by a person

        The alert goes to the workspace's reviewer. They keep one version, or keep both with a note that explains the difference.

      • Logged, and in every answer

        The decision lands in the audit log, and agents cite only the version the person confirmed from then on.

      Everything your team writes,in one memory for every agent.

      Connect the places work already happens. MeshTale reads, sorts into the right workspace and hands the right part back out.

      SlackMicrosoft TeamsDiscordGmailOutlookNotionConfluenceGoogle DriveDropboxSharePointObsidianOneNoteAmazon S3JiraLinearAsanaClickUpTrellomonday.comGitHubSalesforceHubSpotZendeskGranolaFathomZoom
      MeshTaleone governed memory
      Claude CodeMCP
      CursorMCP
      CodexMCP
      Any AI tool that speaks MCPMCPGeminiGrokWindsurfZMuseDevinVS Code+ more
      Your own softwareREST API
      Obsidianplugin
      Anything elsewebhooks, export

      All 26 sources on every plan. Browser extension in development.

      Your next coding agentstarts with what the last one learned.

      A command-line sync tool reads Claude Code, Codex, Gemini CLI, Grok and Muse session histories into the right workspace. Decisions, dead ends and fixes stop evaporating when a session closes.

      • Two tools to connect, one sentence each
      • Works in Claude Code, Cursor, Codex, Gemini, Grok, Windsurf, Zed and any MCP client
      • REST API with workspace-scoped keys, plus an Obsidian plugin
      Read the developer docs

      ClaudeClaude Code · Tue

      Fixed the webhook retry loop
      Kestrel API rate limit is 60/min
      Do not touch legacy billing module

      OpenAI (Codex)Codex · Wed

      Recalled 3 memories · Kestrel only
      Started from the retry fix
      Skipped the legacy module
      $ claude mcp add meshtale
      ✓ Connected. 2 tools registered.
      recall · recall_context_bundle
      2
      tools to connect

      Most setups spend thousands of tokens describing their tools before the model does any work. MeshTale registers two.

      ~8
      permission checks per answer

      Stacked authorization filters, applied to every query on every route.

      26
      sources supported

      Real implementations against real vendor APIs, plus webhooks in and out.

      Built for teams who workacross more than one client.

      Agency team reviewing work at a shared screen

      Agencies

      One workspace per client, so the brief for one never leaks into another.

       Consultants in a meeting

      Consultancies

      Engagement history every consultant and agent can draw on, kept apart.

       A fractional leader working on a laptop

      Fractional leaders

      Several companies in one head. Now in separate workspaces too.

       Developers at work

      Dev shops

      Coding agents that remember each client's codebase decisions.

       Sales team on a call

      Sales teams

      Every account's calls and threads, ready before the next one.

       Internal team collaborating

      Internal teams

      One memory across functions, with audience rules per team.

      Couldn't I justbuild this myself?

      Local memory is great for one person on one computer. A homemade setup can do anything, if someone builds it. Here is where each one stops.

      What you needLocal memoryNotes files or a memory tool on your computerDo it yourselfA vector database and a promptMeshTale
      Works without signing up for anythingYesYesFree account
      Runs entirely on your own computerYesIf you host itHosted, export any time
      Store and search contextYour ownYesBuilt in
      Shared by the whole team, on any deviceOne person, one machineBuild it yourselfBuilt in
      Works in every assistant, not just oneUsually one toolBuild it yourselfBuilt in
      One workspace per client, enforced in the data modelSeparate folders, by habitBuild it yourselfBuilt in
      Every recall logged with agent, workspace and resultNoBuild it yourselfBuilt in
      Answers that cite their sourcesSometimesBuild it yourselfBuilt in
      Audience, sensitivity and retention per memoryNoBuild it yourselfBuilt in
      Review queue before agents can recallNoBuild it yourselfBuilt in
      Personal data detected and masked before storingNoBuild it yourselfBuilt in
      26 connectors and coding-agent session syncCopy things in by handBuild it yourselfBuilt in

      Start free,grow by the client.

      Free

      Try it with your own agents. No card required.

      Pro

      For one person working across several clients.

      Agency

      A team, many client workspaces, review and audit.

      Scale

      More workspaces, more sources, more agents.

      Enterprise

      Custom terms and a direct line to the team.

      See pricing

      Questions

      Each client usually gets its own workspace, and every key and connection is bound to one. Separation runs through the data model, so a memory outside an agent's workspace is never in scope for it. Attempts to reach it are logged.

      Anything that speaks MCP, including Claude Code, Cursor, Codex, Gemini, Grok, Windsurf and Zed. You can also call the REST API with a workspace-scoped key, or use the Obsidian plugin.

      It is detected as content comes in, and each workspace can choose to mask it before it is stored. Data policies and restrictions are set per workspace.

      Yes. New memories can sit in a review queue until someone approves them. Until then, no agent can recall them.

      It is source-available under FSL-1.1-MIT, and there is a free tier with no card required.

      Give every agent and every teammatethe right context.

      Connect a source, connect an agent, and ask your first question.

      Start freeTalk to us
      Free tier, no card required.