MCP Server Mesh

MCP Server Mesh is the inventory surface for every MCP server a tenant has registered — as opposed to MCP Server Connection, which is the form that adds or edits one. The root page (/) lists every server as a row: a type badge, name, endpoint, a live tools/resources count pulled by grouping the catalog's tool and resource rows by mcp_server_id, a policy-mode pill (observe, simulate, or enforce), a health dot, and the last discovery sync time. Search and status/type filters narrow the table client-side; there is no server-side pagination today.

Each server's row links to /servers/:id, a dedicated detail page with a graph tab (the server's tools and resources rendered as a filtered slice of the AI Graph), a catalog tab (its tools, resources, tables, and prompts), a policies tab (every published policy attached to the server itself or to one of its tools/resources, bucketed by target), an actors tab (which AI Actors have called through this server), and a decisions tab (the same enforcement-log table used by the standalone Decisions Log, pre-filtered to this server). A "Discover Now" button on the detail page triggers an out-of-cycle discovery pass rather than waiting for the scheduler's next tick.

"Governance state" is read off the server, not computed by this capability: policy mode (observe / simulate / enforce) and health status are both fields on the underlying gcdm_mcp_servers row, written by the policy and health-probe subsystems respectively — the Mesh page just displays them alongside the count of currently-enforcing servers in the page header.