Add dedicated Operator guide page for MCPServerEntry (#701)

* Add dedicated Operator guide page for MCPServerEntry

Closes #688

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Address review feedback

- Add MCPServerEntry to intro.mdx opening paragraph (#1)
- Link all four resource types in intro.mdx table (#2)
- Include MCPServerEntry in discovered-to-inline RBAC note (#3)
- Move MCPRemoteProxy link from Next steps to Related info (#4)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Update docs/toolhive/guides-k8s/intro.mdx

Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>

* Update docs/toolhive/guides-k8s/mcp-server-entry.mdx

Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>

* Update docs/toolhive/guides-k8s/mcp-server-entry.mdx

Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>

* Update docs/toolhive/guides-k8s/mcp-server-entry.mdx

Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>

* Update docs/toolhive/guides-k8s/mcp-server-entry.mdx

Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>

* Address PR review comments

- Fix backend-discovery.mdx "Backend conversion" to say endpoint URL
  instead of service URL, since MCPServerEntry uses remoteURL (#1)
- Link MCPExternalAuthConfig to token-exchange-k8s.mdx instead of
  embedded auth server section (#2)
- Clarify complete example wording re: CA bundle ConfigMap (#3)
- Remove resource table links in intro.mdx per reviewer preference (#4)
- Add Telemetry row to comparison table (#5)
- Fix step numbering in "What's happening?" admonition (#6, #7)
- Fix TLS and header code blocks to use highlight comments (#8, #9)
- Fix broken duplicate header code block from bad merge

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Dan Barr <danbarr@users.noreply.github.com>

Author: 3 people

docs/toolhive/guides-k8s/intro.mdx

@@ -22,8 +22,9 @@ The operator introduces new Custom Resource Definitions (CRDs) into your
 Kubernetes cluster. The primary CRDs for MCP server workloads are `MCPServer`,
 which represents a single MCP server running in Kubernetes, `MCPRemoteProxy`,
 which represents an MCP server hosted outside the cluster that ToolHive proxies,
-`VirtualMCPServer`, which aggregates multiple backend MCP servers behind a
-single endpoint.
+`MCPServerEntry`, which registers a remote MCP server as a catalog entry for
+vMCP discovery, and `VirtualMCPServer`, which aggregates multiple backend MCP
+servers behind a single endpoint.
 
 All ToolHive CRDs are registered under the `toolhive` category, so you can list
 every ToolHive resource in your cluster with a single command:
@@ -102,4 +103,5 @@ Once the operator is installed, you can create and manage MCP servers:
 
 - [Run MCP servers in Kubernetes](./run-mcp-k8s.mdx)
 - [Proxy remote MCP servers](./remote-mcp-proxy.mdx)
+- [Declare remote MCP server entries](./mcp-server-entry.mdx)
 - [Virtual MCP Server (vMCP)](../guides-vmcp/index.mdx)