mcp-create-adaptive-cards

Generates ANT-style UTM-safe templates for ITSM ticketing systems.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill mcp-create-adaptive-cards-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-create-adaptive-cards
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/mcp-create-adaptive-cards
Command: npx skills add https://github.com/selfagency/agentsy --skill mcp-create-adaptive-cards-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams make Microsoft 365 Copilot responses easier to understand by converting raw MCP API output into Adaptive Card visuals instead of plain JSON or text.

Core Features & Use Cases

  • Static template generation: Define a single Adaptive Card layout for APIs that return a consistent item shape, using response_semantics.static_template in ai-plugin.json.
  • Dynamic template generation: Select different Adaptive Card templates per item via a template_selector field (for mixed result types) with embedded card templates in the API payload.
  • Template fallback behavior: Combine static and dynamic approaches so the card still renders using a default template when selector data is missing or cannot be resolved.
  • Copilot citation mapping: Configure data_path and properties so the right fields map to titles/subtitles/links used by citations.

Quick Start

Create an ai-plugin.json response_semantics block that sets data_path, defines properties, and adds either a static_template or a template_selector with per-item embedded templates.

Frequently Asked Questions about mcp-create-adaptive-cards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I render MCP API results as Adaptive Cards in Microsoft 365 Copilot?

To render MCP API results as Adaptive Cards, configure the `response_semantics` block in `ai-plugin.json` with `data_path`, `properties`, and either a `static_template` or `template_selector` to generate structured visuals instead of raw JSON.

What is the difference between static and dynamic Adaptive Card templates for Copilot plugins?

Static Adaptive Card templates apply a single layout for consistent item shapes, while dynamic templates use a `template_selector` field to render different card layouts per item based on mixed result types in the API payload.

How do I handle missing selector fields when generating dynamic Adaptive Cards?

Handle missing selector fields by combining static and dynamic approaches to enable template fallback behavior, allowing the card to render using a default static template when selector data is missing or cannot be resolved.

How do I map Copilot citations to fields in an MCP API response?

Map Copilot citations by configuring `data_path` and `properties` within the `response_semantics` block of `ai-plugin.json`, ensuring the correct API fields map to titles, subtitles, and links used by citations.

Can I use Adaptive Card template-language bindings for conditional formatting in Copilot response templates?

Yes, Adaptive Card template-language bindings support conditional rendering and formatting within `static_template` and `template_selector` configurations, enabling dynamic visual adjustments for MCP-based API plugin responses.

What response_semantics configuration is required for MCP-based Adaptive Card templates?

Required `response_semantics` configuration includes `data_path` for locating results, `properties` for field mapping, and either `static_template` or `template_selector` with embedded card templates for visual rendering in Copilot.