Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP CU Chat Server render the CU field schema"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A local MCP (Model Context Protocol) server that renders Azure Content Understanding (CU) field schema as an interactive table card directly inside VS Code Chat, using the MCP Apps extension (SEP-1865).
Renders CU field schema as a CU Studio–style table: Value Type / Method dropdowns, Source & Confidence checkbox, header info icons, truncated descriptions.
Interactive: edit a field's description in the card; the edit is persisted back to the
server (via callServerTool) and survives re-renders.
Self-contained MCP App HTML bundle (esbuild), served over stdio.
Related MCP server: Storyblok MCP
server.mjs — MCP server: tool + UI resource registration, in-memory persistence.
view/main.mjs — View logic: table rendering, editing, pulling latest from server.
view/template.html — View HTML skeleton + styles.
build.mjs — esbuild script that bundles the View into dist/mcp-app.html.
data/sample-field-schema.json — sample CU field schema (13 fields).
test-smoke.mjs — smoke test that verifies the MCP protocol without VS Code.
npm install
npm run buildAdd to your user mcp.json (Command Palette → "MCP: Open User Configuration"):
{
"servers": {
"cu-schema-viewer": {
"type": "stdio",
"command": "node",
"args": ["<absolute-path>/server.mjs"]
}
}
}Restart the server (Command Palette → "MCP: List Servers" → cu-schema-viewer → Restart),
then in Agent mode invoke the render_cu_schema tool.
render_cu_schema — render the CU field schema table.
schemaPath (optional): absolute path to a JSON file with fieldSchema.fields.
fieldSchema (optional): inline fieldSchema object.
update_field_description (UI-only) — persists an edited field description.
ui:// authority must equal the server nameVS Code routes UI resource requests by the authority segment of the ui:// URI. It
must equal the server name in mcp.json, otherwise VS Code never sends resources/read
and the card won't render (you only get text output). This server uses
ui://cu-schema-viewer/schema to match the server name cu-schema-viewer.
Render CU field schema as a right-side style table in VS Code Chat
Inputs: schemaPath, fieldSchema.
Persist an edited CU field description (called by the UI panel).
Inputs: fieldName (required), description (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have clearly distinct purposes: one renders a schema table, the other persists a field description edit. There is no ambiguity or overlap.
Both tool names follow a consistent verb_noun pattern using snake_case (render_cu_schema, update_field_description), making them predictable and readable.
With only 2 tools, the set feels thin for a server named 'MCP CU Chat Server,' which implies broader functionality. The scope is borderline minimal.
The tools cover only rendering and updating a field description, leaving out essential operations like creating, deleting, or listing fields. This is a significant gap for CU schema management.
An agent-native database over MCP: shared, validated, structured records in every AI chat.
Astra DB tools for agents: schema, find, vector search, guarded writes, and interactive views.
Create, read, update and delete your data lake with simple prompts. Share tables by row and column.
Shared tables and Markdown docs for teams and AI-built apps, with scoped access and audited changes.
