deploy: chore(main): release 0.31.0 (googleapis#2814)

🤖 I have created a release *beep* *boop*
---

##
[0.31.0](googleapis/genai-toolbox@v0.30.0...v0.31.0)
(2026-03-26)

### ⚠ BREAKING CHANGES

* release upgraded docsite
([googleapis#2831](googleapis#2831))
* **http:** sanitize non-2xx error output
([googleapis#2654](googleapis#2654))
* add a new `enable-api` flag
([googleapis#2846](googleapis#2846))
* remove deprecations and update tools-file flag
([googleapis#2806](googleapis#2806))

### Features

* Add a new `enable-api` flag
([googleapis#2846](googleapis#2846))
([7a070da](googleapis@7a070da))
* **auth:** Add generic `authService` type for MCP
([googleapis#2619](googleapis#2619))
([f6678f8](googleapis@f6678f8))
* **auth:** Add Protected Resource Metadata endpoint
([googleapis#2698](googleapis#2698))
([b53dcf2](googleapis@b53dcf2))
* **auth:** Support manual PRM override
([googleapis#2717](googleapis#2717))
([283e4e3](googleapis@283e4e3))
* **dataplex:** Add support for lookup context tool.
([googleapis#2744](googleapis#2744))
([facb69d](googleapis@facb69d))
* Remove deprecations and update tools-file flag
([googleapis#2806](googleapis#2806))
([ab64c95](googleapis@ab64c95))

### Bug Fixes

* **ci:** Remove search index generation from preview deployment
workflow
([googleapis#2859](googleapis#2859))
([f8891b8](googleapis@f8891b8))
* **docs:** Skip empty folders in pagination & reduce PR comment noise
([googleapis#2853](googleapis#2853))
([9ebd93a](googleapis@9ebd93a))
* **http:** Sanitize non-2xx error output
([googleapis#2654](googleapis#2654))
([5bef954](googleapis@5bef954))
* **skills:** Fix integer parameter parsing through agent skills
([googleapis#2847](googleapis#2847))
([4564efe](googleapis@4564efe))

### Documentation

* Release upgraded docsite
([googleapis#2831](googleapis#2831))
([5b25ce0](googleapis@5b25ce0))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Yuan Teoh <45984206+Yuan325@users.noreply.github.com> c6b811c

Author: xiewu

dev/blogs/index.html

@@ -8,4 +8,12 @@ in with the <code>Client ID</code>.</p>
 <h3 id="authorized-invocations">Authorized Invocations</h3>
 <p>When using <a href="https://mcp-toolbox.dev/dev/documentation/configuration/tools/#authorized-invocations">Authorized Invocations</a>, a tool will be
 considered authorized if it has a valid Oauth 2.0 token that matches the Client
-ID.&lt;/p></description></item></channel></rss>
+ID.&lt;/p></description></item><item><title>Generic OIDC Auth</title><link>https://mcp-toolbox.dev/dev/documentation/configuration/authentication/generic/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mcp-toolbox.dev/dev/documentation/configuration/authentication/generic/</guid><description>&lt;h2 id="getting-started">Getting Started&lt;/h2>
+&lt;p>The Generic Auth Service allows you to integrate with any OpenID Connect (OIDC)
+compliant identity provider (IDP). It discovers the JWKS (JSON Web Key Set) URL
+either through the provider&amp;rsquo;s &lt;code>/.well-known/openid-configuration&lt;/code> endpoint or
+directly via the provided &lt;code>authorizationServer&lt;/code>.&lt;/p>
+&lt;p>To configure this auth service, you need to provide the &lt;code>audience&lt;/code> (typically
+your client ID or the intended audience for the token), the
+&lt;code>authorizationServer&lt;/code> of your identity provider, and optionally a list of
+&lt;code>scopesRequired&lt;/code> that must be present in the token&amp;rsquo;s claims.&lt;/p></description></item></channel></rss>

dev/discord/index.html

@@ -1,4 +1,8 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configuration on MCP Toolbox for Databases</title><link>https://mcp-toolbox.dev/dev/documentation/configuration/</link><description>Recent content in Configuration on MCP Toolbox for Databases</description><generator>Hugo</generator><language>en</language><atom:link href="https://mcp-toolbox.dev/dev/documentation/configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>Toolbox UI</title><link>https://mcp-toolbox.dev/dev/documentation/configuration/toolbox-ui/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mcp-toolbox.dev/dev/documentation/configuration/toolbox-ui/</guid><description>&lt;p>Toolbox UI is a built-in web interface that allows users to visually inspect and
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configuration on MCP Toolbox for Databases</title><link>https://mcp-toolbox.dev/dev/documentation/configuration/</link><description>Recent content in Configuration on MCP Toolbox for Databases</description><generator>Hugo</generator><language>en</language><atom:link href="https://mcp-toolbox.dev/dev/documentation/configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>Toolbox with MCP Authorization</title><link>https://mcp-toolbox.dev/dev/documentation/configuration/toolbox_mcp_auth/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mcp-toolbox.dev/dev/documentation/configuration/toolbox_mcp_auth/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
+&lt;p>Toolbox supports integration with Model Context Protocol (MCP) clients by acting as a Resource Server that implements OAuth 2.1 authorization. This enables Toolbox to validate JWT-based Bearer tokens before processing requests for resources or tool executions.&lt;/p>
+&lt;p>This guide details the specific configuration steps required to deploy Toolbox with MCP Auth enabled.&lt;/p>
+&lt;h2 id="step-1-configure-the-generic-auth-service">Step 1: Configure the &lt;code>generic&lt;/code> Auth Service&lt;/h2>
+&lt;p>Update your &lt;code>tools.yaml&lt;/code> file to use a &lt;code>generic&lt;/code> authorization service with &lt;code>mcpEnabled&lt;/code> set to &lt;code>true&lt;/code>. This instructs Toolbox to intercept requests on the &lt;code>/mcp&lt;/code> routes and validate Bearer tokens using the JWKS (JSON Web Key Set) fetched from your OIDC provider endpoint (&lt;code>authorizationServer&lt;/code>).&lt;/p></description></item><item><title>Toolbox UI</title><link>https://mcp-toolbox.dev/dev/documentation/configuration/toolbox-ui/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mcp-toolbox.dev/dev/documentation/configuration/toolbox-ui/</guid><description>&lt;p>Toolbox UI is a built-in web interface that allows users to visually inspect and
 test out configured resources such as tools and toolsets.&lt;/p>
 &lt;h2 id="launching-toolbox-ui">Launching Toolbox UI&lt;/h2>
 &lt;p>To launch Toolbox&amp;rsquo;s interactive UI, use the &lt;code>--ui&lt;/code> flag.&lt;/p>