refactor: Remove manual cache clearing from Keycloak OAuth example

OAuth client now automatically handles stale credentials and re-registers
with Keycloak when needed. Manual cache clearing is no longer required.

Author: stephaneberle9

docs/integrations/keycloak.mdx

@@ -181,28 +181,13 @@ When you run the client for the first time:
 The client caches tokens locally, so you won't need to re-authenticate for subsequent runs unless the token expires or you explicitly clear the cache.
 </Info>
 
-### Troubleshooting: "Client not found" Error
+### Automatic Client Re-registration
 
-<Warning>
-If you restart Keycloak or change the realm configuration, you may end up seeing Keycloak showing a "Client not found" error instead of the login screen when running your client. This happens because FastMCP uses Dynamic Client Registration (DCR) and the client ID that was cached locally no longer exists on the Keycloak server.
-
-**Keycloak error**: "We are sorry... Client not found."
-
-**Solution**: Clear the local OAuth cache to force re-registration with Keycloak:
-
-```python
-from fastmcp.client.auth.oauth import FileTokenStorage
-
-# Clear OAuth cache for your specific MCP server
-storage = FileTokenStorage("http://localhost:8000/mcp/")  # Use your MCP server URL
-storage.clear()
-
-# Or clear all OAuth cache data for all MCP servers
-FileTokenStorage.clear_all()
-```
+<Info>
+If you restart Keycloak or change the realm configuration, your FastMCP client will automatically detect if the cached OAuth client credentials are no longer valid and will re-register with Keycloak automatically. You don't need to manually clear any caches - just run your client again and it will handle the re-registration process seamlessly.
 
-After clearing the cache, run your client again. It will automatically re-register with Keycloak and obtain new credentials.
-</Warning>
+This automatic retry mechanism ensures a smooth developer experience when working with Dynamic Client Registration (DCR).
+</Info>
 
 ## Environment Variables
 

examples/auth/keycloak_auth/client.py

@@ -9,23 +9,11 @@
 import asyncio
 
 from fastmcp import Client
-from fastmcp.client.auth.oauth import FileTokenStorage
 
 SERVER_URL = "http://localhost:8000/mcp"
 
-# Set to True to clear any previously stored tokens.
-# This is useful if you have just restarted Keycloak and end up seeing
-# Keycloak showing this error: "We are sorry... Client not found."
-# instead of the login screen
-CLEAR_TOKEN_CACHE = False
-
 
 async def main():
-    if CLEAR_TOKEN_CACHE:
-        storage = FileTokenStorage(f"{SERVER_URL.rstrip('/')}/")
-        storage.clear()
-        print("🧹 Cleared cached OAuth tokens.")
-
     try:
         async with Client(SERVER_URL, auth="oauth") as client:
             assert await client.ping()

examples/auth/keycloak_auth/keycloak/README.md

@@ -114,18 +114,6 @@ docker-compose logs -f keycloak
    - Review client registration policies in the admin console
 
 4. **"Client not found" error after Keycloak restart**
-   - This happens because FastMCP uses Dynamic Client Registration (DCR) and the client ID that was cached locally no longer exists on the Keycloak server after restart
-   - **Solution**: Clear the local OAuth cache to force re-registration:
-
-     ```python
-     from fastmcp.client.auth.oauth import FileTokenStorage
-
-     # Clear OAuth cache for your specific MCP server
-     storage = FileTokenStorage("http://localhost:8000/mcp/")
-     storage.clear()
-
-     # Or clear all OAuth cache data
-     FileTokenStorage.clear_all()
-     ```
-
-   - After clearing the cache, run your client again to automatically re-register with Keycloak
+   - This can happen when Keycloak is restarted and the previously registered OAuth client no longer exists
+   - **No action needed**: The FastMCP OAuth client automatically detects this condition and re-registers with Keycloak
+   - Simply run your client again and it will automatically handle the re-registration process