@mastra/mcp-docs-server 1.2.15-alpha.9 → 1.2.15

package/.docs/docs/server/mastra-server.md

@@ -4,7 +4,7 @@
 
 Mastra runs as an HTTP server that exposes your agents, workflows, and other functionality as API endpoints. The server handles request routing, middleware execution, authentication, and streaming responses.
 
-> **Info:** This page covers the [`server`](https://mastra.ai/reference/configuration) configuration options passed to the `Mastra` constructor. For running Mastra with your own HTTP server (Hono, Express, etc.), visit [Server Adapters](https://mastra.ai/docs/server/server-adapters).
+> **Note:** This page covers the [`server`](https://mastra.ai/reference/configuration) configuration options passed to the `Mastra` constructor. For running Mastra with your own HTTP server (Hono, Express, etc.), visit [Server Adapters](https://mastra.ai/docs/server/server-adapters).
 
 ## Server features
 

package/.docs/docs/storage/overview.md

@@ -190,18 +190,20 @@ You can also route `observability` to a dedicated analytics backend. See the [ob
 
 Each provider page includes installation instructions, configuration parameters, and usage examples:
 
-- [libSQL](https://mastra.ai/reference/storage/libsql)
-- [PostgreSQL](https://mastra.ai/reference/storage/postgresql)
-- [MongoDB](https://mastra.ai/reference/storage/mongodb)
-- [Upstash](https://mastra.ai/reference/storage/upstash)
-- [Redis](https://mastra.ai/reference/storage/redis)
-- [Cloudflare D1](https://mastra.ai/reference/storage/cloudflare-d1)
-- [Cloudflare KV & Durable Objects](https://mastra.ai/reference/storage/cloudflare)
-- [Convex](https://mastra.ai/reference/storage/convex)
-- [DynamoDB](https://mastra.ai/reference/storage/dynamodb)
-- [LanceDB](https://mastra.ai/reference/storage/lance)
-- [Microsoft SQL Server](https://mastra.ai/reference/storage/mssql)
-- [Google Cloud Spanner](https://mastra.ai/reference/storage/spanner)
+- [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1)
+- [Cloudflare KV & Durable Objects](https://mastra.ai/integrations/databases/cloudflare-kv)
+- [Convex](https://mastra.ai/integrations/databases/convex)
+- [DynamoDB](https://mastra.ai/integrations/databases/dynamodb)
+- [Google Cloud Spanner](https://mastra.ai/integrations/databases/spanner)
+- [LanceDB](https://mastra.ai/integrations/databases/lancedb)
+- [libSQL](https://mastra.ai/integrations/databases/libsql)
+- [Microsoft SQL Server](https://mastra.ai/integrations/databases/mssql)
+- [MongoDB](https://mastra.ai/integrations/databases/mongodb)
+- [Neon Postgres](https://mastra.ai/integrations/databases/neon)
+- [OracleDB](https://mastra.ai/integrations/databases/oracledb)
+- [PostgreSQL](https://mastra.ai/integrations/databases/postgresql)
+- [Redis](https://mastra.ai/integrations/databases/redis)
+- [Upstash](https://mastra.ai/integrations/databases/upstash)
 
 > **Tip:** libSQL is the fastest path for local development because it doesn't require running a separate database server.
 

package/.docs/docs/studio/observability.md

@@ -12,7 +12,7 @@ All require an observability storage backend to be configured.
 
 ## Quickstart
 
-For detailed instructions, follow the [observability instructions](https://mastra.ai/docs/observability/overview). To get up and running quickly, add the `@mastra/observability` package to your project and configure it with [LibSQL](https://mastra.ai/reference/storage/libsql) and [DuckDB](https://mastra.ai/reference/vectors/duckdb) for a local development setup that supports both traces and metrics.
+For detailed instructions, follow the [observability instructions](https://mastra.ai/docs/observability/overview). To get up and running quickly, add the `@mastra/observability` package to your project and configure it with [LibSQL](https://mastra.ai/integrations/databases/libsql) and [DuckDB](https://mastra.ai/reference/vectors/duckdb) for a local development setup that supports both traces and metrics.
 
 **npm**:
 

package/.docs/docs/workflows/dynamic-workflows.md

@@ -2,7 +2,7 @@
 
 # Dynamic workflows
 
-> **Beta:** This feature is in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 Dynamic workflows are workflow definitions expressed as data instead of code. A definition is a JSON document that describes the workflow's schemas and step graph. Mastra validates the definition and registers it as a runnable workflow, then persists it in storage so it survives process restarts.
 

package/.docs/docs/workflows/overview.md

@@ -287,7 +287,7 @@ You can run workflows from agents, tools, the Mastra Client, or the command line
 const testWorkflow = mastra.getWorkflow('testWorkflow')
 ```
 
-> **Info:** `mastra.getWorkflow()` is preferred over a direct import for two reasons:
+> **Note:** `mastra.getWorkflow()` is preferred over a direct import for two reasons:
 >
 > 1. It provides access to the Mastra instance configuration (logger, telemetry, storage, registered agents, and vector stores)
 > 2. It provides full TypeScript type inference for workflow input and output schemas
@@ -407,7 +407,7 @@ Here's an example of a successful workflow result, showing the `input`, `steps`,
 
 ## Streaming
 
-For generic `writer` API usage, see [Streaming](https://mastra.ai/guides/concepts/streaming).
+For generic `writer` API usage, see [Streaming](https://mastra.ai/docs/guides/streaming).
 
 ### Inspecting workflow stream payloads
 

package/.docs/docs/workflows/snapshots.md

@@ -81,13 +81,14 @@ Each snapshot includes the `runId`, input, step status (`success`, `suspended`,
 
 ## How snapshots are saved and retrieved
 
-Snapshots are saved to the configured storage system. By default, they use libSQL, but you can configure Upstash or PostgreSQL instead. Each snapshot is saved in the `workflow_snapshots` table and identified by the workflow's `runId`.
+Snapshots are saved to the configured storage system. By default, they use libSQL, but you can configure Upstash, PostgreSQL, or OracleDB instead. Each snapshot is saved in the `workflow_snapshots` table and identified by the workflow's `runId`.
 
 Read more about:
 
-- [libSQL Storage](https://mastra.ai/reference/storage/libsql)
-- [Upstash Storage](https://mastra.ai/reference/storage/upstash)
-- [PostgreSQL Storage](https://mastra.ai/reference/storage/postgresql)
+- [libSQL Storage](https://mastra.ai/integrations/databases/libsql)
+- [Upstash Storage](https://mastra.ai/integrations/databases/upstash)
+- [PostgreSQL Storage](https://mastra.ai/integrations/databases/postgresql)
+- [OracleDB Storage](https://mastra.ai/integrations/databases/oracledb)
 
 ### Saving snapshots
 
@@ -139,12 +140,13 @@ export const mastra = new Mastra({
 })
 ```
 
-- [libSQL Storage](https://mastra.ai/reference/storage/libsql)
-- [PostgreSQL Storage](https://mastra.ai/reference/storage/postgresql)
-- [MongoDB Storage](https://mastra.ai/reference/storage/mongodb)
-- [Upstash Storage](https://mastra.ai/reference/storage/upstash)
-- [Cloudflare D1](https://mastra.ai/reference/storage/cloudflare-d1)
-- [DynamoDB](https://mastra.ai/reference/storage/dynamodb)
+- [libSQL Storage](https://mastra.ai/integrations/databases/libsql)
+- [PostgreSQL Storage](https://mastra.ai/integrations/databases/postgresql)
+- [OracleDB Storage](https://mastra.ai/integrations/databases/oracledb)
+- [MongoDB Storage](https://mastra.ai/integrations/databases/mongodb)
+- [Upstash Storage](https://mastra.ai/integrations/databases/upstash)
+- [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1)
+- [DynamoDB](https://mastra.ai/integrations/databases/dynamodb)
 - [More storage providers](https://mastra.ai/docs/storage/overview)
 
 ## Best practices

package/.docs/docs/workflows/time-travel.md

@@ -15,6 +15,8 @@ When you call `timeTravel()` on a workflow run:
 3. Execution begins from the specified step with the provided or reconstructed input data
 4. The workflow continues to completion from that point forward
 
+If the workflow definition has changed since the run was recorded (for example, a step was renamed), or the recorded run never reached a step that precedes the target, time travel fails with a descriptive error before anything executes, and the stored snapshot is left unchanged.
+
 Time travel requires storage to be configured since it relies on persisted workflow snapshots.
 
 ## Basic usage

package/.docs/docs/workspace/filesystem.md

@@ -21,15 +21,15 @@ A filesystem provider handles all file operations for a workspace:
 Available providers:
 
 - [`LocalFilesystem`](https://mastra.ai/reference/workspace/local-filesystem): Stores files in a directory on disk
-- [`S3Filesystem`](https://mastra.ai/reference/workspace/s3-filesystem): Stores files in Amazon S3 or S3-compatible storage (R2, MinIO, Tigris)
-- [`GCSFilesystem`](https://mastra.ai/reference/workspace/gcs-filesystem): Stores files in Google Cloud Storage
+- [`S3Filesystem`](https://mastra.ai/integrations/file-storage/amazon-s3): Stores files in Amazon S3 or S3-compatible storage (R2, MinIO, Tigris)
+- [`GCSFilesystem`](https://mastra.ai/integrations/file-storage/google-cloud-storage): Stores files in Google Cloud Storage
 - [`PlatformFilesystem`](https://mastra.ai/reference/workspace/platform-filesystem): Stores files in a Mastra Platform workspace bucket
-- [`GoogleDriveFilesystem`](https://mastra.ai/reference/workspace/google-drive-filesystem): Stores files inside a Google Drive folder
-- [`AzureBlobFilesystem`](https://mastra.ai/reference/workspace/azure-blob-filesystem): Stores files in Azure Blob Storage
-- [`FilesSDKFilesystem`](https://mastra.ai/reference/workspace/files-sdk-filesystem): Stores files in any [FilesSDK](https://files-sdk.dev) adapter (S3, R2, GCS, Azure Blob, Vercel Blob, local filesystem, and more): useful when you want one provider that can target multiple backends
-- [`AgentFSFilesystem`](https://mastra.ai/reference/workspace/agentfs-filesystem): Stores files in a Turso/SQLite database via AgentFS
-- [`MesaFilesystem`](https://mastra.ai/reference/workspace/mesa-filesystem): Stores files in versioned Mesa repos
-- [`ArchilFilesystem`](https://mastra.ai/reference/workspace/archil-filesystem): Stores files on Archil elastic, serverless disks
+- [`GoogleDriveFilesystem`](https://mastra.ai/integrations/file-storage/google-drive): Stores files inside a Google Drive folder
+- [`AzureBlobFilesystem`](https://mastra.ai/integrations/file-storage/azure-blob): Stores files in Azure Blob Storage
+- [`FilesSDKFilesystem`](https://mastra.ai/integrations/file-storage/vercel-files): Stores files in any [FilesSDK](https://files-sdk.dev) adapter (S3, R2, GCS, Azure Blob, Vercel Blob, local filesystem, and more): useful when you want one provider that can target multiple backends
+- [`AgentFSFilesystem`](https://mastra.ai/integrations/file-storage/agentfs): Stores files in a Turso/SQLite database via AgentFS
+- [`MesaFilesystem`](https://mastra.ai/integrations/file-storage/mesa): Stores files in versioned Mesa repos
+- [`ArchilFilesystem`](https://mastra.ai/integrations/file-storage/archil): Stores files on Archil elastic, serverless disks
 
 > **Tip:** `LocalFilesystem` is the simplest way to get started as it requires no external services. For cloud storage, use `S3Filesystem`, `GCSFilesystem`, or `AzureBlobFilesystem`. For versioned storage, use `MesaFilesystem`. For database-backed storage without external services, use `AgentFSFilesystem`.
 
@@ -227,12 +227,12 @@ When you configure a filesystem on a workspace, agents receive tools for reading
 ## Related
 
 - [LocalFilesystem reference](https://mastra.ai/reference/workspace/local-filesystem)
-- [S3Filesystem reference](https://mastra.ai/reference/workspace/s3-filesystem)
-- [GCSFilesystem reference](https://mastra.ai/reference/workspace/gcs-filesystem)
-- [GoogleDriveFilesystem reference](https://mastra.ai/reference/workspace/google-drive-filesystem)
-- [AzureBlobFilesystem reference](https://mastra.ai/reference/workspace/azure-blob-filesystem)
-- [FilesSDKFilesystem reference](https://mastra.ai/reference/workspace/files-sdk-filesystem)
-- [AgentFSFilesystem reference](https://mastra.ai/reference/workspace/agentfs-filesystem)
-- [MesaFilesystem reference](https://mastra.ai/reference/workspace/mesa-filesystem)
+- [S3Filesystem reference](https://mastra.ai/integrations/file-storage/amazon-s3)
+- [GCSFilesystem reference](https://mastra.ai/integrations/file-storage/google-cloud-storage)
+- [GoogleDriveFilesystem reference](https://mastra.ai/integrations/file-storage/google-drive)
+- [AzureBlobFilesystem reference](https://mastra.ai/integrations/file-storage/azure-blob)
+- [FilesSDKFilesystem reference](https://mastra.ai/integrations/file-storage/vercel-files)
+- [AgentFSFilesystem reference](https://mastra.ai/integrations/file-storage/agentfs)
+- [MesaFilesystem reference](https://mastra.ai/integrations/file-storage/mesa)
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)
 - [Sandbox](https://mastra.ai/docs/workspace/sandbox)

package/.docs/docs/workspace/sandbox.md

@@ -20,17 +20,17 @@ A sandbox provider executes commands in a controlled environment:
 ## Supported providers
 
 - [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox): Executes commands on the local machine
-- [`AgentCoreRuntimeSandbox`](https://mastra.ai/reference/workspace/agentcore-runtime-sandbox): Executes commands in AWS Bedrock AgentCore Runtime sessions
-- [`AppleContainerSandbox`](https://mastra.ai/reference/workspace/apple-container-sandbox): Executes commands in local OCI Linux containers using Apple's `container` CLI
-- [`BlaxelSandbox`](https://mastra.ai/reference/workspace/blaxel-sandbox): Executes commands in isolated Blaxel cloud sandboxes
-- [`DaytonaSandbox`](https://mastra.ai/reference/workspace/daytona-sandbox): Executes commands in isolated Daytona cloud sandboxes
-- [`DockerSandbox`](https://mastra.ai/reference/workspace/docker-sandbox): Executes commands in long-lived Docker containers on the local machine
-- [`E2BSandbox`](https://mastra.ai/reference/workspace/e2b-sandbox): Executes commands in isolated E2B cloud sandboxes
-- [`ModalSandbox`](https://mastra.ai/reference/workspace/modal-sandbox): Executes commands in isolated Modal cloud sandboxes
+- [`AgentCoreRuntimeSandbox`](https://mastra.ai/integrations/sandboxes/agentcore): Executes commands in AWS Bedrock AgentCore Runtime sessions
+- [`AppleContainerSandbox`](https://mastra.ai/integrations/sandboxes/apple-container): Executes commands in local OCI Linux containers using Apple's `container` CLI
+- [`BlaxelSandbox`](https://mastra.ai/integrations/sandboxes/blaxel): Executes commands in isolated Blaxel cloud sandboxes
+- [`DaytonaSandbox`](https://mastra.ai/integrations/sandboxes/daytona): Executes commands in isolated Daytona cloud sandboxes
+- [`DockerSandbox`](https://mastra.ai/integrations/sandboxes/docker): Executes commands in long-lived Docker containers on the local machine
+- [`E2BSandbox`](https://mastra.ai/integrations/sandboxes/e2b): Executes commands in isolated E2B cloud sandboxes
+- [`ModalSandbox`](https://mastra.ai/integrations/sandboxes/modal): Executes commands in isolated Modal cloud sandboxes
 - [`PlatformSandbox`](https://mastra.ai/reference/workspace/platform-sandbox): Executes commands in a sandbox tied to a Mastra Platform environment
-- [`RailwaySandbox`](https://mastra.ai/reference/workspace/railway-sandbox): Executes commands in ephemeral, isolated Railway cloud sandboxes
-- [`VercelSandbox`](https://mastra.ai/reference/workspace/vercel-sandbox): Executes commands in an ephemeral Vercel Sandbox Firecracker MicroVM
-- [`VercelServerlessSandbox`](https://mastra.ai/reference/workspace/vercel-serverless): Executes commands as stateless Vercel serverless functions
+- [`RailwaySandbox`](https://mastra.ai/integrations/sandboxes/railway): Executes commands in ephemeral, isolated Railway cloud sandboxes
+- [`VercelSandbox`](https://mastra.ai/integrations/sandboxes/vercel): Executes commands in an ephemeral Vercel Sandbox Firecracker MicroVM
+- [`VercelServerlessSandbox`](https://mastra.ai/integrations/sandboxes/vercel): Executes commands as stateless Vercel serverless functions
 
 ## Basic usage
 
@@ -234,13 +234,13 @@ Use `null` or `false` for cloud sandboxes (for example, E2B, Daytona, or Modal)
 ## Related
 
 - [`SandboxProcessManager` reference](https://mastra.ai/reference/workspace/process-manager)
-- [`AgentCoreRuntimeSandbox` reference](https://mastra.ai/reference/workspace/agentcore-runtime-sandbox)
-- [`AppleContainerSandbox` reference](https://mastra.ai/reference/workspace/apple-container-sandbox)
-- [`DaytonaSandbox` reference](https://mastra.ai/reference/workspace/daytona-sandbox)
-- [`E2BSandbox` reference](https://mastra.ai/reference/workspace/e2b-sandbox)
+- [`AgentCoreRuntimeSandbox` reference](https://mastra.ai/integrations/sandboxes/agentcore)
+- [`AppleContainerSandbox` reference](https://mastra.ai/integrations/sandboxes/apple-container)
+- [`DaytonaSandbox` reference](https://mastra.ai/integrations/sandboxes/daytona)
+- [`E2BSandbox` reference](https://mastra.ai/integrations/sandboxes/e2b)
 - [`LocalSandbox` reference](https://mastra.ai/reference/workspace/local-sandbox)
-- [`ModalSandbox` reference](https://mastra.ai/reference/workspace/modal-sandbox)
-- [`VercelSandbox` reference](https://mastra.ai/reference/workspace/vercel-sandbox)
-- [`VercelServerlessSandbox` reference](https://mastra.ai/reference/workspace/vercel-serverless)
+- [`ModalSandbox` reference](https://mastra.ai/integrations/sandboxes/modal)
+- [`VercelSandbox` reference](https://mastra.ai/integrations/sandboxes/vercel)
+- [`VercelServerlessSandbox` reference](https://mastra.ai/integrations/sandboxes/vercel)
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)
 - [Filesystem](https://mastra.ai/docs/workspace/filesystem)

package/.docs/docs/workspace/search.md

@@ -280,5 +280,5 @@ When you configure search on a workspace, agents receive tools for searching and
 ## Related
 
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)
-- [RAG overview](https://mastra.ai/guides/rag/overview)
+- [RAG overview](https://mastra.ai/reference/rag/overview)
 - [Workspace class reference](https://mastra.ai/reference/workspace/workspace-class)

package/.docs/guides/agent-frameworks/ai-sdk.md

@@ -4,7 +4,7 @@
 
 If you're already using the [Vercel AI SDK](https://sdk.vercel.ai) directly and want to add Mastra capabilities like [processors](https://mastra.ai/docs/agents/processors) or [memory](https://mastra.ai/docs/memory/memory-processors) without switching to the full Mastra agent API, [`withMastra()`](https://mastra.ai/reference/ai-sdk/with-mastra) lets you wrap any AI SDK model with these features. This is useful when you want to keep your existing AI SDK code but add input/output processing, conversation persistence, or content filtering.
 
-> **Tip:** If you want to use Mastra together with AI SDK UI (e.g. `useChat()`), visit the [AI SDK UI guide](https://mastra.ai/guides/build-your-ui/ai-sdk-ui).
+> **Tip:** If you want to use Mastra together with AI SDK UI (e.g. `useChat()`), visit the [AI SDK UI guide](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui).
 
 ## Installation
 
@@ -139,4 +139,4 @@ const { text } = await generateText({
 - [`withMastra()`](https://mastra.ai/reference/ai-sdk/with-mastra): API reference for `withMastra()`
 - [Processors](https://mastra.ai/docs/agents/processors): Learn about input and output processors
 - [Memory](https://mastra.ai/docs/memory/overview): Overview of Mastra's memory system
-- [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui): Using AI SDK UI hooks with Mastra agents, workflows, and networks
+- [AI SDK UI](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui): Using AI SDK UI hooks with Mastra agents, workflows, and networks

package/.docs/guides/deployment/mastra-workers.md

@@ -4,7 +4,9 @@
 
 Run [Mastra workers](https://mastra.ai/docs/deployment/workers) as separate processes so you can scale orchestration, scheduling, and background tasks independently from the API. This guide walks through a fully split deployment using Docker Compose or Kubernetes.
 
-> **Info:** This guide covers splitting workers into their own containers. If you only need workers to run in-process alongside the API, see [Workers](https://mastra.ai/docs/deployment/workers). No extra setup is required.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
+> **Note:** This guide covers splitting workers into their own containers. If you only need workers to run in-process alongside the API, see [Workers](https://mastra.ai/docs/deployment/workers). No extra setup is required.
 
 ## Before you begin
 
@@ -573,4 +575,4 @@ Workers recover from crashes because the distributed PubSub backend persists una
 - [CLI reference](https://mastra.ai/reference/cli/mastra): `mastra worker build` and `mastra worker start`
 - [PubSub](https://mastra.ai/docs/server/pubsub): Event delivery backends
 - [Deploy a Mastra server](https://mastra.ai/docs/deployment/mastra-server): Build output and server configuration
-- [Deploy Mastra to Kubernetes](https://mastra.ai/guides/deployment/kubernetes): Multi-pod deployment with durable agents
+- [Deploy Mastra to Kubernetes](https://mastra.ai/integrations/deploy/kubernetes): Multi-pod deployment with durable agents

package/.docs/guides/getting-started/quickstart.md

@@ -2,11 +2,11 @@
 
 # Mastra Quickstart
 
-**For AI agents:** Create a new Mastra project non-interactively with `npm create mastra@latest <project-name> -- --llm <provider>`, replacing `<provider>` with `openai`, `anthropic`, `google`, or `xai`. For a minimal project without an agent or model provider, use `npm create mastra@latest <project-name> -- --empty`. To build a Mastra project from scratch, see the [manual installation guide](https://mastra.ai/guides/getting-started/manual-install).
+**For AI agents:** Create a new Mastra project non-interactively with `npm create mastra@latest <project-name> -- --llm <provider>`, replacing `<provider>` with `openai`, `anthropic`, `google`, or `xai`. For a minimal project without an agent or model provider, use `npm create mastra@latest <project-name> -- --empty`. To build a Mastra project from scratch, see the [manual installation guide](https://mastra.ai/reference/manual-install).
 
 The `create-mastra` CLI is the quickest way to start a Mastra project. It creates an agent harness with workspace tools, memory, task tracking, web access, schedules, storage, and observability.
 
-For more control, see the [manual installation guide](https://mastra.ai/guides/getting-started/manual-install). To add Mastra to an existing project, use [`mastra init`](https://mastra.ai/reference/cli/mastra).
+For more control, see the [manual installation guide](https://mastra.ai/reference/manual-install). To add Mastra to an existing project, use [`mastra init`](https://mastra.ai/reference/cli/mastra).
 
 > **📹 Watch:** Watch the [Mastra AI agent course](https://www.youtube.com/watch?v=lCmf_qrGfGA) for a guided introduction to building agents with Mastra.
 
@@ -82,7 +82,7 @@ Open [Studio at localhost:4111](http://localhost:4111), select the agent, and se
 
 ## Next steps
 
-- Integrate Mastra with [Next.js](https://mastra.ai/guides/getting-started/next-js), [React](https://mastra.ai/guides/getting-started/vite-react), or [Astro](https://mastra.ai/guides/getting-started/astro)
+- Integrate Mastra with [Next.js](https://mastra.ai/integrations/frameworks/next-js), [React](https://mastra.ai/integrations/frameworks/vite-react), or [Astro](https://mastra.ai/integrations/frameworks/astro)
 - Learn how to [build Mastra with AI](https://mastra.ai/reference/build-with-ai)
 - Build an agent from scratch with a [guide](https://mastra.ai/guides)
 - Watch the [Mastra YouTube channel](https://www.youtube.com/@mastra-ai)

package/.docs/guides/guide/signal-provider.md

@@ -6,7 +6,7 @@ In this guide, you'll build a signal provider that polls an external service on
 
 The example watches build pipelines in a fake CI service, but the pattern applies to any pull-based source: an issue tracker, a status API, a queue, or your own backend.
 
-> **Beta:** Signal providers are in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 ## Prerequisites
 

package/.docs/guides/index.md

@@ -14,11 +14,11 @@ The `npm create mastra@latest` command is the fastest way to build your first ag
 
 Add Mastra to an existing project, or scaffold a new Mastra-powered app if you’re starting from scratch.
 
-- [Next.js](https://mastra.ai/guides/getting-started/next-js)
-- [React](https://mastra.ai/guides/getting-started/vite-react)
-- [SvelteKit](https://mastra.ai/guides/getting-started/sveltekit)
-- [Astro](https://mastra.ai/guides/getting-started/astro)
-- [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)
+- [Next.js](https://mastra.ai/integrations/frameworks/next-js)
+- [React](https://mastra.ai/integrations/frameworks/vite-react)
+- [SvelteKit](https://mastra.ai/integrations/frameworks/sveltekit)
+- [Astro](https://mastra.ai/integrations/frameworks/astro)
+- [Nuxt](https://mastra.ai/integrations/frameworks/nuxt)
+- [Express](https://mastra.ai/integrations/frameworks/express)
+- [Hono](https://mastra.ai/integrations/frameworks/hono)
+- [Electron](https://mastra.ai/integrations/frameworks/electron)