Refresh reference assets for toolhive v0.23.1

Author: github-actions[bot]

docs/toolhive/reference/crds/embeddingserver.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `EmbeddingServer` defines a containerized embedding model server managed by the ToolHive operator. The [VirtualMCPServer](./virtualmcpserver.mdx) optimizer references an `EmbeddingServer` to generate vector embeddings for tool discovery.
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `emb`, `embedding`
 
 ## Example
 
 ```yaml title="embeddingserver.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: EmbeddingServer
 metadata:
   name: my-embeddingserver

docs/toolhive/reference/crds/mcpexternalauthconfig.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPExternalAuthConfig` configures how an MCP server or proxy authenticates to external services via token exchange or an embedded authorization server. It is referenced by [MCPServer](./mcpserver.mdx), [MCPRemoteProxy](./mcpremoteproxy.mdx), [MCPServerEntry](./mcpserverentry.mdx), and [VirtualMCPServer](./virtualmcpserver.mdx).
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `extauth`, `mcpextauth`
 
 ## Example
 
 ```yaml title="mcpexternalauthconfig.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPExternalAuthConfig
 metadata:
   name: my-mcpexternalauthconfig

docs/toolhive/reference/crds/mcpgroup.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPGroup` is a grouping construct for backend workloads. Other resources reference an `MCPGroup` by name to join a shared pool - for example, a [VirtualMCPServer](./virtualmcpserver.mdx) aggregates the tools exposed by every member of its referenced group.
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `mcpg`, `mcpgroup`
 
 ## Example
 
 ```yaml title="mcpgroup.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPGroup
 metadata:
   name: my-mcpgroup

docs/toolhive/reference/crds/mcpoidcconfig.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPOIDCConfig` defines OIDC authentication settings that can be shared across multiple MCP workloads. [MCPServer](./mcpserver.mdx), [MCPRemoteProxy](./mcpremoteproxy.mdx), and [VirtualMCPServer](./virtualmcpserver.mdx) reference an `MCPOIDCConfig` via `spec.oidcConfigRef` to validate incoming tokens.
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `mcpoidc`
 
 ## Example
 
 ```yaml title="mcpoidcconfig.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPOIDCConfig
 metadata:
   name: my-mcpoidcconfig

docs/toolhive/reference/crds/mcpregistry.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPRegistry` deploys a [ToolHive Registry Server](../../guides-registry/intro.mdx) in the cluster. The operator watches `MCPRegistry` resources and provisions the Registry Server, its PostgreSQL backing, and the configured sources (Git, ConfigMap, URL, or Kubernetes discovery) that populate its catalog of MCP server definitions.
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `mcpreg`, `registry`
 
 ## Example
 
 ```yaml title="mcpregistry.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPRegistry
 metadata:
   name: my-mcpregistry

docs/toolhive/reference/crds/mcpremoteproxy.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPRemoteProxy` fronts a remote MCP server (reachable over HTTPS) with the same authentication, telemetry, and tool-filtering features that the operator applies to containerized servers. Use this when you want to apply ToolHive policies to a third-party hosted MCP endpoint.
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `rp`, `mcprp`
 
 ## Example
 
 ```yaml title="mcpremoteproxy.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPRemoteProxy
 metadata:
   name: my-mcpremoteproxy

docs/toolhive/reference/crds/mcpserver.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPServer` defines a containerized MCP server managed by the ToolHive Kubernetes operator. The operator watches `MCPServer` resources and reconciles them into a running, proxied MCP server with the configured transport, authentication, telemetry, and tool filtering.
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `mcpserver`, `mcpservers`
 
 ## Example
 
 ```yaml title="mcpserver.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPServer
 metadata:
   name: my-mcpserver

docs/toolhive/reference/crds/mcpserverentry.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPServerEntry` declares a remote MCP server as a first-class member of an [MCPGroup](./mcpgroup.mdx) without running a full [MCPRemoteProxy](./mcpremoteproxy.mdx). Entries appear in registry listings and participate in group-scoped aggregations like a [VirtualMCPServer](./virtualmcpserver.mdx).
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `mcpentry`
 
 ## Example
 
 ```yaml title="mcpserverentry.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPServerEntry
 metadata:
   name: my-mcpserverentry

docs/toolhive/reference/crds/mcptelemetryconfig.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPTelemetryConfig` defines telemetry settings that can be shared across multiple MCP workloads. [MCPServer](./mcpserver.mdx), [MCPRemoteProxy](./mcpremoteproxy.mdx), and [VirtualMCPServer](./virtualmcpserver.mdx) reference a single `MCPTelemetryConfig` to emit traces and metrics to a common backend.
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `mcpotel`
 
 ## Example
 
 ```yaml title="mcptelemetryconfig.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPTelemetryConfig
 metadata:
   name: my-mcptelemetryconfig

docs/toolhive/reference/crds/mcptoolconfig.mdx

@@ -8,13 +8,13 @@ toc_max_heading_level: 4
 
 `MCPToolConfig` defines tool-filtering and renaming rules that can be shared across MCP workloads. [MCPServer](./mcpserver.mdx), [MCPRemoteProxy](./mcpremoteproxy.mdx), and [VirtualMCPServer](./virtualmcpserver.mdx) reference an `MCPToolConfig` via `spec.toolConfigRef` to customize the tool surface their clients see.
 
-**API:** `toolhive.stacklok.dev/v1alpha1`
+**API:** `toolhive.stacklok.dev/v1beta1`
  · **Scope:** Namespaced · **Short names:** `tc`, `toolconfig`
 
 ## Example
 
 ```yaml title="mcptoolconfig.yaml"
-apiVersion: toolhive.stacklok.dev/v1alpha1
+apiVersion: toolhive.stacklok.dev/v1beta1
 kind: MCPToolConfig
 metadata:
   name: my-mcptoolconfig