[MCP] Update Mcp Documents and Images (#21720)

* Update documentation

* Updated documentation

* Update Documentation

* doc change

* update description

* again try something

* update

* Update to "MCP Server"

openmetadata-service/src/main/resources/json/data/app/McpApplication.json

@@ -1,6 +1,6 @@
 {
   "name": "McpApplication",
-  "displayName": "MCP Application",
+  "displayName": "MCP Server",
   "appConfiguration": {
     "originValidationEnabled": false,
     "originHeaderUri": "http://localhost"

openmetadata-service/src/main/resources/json/data/appMarketPlaceDefinition/McpApplication.json

@@ -1,7 +1,7 @@
 {
   "name": "McpApplication",
-  "displayName": "MCP Application",
-  "description": "MCP Application for OpenMetadata.",
+  "displayName": "MCP Server",
+  "description": "MCP Server for OpenMetadata.",
   "features": "Sets up a embedded server for MCP (Metadata Collection Protocol) to interact with OpenMetadata via SSE/Streamable-Http transport.",
   "appType": "internal",
   "appScreenshots": ["McpApplication.png"],

openmetadata-ui/src/main/resources/ui/public/locales/en-US/Applications/McpApplication.md

@@ -1,11 +1,14 @@
-# MCP Application
+# MCP Server
 
-MCP Application installs an embedded MCP Server with OpenMetadata. Clients supporting MCP Protocol can connect using SSE or Streamable-Http transports.For different transports the client can use the following endpoints:
-For different transports the client can use the following endpoints:
-1. SSE : http[s]://<openmetadata-host>/mcp/sse 
-   - This endpoint can be used by client if Streamable-Http transport is used.  
-2. Streamable-Http : http[s]://<openmetadata-host>/mcp 
-   - This endpoint can be used by client if Streamable-Http transport is used.
+MCP Server app installs an embedded Model Context Protocol(MCP) server within OpenMetadata. Clients supporting MCP Protocol can connect using SSE or Streamable-Http transports.
+ 
+   1. SSE : http[s]://openmetadata-host/mcp/sse
+ 
+    - This endpoint can be used by client if Streamable-Http transport is used.
+ 
+   2. Streamable-Http : http[s]://openmetadata-host/mcp
+ 
+    - This endpoint can be used by client if Streamable-Http transport is used.
 
 $$section
 ### Should Origin Header Be validated $(id="originValidationEnabled")

openmetadata-ui/src/main/resources/ui/src/utils/ApplicationSchemas/McpApplication.json

@@ -1,16 +1,18 @@
 {
   "$id": "McpApplication.json",
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "MCP Application",
-  "description": "This schema defines configuration for MCP Application.",
+  "title": "MCP Server",
+  "description": "MCP Server app installs an embedded Model Context Protocol(MCP) server within OpenMetadata. Clients supporting MCP Protocol can connect using SSE or Streamable-Http transports.\n \n   1. SSE : http[s]://openmetadata-host/mcp/sse\n \n    - This endpoint can be used by client if Streamable-Http transport is used.\n \n   2. Streamable-Http : http[s]://openmetadata-host/mcp\n \n    - This endpoint can be used by client if Streamable-Http transport is used.",
   "properties": {
     "originValidationEnabled": {
       "title": "Should Origin Header Be validated",
+      "description": "When enabled, clients must include a valid Origin header when connecting via Streamable-Http transport. This prevents unauthorized cross-origin requests.",
       "type": "boolean",
       "default": false
     },
     "originHeaderUri": {
       "title": "Origin Header URI",
+      "description": "The allowed origin URI that clients must include in their Origin header when validation is enabled. Only requests from this URI will be accepted.\nExample: `https://myapp.example.com`",
       "type": "string",
       "default": "http://localhost"
     }