fix: dark mode colors

Signed-off-by: Richard Gebhardt <[email protected]>

Author: gebhardtr

server/README.md

@@ -39,30 +39,31 @@ The following diagram illustrates the architecture of the MCP Server:
 
 ```mermaid
 sequenceDiagram
-    box hsl(60, 80%, 95%) User Tenancy
-    participant Client
+    subgraph
+        box User Tenancy
+            participant Client
+        end
+        box Service Tenancy
+            participant MCP Server
+            participant IDCS
+        end
+        box OCI
+            participant OCI APIs
+        end
+
+        Client->>MCP Server: Authentication Request
+        MCP Server->>IDCS: Redirect to IDCS Authentication
+        Client->>IDCS: Authenticate
+        IDCS->>Client: Authorization Token
+        Client->>MCP Server: Request with Authorization Token
+        MCP Server->>IDCS: Validate Token
+        IDCS->>MCP Server: Token Validation Response
+        MCP Server->>IDCS: Exchange Token for UPST
+        IDCS->>MCP Server: UPST
+        MCP Server->>OCI APIs: Request with UPST (Token Exchange Signer)
+        OCI APIs->>MCP Server: Response
+        MCP Server->>Client: Response
     end
-    box hsl(60, 80%, 95%) Service Tenancy
-    participant MCP Server
-    participant IDCS
-    end
-
-    box hsl(60, 80%, 95%) OCI
-    participant OCI APIs
-    end
-
-    Client->>MCP Server: Authentication Request
-    MCP Server->>IDCS: Redirect to IDCS Authentication
-    Client->>IDCS: Authenticate
-    IDCS->>Client: Authorization Token
-    Client->>MCP Server: Request with Authorization Token
-    MCP Server->>IDCS: Validate Token
-    IDCS->>MCP Server: Token Validation Response
-    MCP Server->>IDCS: Exchange Token for UPST
-    IDCS->>MCP Server: UPST
-    MCP Server->>OCI APIs: Request with UPST (using Token Exchange Signer)
-    OCI APIs->>MCP Server: Response
-    MCP Server->>Client: Response
 ```
 
 ## License