docs: complete PR #620 sync with advanced handler config

Add remaining documentation for PR #620:
- Document createMcpHandler advanced configuration options (authContext, transport, corsOptions, route)
- Add cross-reference from hibernation section to persistent transport state
- Add MCP elicitation example reference in remote-mcp-server guide

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: github-actions[bot]

src/content/docs/agents/guides/remote-mcp-server.mdx

@@ -256,6 +256,16 @@ npm run deploy
 
 Now that you've added the ID and secret of your production OAuth app, you should now be able to connect to your MCP server running at `worker-name.account-name.workers.dev/sse` using the [AI Playground](https://playground.ai.cloudflare.com/), MCP inspector or ([other MCP clients](/agents/guides/remote-mcp-server/#connect-your-mcp-server-to-claude-and-other-mcp-clients)), and authenticate with GitHub.
 
+## Example: MCP Elicitation
+
+Want to see MCP user elicitation in action? Check out the [MCP Elicitation guide](/agents/guides/mcp-elicitation/) which demonstrates how to build an MCP server that uses the elicitation API to request user input during tool execution. This example shows how to:
+
+- Request user confirmation before executing actions
+- Collect structured data from users via forms
+- Handle elicitation responses following the MCP specification
+
+The elicitation feature allows your MCP tools to pause execution and ask users for additional information or confirmation, creating more interactive and controlled agent experiences.
+
 ## Next steps
 
 - Add [tools](/agents/model-context-protocol/tools/) to your MCP server.

src/content/docs/agents/model-context-protocol/mcp-agent-api.mdx

@@ -53,6 +53,8 @@ You can use the APIs below in order to do so.
 
 Hibernation is enabled by default and requires no additional configuration.
 
+For advanced use cases where you need to persist MCP transport state (session ID, initialization status, protocol version) across hibernation cycles, you can use the `storage` option when creating a `WorkerTransport`. See [Persistent transport state](/agents/model-context-protocol/transport/#persistent-transport-state) for details.
+
 #### Authentication & Authorization
 
 The McpAgent class provides seamless integration with the [OAuth Provider Library](https://github.com/cloudflare/workers-oauth-provider) for [authentication and authorization](/agents/model-context-protocol/authorization/). 

src/content/docs/agents/model-context-protocol/transport.mdx

@@ -163,6 +163,46 @@ The `TransportState` type includes:
 If you're using `McpAgent`, transport state is automatically managed for you. The persistent storage API is primarily useful for stateless MCP servers using `createMcpHandler` directly.
 :::
 
+## Advanced handler configuration
+
+The `createMcpHandler` function accepts optional configuration to customize how MCP requests are handled:
+
+```ts
+import { createMcpHandler, WorkerTransport } from "agents/mcp";
+
+const handler = createMcpHandler(server, {
+  // Optional: Provide authentication context explicitly
+  authContext: {
+    props: { userId: "123", role: "admin" }
+  },
+
+  // Optional: Provide a custom transport instance
+  transport: new WorkerTransport({
+    sessionIdGenerator: () => crypto.randomUUID(),
+    storage: { /* ... */ }
+  }),
+
+  // Optional: Customize CORS settings
+  corsOptions: {
+    allowedOrigins: ["https://example.com"],
+    allowedMethods: ["GET", "POST"]
+  },
+
+  // Optional: Specify the route path (defaults to handler for all paths)
+  route: "/mcp"
+});
+```
+
+### Configuration options
+
+- **`authContext`**: Explicitly provide authentication information (user identity, tokens, etc.) to be made available in tool handlers via `getMcpAuthContext()`. If not provided, the handler will automatically use authentication data from `ctx.props` if available.
+
+- **`transport`**: Supply a custom `WorkerTransport` instance. This is useful when you need to configure transport settings (like storage persistence) or reuse a transport across multiple requests. If not provided, a new transport is created for each handler.
+
+- **`corsOptions`**: Configure Cross-Origin Resource Sharing (CORS) settings for your MCP server. Useful when your MCP server needs to be accessed from web applications hosted on different domains.
+
+- **`route`**: Specify the URL path that this handler should respond to. If not provided, the handler will process all requests.
+
 ### Testing with MCP clients
 While most MCP clients have not yet adopted the new Streamable HTTP transport, you can start testing it today using [`mcp-remote`](https://www.npmjs.com/package/mcp-remote), an adapter that lets MCP clients that otherwise only support local connections work with remote MCP servers.