Mastra gives agents shared, editable knowledge stores
Mastra has introduced Knowledge, a shared store for documents, policies and decisions that lets its agents search, read and update information across defined access scopes. The feature works with Mastra's Signals context engineering primitive, which brings relevant knowledge into an agent's context and keeps it current while the agent runs.
- Knowledge stores shared information as named markdown pages.
- Scopes control access for organizations, users and conversations.
- Agents can search, read, create, edit and annotate pages.
- Importers for Notion, Confluence, Linear, Zendesk and Fireflies are coming in the next release.
- Knowledge is in alpha and its API may change.
A shared source of company context
Mastra says Knowledge is designed for information that agents cannot reliably obtain from training data, including why a feature was built a certain way, which policy applies, or what a team has already tried. That information may be spread across multiple systems or held by one person.
Knowledge stores information as named markdown documents called pages. Each page belongs to a scope, which determines which organizations, users or conversations can read or write it. The knowledgeMemoryScopes() helper sets up three scopes: org, shared with everyone in an organization, resource, visible to one user, and thread, limited to one conversation.
Mastra positions the feature as an alternative to relying only on instructions, retrieval-augmented generation, skills or tools that query APIs and databases. Those approaches are usually read-only, while Knowledge allows an agent to update stored information as it works.
Agents can search, edit and add notes
Developers can enable Knowledge tools when creating a Knowledge instance. Mastra provides five tools: knowledge_search finds matching pages and notes, knowledge_list lists pages in a scope, knowledge_read reads a page, knowledge_page creates or edits a page, and knowledge_note adds a note to a page.
Every call passes its scopes. For a question, an agent can search and read pages across an organization, user and conversation scope. For an update, it can write to the scope that matches the request. Mastra's example uses a request to save a refund window “for the team” as an organization-level update.
Knowledge can also be viewed in Studio. The Knowledge page displays scopes and pages as a tree beside a graph showing how pages link. Mastra says a Studio example includes an agent answering from pages and a coding agent turning a pinned proposal into a pull request, with the result recorded on the page as a note.
Setup, imports and alpha status
Developers can seed Knowledge with existing documents or use Mastra Connect on the Mastra platform. Mastra says importers for Notion, Confluence, Linear, Zendesk and Fireflies are planned for the next release, making it easier to connect those data sources.
The installation command uses @mastra/core@latest, @mastra/server@latest and @mastra/libsql@latest. The announcement says the feature requires @mastra/[email protected] or later. Knowledge is stored through the configured storage provider, which adds tables for pages, notes, mentions, pinned pages, scopes, access and recent activity.
Mastra describes Knowledge as being in alpha, so its API may change between releases. For users building Mastra agents, the feature provides a way to keep organization-specific context editable and available within the access boundaries assigned to each agent.
Mastra: Introducing Knowledge for Mastra Agents | Mastra Blog
