@mastra/mcp-docs-server 1.1.1-alpha.0 → 1.1.1-alpha.2

package/.docs/docs/agents/agent-memory.md

@@ -2,7 +2,7 @@
 
 Agents use memory to maintain context across interactions. LLMs are stateless and don't retain information between calls, so agents need memory to track message history and recall relevant information.
 
-Mastra agents can be configured to store message history, with optional [working memory](https://mastra.ai/docs/memory/working-memory) to maintain recent context or [semantic recall](https://mastra.ai/docs/memory/semantic-recall) to retrieve past messages based on meaning.
+Mastra agents can be configured to store message history, with optional [working memory](https://mastra.ai/docs/memory/working-memory) to maintain recent context, [semantic recall](https://mastra.ai/docs/memory/semantic-recall) to retrieve past messages based on meaning, or [observational memory](https://mastra.ai/docs/memory/observational-memory) for automatic long-term memory that compresses conversations as they grow.
 
 ## When to use memory
 
@@ -134,6 +134,49 @@ const response = await memoryAgent.generate("What's my favorite color?", {
 
 To learn more about memory see the [Memory](https://mastra.ai/docs/memory/overview) documentation.
 
+## Observational Memory
+
+For long-running conversations, raw message history grows until it fills the context window, degrading agent performance. [Observational Memory](https://mastra.ai/docs/memory/observational-memory) solves this by running background agents that compress old messages into dense observations, keeping the context window small while preserving long-term memory.
+
+```typescript
+import { Agent } from "@mastra/core/agent";
+import { Memory } from "@mastra/memory";
+
+export const memoryAgent = new Agent({
+  id: 'memory-agent',
+  name: 'Memory Agent',
+  memory: new Memory({
+    options: {
+      observationalMemory: true,
+    },
+  }),
+});
+```
+
+Setting `observationalMemory: true` uses `google/gemini-2.5-flash` as the default model for the Observer and Reflector. To use a different model or customize thresholds, pass a config object:
+
+```typescript
+import { Agent } from "@mastra/core/agent";
+import { Memory } from "@mastra/memory";
+
+export const memoryAgent = new Agent({
+  id: 'memory-agent',
+  name: 'Memory Agent',
+  memory: new Memory({
+    options: {
+      observationalMemory: {
+        model: "deepseek/deepseek-reasoner",
+        observation: {
+          messageTokens: 20_000,
+        },
+      },
+    },
+  }),
+});
+```
+
+> **Info:** See [Observational Memory](https://mastra.ai/docs/memory/observational-memory) for details on how observations and reflections work, and [the reference](https://mastra.ai/reference/memory/observational-memory) for all configuration options.
+
 ## Using `RequestContext`
 
 Use [RequestContext](https://mastra.ai/docs/server/request-context) to access request-specific values. This lets you conditionally select different memory or storage configurations based on the context of the request.
@@ -162,6 +205,7 @@ export const memoryAgent = new Agent({
 
 ## Related
 
+- [Observational Memory](https://mastra.ai/docs/memory/observational-memory)
 - [Working Memory](https://mastra.ai/docs/memory/working-memory)
 - [Semantic Recall](https://mastra.ai/docs/memory/semantic-recall)
 - [Storage](https://mastra.ai/docs/memory/storage)

package/.docs/docs/agents/network-approval.md

@@ -1,6 +1,6 @@
 # Network Approval
 
-Agent networks can require the same [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) oversight used in individual agents and workflows. When a tool, sub-agent, or workflow within a network requires approval or suspends execution, the network pauses and emits events that allow your application to collect user input before resuming.
+Agent networks can require the same [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) oversight used in individual agents and workflows. When a tool, subagent, or workflow within a network requires approval or suspends execution, the network pauses and emits events that allow your application to collect user input before resuming.
 
 ## Storage
 

package/.docs/docs/agents/networks.md

@@ -1,6 +1,6 @@
 # Agent Networks
 
-Agent networks in Mastra coordinate multiple agents, workflows, and tools to handle tasks that aren't clearly defined upfront but can be inferred from the user's message or context. A top-level **routing agent** (a Mastra agent with other agents, workflows, and tools configured) uses an LLM to interpret the request and decide which primitives (sub-agents, workflows, or tools) to call, in what order, and with what data.
+Agent networks in Mastra coordinate multiple agents, workflows, and tools to handle tasks that aren't clearly defined upfront but can be inferred from the user's message or context. A top-level **routing agent** (a Mastra agent with other agents, workflows, and tools configured) uses an LLM to interpret the request and decide which primitives (subagents, workflows, or tools) to call, in what order, and with what data.
 
 ## When to use networks
 
@@ -16,7 +16,7 @@ Mastra agent networks operate using these principles:
 
 ## Creating an agent network
 
-An agent network is built around a top-level routing agent that delegates tasks to agents, workflows, and tools defined in its configuration. Memory is configured on the routing agent using the `memory` option, and `instructions` define the agent's routing behavior.
+An agent network is built around a top-level routing agent that delegates tasks to subagents, workflows, and tools defined in its configuration. Memory is configured on the routing agent using the `memory` option, and `instructions` define the agent's routing behavior.
 
 ```typescript
 import { Agent } from "@mastra/core/agent";
@@ -64,7 +64,7 @@ When configuring a Mastra agent network, each primitive (agent, workflow, or too
 
 #### Agent descriptions
 
-Each agent in a network should include a clear `description` that explains what the agent does.
+Each subagent in a network should include a clear `description` that explains what the agent does.
 
 ```typescript
 export const researchAgent = new Agent({

package/.docs/docs/agents/overview.md

@@ -119,6 +119,14 @@ export const mastra = new Mastra({
 });
 ```
 
+### Registering subagents
+
+You can register subagents within an agent. They'll be executed as tools from the parent agent. Read the [using agents as tools](https://mastra.ai/docs/agents/using-tools) documentation to learn more.
+
+### Registering subworkflows
+
+You can register subworkflows within an agent. They'll be executed as tools from the parent agent. Read the [using workflows as tools](https://mastra.ai/docs/agents/using-tools) documentation to learn more.
+
 ## Referencing an agent
 
 You can call agents from workflow steps, tools, the Mastra Client, or the command line. Get a reference by calling `.getAgent()` on your `mastra` or `mastraClient` instance, depending on your setup:

package/.docs/docs/agents/using-tools.md

@@ -57,84 +57,49 @@ export const weatherAgent = new Agent({
 });
 ```
 
-## Controlling `toolName` in stream responses
+## Using multiple tools
 
-The `toolName` in stream responses is determined by the **object key** you use, not the `id` property of the tool, agent, or workflow.
+When multiple tools are available, the agent may choose to use one, several, or none, depending on what's needed to answer the query.
 
 ```typescript
-// Tool defined with id: "weather-tool"
-export const weatherTool = createTool({
-  id: "weather-tool",
-  // ...
-});
-
-// Using the variable name as the key
-tools: { weatherTool }
-// Stream returns: toolName: "weatherTool"
-
-// Using the tool's id as the key
-tools: { [weatherTool.id]: weatherTool }
-// Stream returns: toolName: "weather-tool"
+import { weatherTool } from "../tools/weather-tool";
+import { activitiesTool } from "../tools/activities-tool";
 
-// Using a custom key
-tools: { "my-custom-name": weatherTool }
-// Stream returns: toolName: "my-custom-name"
+export const weatherAgent = new Agent({
+  id: "weather-agent",
+  name: "Weather Agent",
+  tools: { weatherTool, activitiesTool },
+});
 ```
 
-This lets you specify how tools are identified in the stream. If you want the `toolName` to match the tool's `id`, use the tool's `id` as the object key.
-
-### Sub-agents and workflows as tools
-
-Sub-agents and workflows follow the same pattern. They are converted to tools with a prefix followed by your object key:
+## Using agents as tools
 
-| Property    | Prefix      | Example key | `toolName`          |
-| ----------- | ----------- | ----------- | ------------------- |
-| `agents`    | `agent-`    | `weather`   | `agent-weather`     |
-| `workflows` | `workflow-` | `research`  | `workflow-research` |
+Agents can be added to other agents through the `agents` configuration. When you add a subagent, Mastra automatically converts it to a tool that the parent agent can call. The generated tool is named `agent-<agentName>`.
 
 ```typescript
-const orchestrator = new Agent({
-  // ...
+import { Agent } from "@mastra/core/agent";
+
+export const parentAgent = new Agent({
+  id: "parent-agent",
+  name: "Parent Agent",
+  description: "Take care in writing a good description here",
+  instructions: `Instructions`,
+  model: "openai/gpt-5.1",
   agents: {
-    weather: weatherAgent,  // toolName: "agent-weather"
-  },
-  workflows: {
-    research: researchWorkflow,  // toolName: "workflow-research"
+    subAgent,
   },
 });
-```
-
-Note that for sub-agents, you'll see two different identifiers in stream responses:
 
-- `toolName: "agent-weather"` in tool call events — the generated tool wrapper name
-- `id: "weather-agent"` in `data-tool-agent` chunks — the sub-agent's actual `id` property
-
-## Calling an agent
-
-The agent uses the tool's `inputSchema` to infer what data the tool expects. In this case, it extracts `London` as the `location` from the message and passes it to the tool's inputData parameter.
-
-```typescript
-import { mastra } from "./mastra";
-
-const agent = mastra.getAgent("weatherAgent");
-
-const result = await agent.generate("What's the weather in London?");
+const subAgent = new Agent({
+  id: "sub-agent",
+  name: "Sub Agent",
+  description: "Take care in writing a good description here",
+  instructions: `Instructions`,
+  model: "openai/gpt-5.1",
+})
 ```
 
-## Using multiple tools
-
-When multiple tools are available, the agent may choose to use one, several, or none, depending on what's needed to answer the query.
-
-```typescript
-import { weatherTool } from "../tools/weather-tool";
-import { activitiesTool } from "../tools/activities-tool";
-
-export const weatherAgent = new Agent({
-  id: "weather-agent",
-  name: "Weather Agent",
-  tools: { weatherTool, activitiesTool },
-});
-```
+The subagent should include a `description` to help the parent agent understand when to use it. See the [`toolName` docs](#subagents-and-workflows-as-tools) to learn more about the tool naming scheme.
 
 ## Using workflows as tools
 
@@ -169,16 +134,8 @@ import { z } from "zod";
 export const researchWorkflow = createWorkflow({
   id: "research-workflow",
   description: "Gathers information on a topic and compiles a summary report.",
-  inputSchema: z.object({
-    topic: z.string(),
-  }),
-  outputSchema: z.object({
-    summary: z.string(),
-    sources: z.array(z.string()),
-  }),
+  // Rest of the workflow...
 })
-  .then(gatherSourcesStep)
-  .then(compileReportStep)
   .commit();
 ```
 
@@ -191,6 +148,59 @@ When the agent calls the workflow tool, it receives a response containing the wo
 }
 ```
 
+See the [`toolName` docs](#subagents-and-workflows-as-tools) to learn more about the tool naming scheme.
+
+## Controlling `toolName` in stream responses
+
+The `toolName` in stream responses is determined by the **object key** you use, not the `id` property of the tool, agent, or workflow.
+
+```typescript
+// Tool defined with id: "weather-tool"
+export const weatherTool = createTool({
+  id: "weather-tool",
+  // ...
+});
+
+// Using the variable name as the key
+tools: { weatherTool }
+// Stream returns: toolName: "weatherTool"
+
+// Using the tool's id as the key
+tools: { [weatherTool.id]: weatherTool }
+// Stream returns: toolName: "weather-tool"
+
+// Using a custom key
+tools: { "my-custom-name": weatherTool }
+// Stream returns: toolName: "my-custom-name"
+```
+
+This lets you specify how tools are identified in the stream. If you want the `toolName` to match the tool's `id`, use the tool's `id` as the object key.
+
+### Subagents and workflows as tools
+
+Subagents and workflows follow the same pattern. They are converted to tools with a prefix followed by your object key:
+
+| Property    | Prefix      | Example key | `toolName`          |
+| ----------- | ----------- | ----------- | ------------------- |
+| `agents`    | `agent-`    | `weather`   | `agent-weather`     |
+| `workflows` | `workflow-` | `research`  | `workflow-research` |
+
+```typescript
+const orchestrator = new Agent({
+  agents: {
+    weather: weatherAgent,  // toolName: "agent-weather"
+  },
+  workflows: {
+    research: researchWorkflow,  // toolName: "workflow-research"
+  },
+});
+```
+
+Note that for subagents, you'll see two different identifiers in stream responses:
+
+- `toolName: "agent-weather"` in tool call events — the generated tool wrapper name
+- `id: "weather-agent"` in `data-tool-agent` chunks — the subagent's actual `id` property
+
 ## Tools with structured output
 
 When using tools with [structured output](https://mastra.ai/docs/agents/structured-output), some models don't support combining both features in the same API call. If your tools aren't being called when structured output is enabled, or you receive errors about incompatible options, see [Combining tools and structured output](https://mastra.ai/docs/agents/structured-output) for model compatibility information and workarounds.

package/.docs/docs/{getting-started → build-with-ai}/mcp-docs-server.md

@@ -1,6 +1,6 @@
 # Mastra Docs Server
 
-The `@mastra/mcp-docs-server` package provides direct access to Mastra’s full knowledge base, including documentation, code examples, blog posts, and changelogs, via the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). It works with Cursor, Windsurf, Cline, Claude Code, VS Code, Codex or any tool that supports MCP.
+The `@mastra/mcp-docs-server` package provides direct access to Mastra’s full documentation via the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). It works with Cursor, Windsurf, Cline, Claude Code, VS Code, Codex or any tool that supports MCP.
 
 These tools are designed to help agents retrieve precise, task-specific information — whether you're adding a feature to an agent, scaffolding a new project, or exploring how something works.
 
@@ -219,7 +219,6 @@ Once configured, you can ask your AI tool questions about Mastra or instruct it
 **Ask about integrations:**
 
 - "Does Mastra work with the AI SDK? How can I use it in my `[React/Svelte/etc]` project?"
-- "What's the latest Mastra news around MCP?"
 - "Does Mastra support `[provider]` speech and voice APIs? Show me an example in my code of how I can use it."
 
 **Debug or update existing code:**

package/.docs/docs/build-with-ai/skills.md

@@ -0,0 +1,35 @@
+# Mastra Skills
+
+Mastra Skills are folders of instructions, scripts, and resources that agents can discover and use to gain Mastra knowledge. They contain setup instructions, best practices, and methods to fetch up-to-date information from Mastra's documentation.
+
+## Installation
+
+To install all available Mastra skills, run the following command:
+
+**npm**:
+
+```bash
+npx skills add mastra-ai/skills
+```
+
+**pnpm**:
+
+```bash
+pnpm dlx skills add mastra-ai/skills
+```
+
+**Yarn**:
+
+```bash
+yarn dlx skills add mastra-ai/skills
+```
+
+**Bun**:
+
+```bash
+bun x skills add mastra-ai/skills
+```
+
+Mastra skills work with any coding agent that supports the [Skills standard](https://agentskills.io/), including Claude Code, Cursor, Codex, OpenCode, and others.
+
+They are also available on [GitHub](https://github.com/mastra-ai/skills).

package/.docs/docs/community/contributing-templates.md

@@ -1,184 +1,3 @@
 # Contributing Templates
 
-The Mastra community plays a vital role in creating templates that showcase innovative application patterns. This guide explains how to contribute your own templates to the Mastra ecosystem.
-
-## Template Contribution Process
-
-### 1. Review Requirements
-
-Before creating a template, ensure you understand:
-
-- [Templates Reference](https://mastra.ai/reference/templates/overview) - Technical requirements and conventions
-- [Project Structure](https://mastra.ai/docs/getting-started/project-structure) - Standard Mastra project organization
-- Community guidelines and quality standards
-
-### 2. Develop Your Template
-
-Create your template following the established patterns:
-
-- Focus on a specific use case or pattern
-- Include comprehensive documentation
-- Test thoroughly with fresh installations
-- Follow all technical requirements
-- Ensure the github repo is a template repo. [How to create a template repo](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository)
-
-### 3. Submit for Review
-
-Once your template is ready, submit it through our contribution form. Templates undergo an approval process to ensure quality and consistency.
-
-## Submission Guidelines
-
-### Template Criteria
-
-We accept templates that:
-
-- **Demonstrate unique value** - Show innovative use cases or patterns not covered by existing templates
-- **Follow conventions** - Adhere to all technical requirements and structural guidelines
-- **Include quality documentation** - Provide clear setup instructions and usage examples
-- **Work reliably** - Function correctly with minimal setup after installation
-
-### Quality Standards
-
-Templates must meet these quality benchmarks:
-
-- **Code quality** - Clean, well-commented, and maintainable code
-- **Error handling** - Proper error handling for external APIs and user inputs
-- **Type safety** - Full TypeScript typing with Zod validation where appropriate
-- **Documentation** - Comprehensive README with setup and usage instructions
-- **Testing** - Verified to work with fresh installations
-
-## Submission Process
-
-### 1. Prepare Your Template
-
-Ensure your template meets all requirements outlined in the [Templates Reference](https://mastra.ai/reference/templates/overview):
-
-- Proper project structure in `src/mastra/` directory
-- Standard TypeScript configuration
-- Comprehensive `.env.example` file
-- Detailed README with setup instructions
-
-### 2. Submit Your Template
-
-Submit your template using our contribution form:
-
-**[Submit Template Contribution](https://forms.gle/g1CGuwFxqbrb3Rz57)**
-
-### Required Information
-
-When submitting your template, provide:
-
-- **Template Name** - Clear, descriptive name indicating the use case
-- **Template Author Name** - Your name or organization name
-- **Template Author Email** - Contact email for communication about your submission
-- **GitHub URL** - Link to your template repository
-- **Description** - Detailed explanation of what the template does and its value
-- **Optional Image** - Screenshot or diagram showing the template in action
-- **Optional Demo Video** - Link to a video demonstrating the template's functionality
-
-## Review Process
-
-### Review Criteria
-
-Templates are evaluated on:
-
-- **Technical compliance** - Adherence to template rules and conventions
-- **Code quality** - Clean, maintainable, and well-documented code
-- **Uniqueness** - Novel use cases or innovative implementation patterns
-- **Educational value** - Ability to teach Mastra concepts effectively
-- **Community benefit** - Potential value to the broader Mastra community
-
-### Feedback and Iteration
-
-If your template needs improvements:
-
-- You'll receive specific feedback on required changes
-- Make the requested modifications and resubmit
-- The review process continues until the template meets standards
-
-## Community Guidelines
-
-### Template Ideas
-
-Consider creating templates for:
-
-- **Industry-specific use cases** - Healthcare, finance, education, etc.
-- **Integration patterns** - Specific API or service integrations
-- **Advanced techniques** - Complex workflows, multi-agent systems, or novel patterns
-- **Learning resources** - Step-by-step tutorials for specific concepts
-
-### Development Best Practices
-
-- **Start simple** - Begin with a minimal working example and add complexity gradually
-- **Document thoroughly** - Include detailed comments and comprehensive README
-- **Test extensively** - Verify your template works across different environments
-- **Seek feedback** - Share with the community for early feedback before submission
-
-### Community Engagement
-
-- **Join Discord** - Participate in the [Mastra Discord community](https://discord.gg/BTYqqHKUrf)
-- **Share progress** - Update the community on your template development
-- **Help others** - Assist other contributors with their templates
-- **Stay updated** - Keep track of new Mastra features and conventions
-
-## Template Maintenance
-
-### Ongoing Responsibilities
-
-As a template contributor, you may be asked to:
-
-- **Update dependencies** - Keep templates current with latest Mastra versions
-- **Fix issues** - Address bugs or compatibility problems
-- **Improve documentation** - Enhance instructions based on user feedback
-- **Add features** - Extend templates with new capabilities
-
-### Community Support
-
-The Mastra team and community provide:
-
-- **Technical guidance** - Help with complex implementation challenges
-- **Review feedback** - Detailed feedback to improve template quality
-- **Promotion** - Showcase approved templates to the community
-- **Maintenance assistance** - Support for keeping templates up-to-date
-
-## Validation Checklist
-
-Before submitting a template, verify:
-
-- [ ] All code organized in `src/mastra/` directory
-- [ ] Uses standard Mastra TypeScript configuration
-- [ ] Includes comprehensive `.env.example`
-- [ ] Has detailed README with setup instructions
-- [ ] No monorepo or web framework boilerplate
-- [ ] Successfully runs after fresh install and environment setup
-- [ ] Follows all code quality standards
-- [ ] Demonstrates clear, valuable use case
-
-## Community Showcase
-
-### Template Gallery
-
-Approved templates will be featured in:
-
-- **mastra.ai/templates** - Community template gallery (coming soon)
-- **Documentation** - Referenced in relevant documentation sections
-- **Community highlights** - Featured in newsletters and community updates
-
-### Recognition
-
-Template contributors receive:
-
-- **Attribution** - Your name and contact information with the template
-- **Community recognition** - Acknowledgment in community channels
-
-## Getting Started
-
-Ready to contribute a template?
-
-1. **Explore existing templates** - Review current templates for inspiration and patterns
-2. **Plan your template** - Define the use case and value proposition
-3. **Follow the requirements** - Ensure compliance with all technical requirements
-4. **Build and test** - Create a working, well-documented template
-5. **Submit for review** - Use the contribution form to submit your template
-
-> **Info:** Your contributions help grow the Mastra ecosystem and provide valuable resources for the entire community. We look forward to seeing your innovative templates!
+The Mastra community plays a vital role in creating templates that showcase innovative application patterns. We're currently reworking our template contribution process to ensure high-quality, valuable templates for the community. For the time being, we're not accepting new template contributions. Please keep an eye on this page for updates on when contributions will reopen and the new submission process.

package/.docs/docs/community/discord.md

@@ -1,6 +1,8 @@
 # Discord Community
 
-The Discord server has over 1000 members and serves as the main discussion forum for Mastra. The Mastra team monitors Discord during North American and European business hours, with community members active across other time zones.[Join the Discord server](https://discord.gg/BTYqqHKUrf).
+The Discord server has over 1000 members and serves as the main discussion forum for Mastra. The Mastra team monitors Discord during North American and European business hours, with community members active across other time zones.
+
+[Join the Discord server](https://discord.gg/BTYqqHKUrf)
 
 ## Discord MCP Bot
 

package/.docs/docs/deployment/cloud-providers.md

@@ -11,5 +11,5 @@ The following guides show how to deploy Mastra to specific cloud providers:
 - [Azure App Services](https://mastra.ai/guides/deployment/azure-app-services)
 - [Cloudflare](https://mastra.ai/guides/deployment/cloudflare-deployer)
 - [Digital Ocean](https://mastra.ai/guides/deployment/digital-ocean)
-- [Netlify](https://mastra.ai/guides/deployment/netlify-deployer)
-- [Vercel](https://mastra.ai/guides/deployment/vercel-deployer)
+- [Netlify](https://mastra.ai/guides/deployment/netlify)
+- [Vercel](https://mastra.ai/guides/deployment/vercel)

package/.docs/docs/deployment/overview.md

@@ -36,8 +36,8 @@ Use this option for auto-scaling, minimal infrastructure management, or when you
 - [Azure App Services](https://mastra.ai/guides/deployment/azure-app-services)
 - [Cloudflare](https://mastra.ai/guides/deployment/cloudflare-deployer)
 - [Digital Ocean](https://mastra.ai/guides/deployment/digital-ocean)
-- [Netlify](https://mastra.ai/guides/deployment/netlify-deployer)
-- [Vercel](https://mastra.ai/guides/deployment/vercel-deployer)
+- [Netlify](https://mastra.ai/guides/deployment/netlify)
+- [Vercel](https://mastra.ai/guides/deployment/vercel)
 
 ### Web Framework
 

package/.docs/docs/getting-started/build-with-ai.md

@@ -0,0 +1,68 @@
+# Build with AI
+
+AI agents may not have up-to-date knowledge about Mastra's APIs, patterns, and best practices. These resources give your AI tools direct access to current Mastra documentation, enabling them to generate accurate code and help you build faster.
+
+## Mastra Skills
+
+Agent Skills are folders of instructions, scripts, and resources that agents can discover and use to do things more accurately and efficiently. [Mastra Skills](https://mastra.ai/docs/build-with-ai/skills) contain setup instructions, best practices, and instructions on how to fetch up-to-date information from Mastra's documentation.
+
+**npm**:
+
+```bash
+npx skills add mastra-ai/skills
+```
+
+**pnpm**:
+
+```bash
+pnpm dlx skills add mastra-ai/skills
+```
+
+**Yarn**:
+
+```bash
+yarn dlx skills add mastra-ai/skills
+```
+
+**Bun**:
+
+```bash
+bun x skills add mastra-ai/skills
+```
+
+Read the dedicated [Mastra Skills](https://mastra.ai/docs/build-with-ai/skills) guide to learn more about installation options and available skills.
+
+> **Tip:** If you're just interested in giving your agent access to Mastra's documentation, we recommend using **Skills**. While the MCP Docs Server also provides this information, Skills will perform better. Use the MCP Docs Server when you need its tools, e.g. the migration tool.
+
+## MCP Docs Server
+
+In addition to documentation access, the [MCP Docs Server](https://mastra.ai/docs/build-with-ai/mcp-docs-server) also provides tools to help you migrate to newer versions of Mastra or follow the [Mastra 101 course](https://mastra.ai/course).
+
+Learn how to use the [MCP Docs Server](https://mastra.ai/docs/build-with-ai/mcp-docs-server).
+
+## Embedded package docs
+
+Mastra packages ship with embedded documentation in `dist/docs`. When you install a Mastra package, your AI agent can read these files directly from `node_modules` to understand the package's APIs and patterns.
+
+Each `dist/docs` includes:
+
+- `SKILL.md`: A skill file following the skills standard
+- `references/`: A folder with documentation files relevant to the package
+- `assets/SOURCE_MAP.json`: A source map file linking public exports to their location in `node_modules`
+
+## Context files
+
+Mastra provides a root [`llms.txt`](https://mastra.ai/llms.txt) file that contains an overview of all available documentation pages.
+
+Each documentation page also has its own `llms.txt` file. These files are streamlined markdown files. At the end of each docs page you'll find a link to the corresponding `llms.txt` file.
+
+Add `/llms.txt` to any Mastra docs URL to access it. You can also request it by adding a `.md` extension to the end of the URL.
+
+Examples for the [introduction page](https://mastra.ai/docs):
+
+- [`/docs/llms.txt`](https://mastra.ai/docs/llms.txt)
+- [`/docs.md`](https://mastra.ai/docs.md)
+
+## Mastra's documentation
+
+In addition to the [context files](#context-files) each documentation page also features a "Copy markdown" button at the top of the page. It'll copy the streamlined markdown version to your clipboard. Beside it, you'll find a dropdown menu to open the page on GitHub, in ChatGPT, Claude, and others.

package/.docs/docs/getting-started/start.md

@@ -19,6 +19,7 @@ Add Mastra to an existing project, or scaffold a new Mastra-powered app if you
 - [Nuxt](https://mastra.ai/guides/getting-started/nuxt)
 - [Express](https://mastra.ai/guides/getting-started/express)
 - [Hono](https://mastra.ai/guides/getting-started/hono)
+- [Electron](https://mastra.ai/guides/getting-started/electron)
 
 Mastra works great with agentic UI frameworks like [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui), [CopilotKit](https://mastra.ai/guides/build-your-ui/copilotkit), and [Assistant UI](https://mastra.ai/guides/build-your-ui/assistant-ui). Use them with any of the frontend frameworks above to stream agent responses, render tools, and build chat interfaces.