mcp-create-adaptive-cards

Generate Adaptive Card response templates for MCP-based API plugins.

1|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/interserver/teams-chat-bot --skill mcp-create-adaptive-cards-interserver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-create-adaptive-cards
Source: https://github.com/interserver/teams-chat-bot/tree/main/.claude/skills/mcp-create-adaptive-cards
Command: npx skills add https://github.com/interserver/teams-chat-bot --skill mcp-create-adaptive-cards-interserver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help developers present structured API data in Microsoft 365 Copilot by converting raw JSON responses into clear, consistent Adaptive Card UI.

Core Features & Use Cases

  • Static response templates: Define one Adaptive Card layout for a stable item shape using response_semantics.static_template.
  • Dynamic response templates: Select different Adaptive Card layouts per item using a template_selector property (and templates embedded in the API payload).
  • Combined patterns: Use a default static template when no template selector exists, while still supporting per-item dynamic rendering.
  • Use case: When an MCP-based API returns a list of records (e.g., projects, transactions, tickets), generate visually scannable cards with facts, conditional fields, and actions like OpenUrl for drill-down.

Quick Start

Use the mcp-create-adaptive-cards skill to generate an ai-plugin.json response_semantics section (data_path, properties, static_template, and optional template_selector) for your MCP function so Copilot renders your API results as Responsive Adaptive Cards.

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 generate Adaptive Card templates for Microsoft 365 Copilot API responses?▼

Generate Adaptive Card templates for Microsoft 365 Copilot by defining the ai-plugin.json response_semantics section, mapping data_path and properties to create static or dynamic card layouts from JSON API results.

What is response_semantics in ai-plugin.json for MCP plugins?▼

Response_semantics in ai-plugin.json is the configuration block that binds MCP API JSON results to Adaptive Card UI, specifying data_path, properties, static_template, and optional template_selector for Copilot rendering.

How do I use a template_selector for dynamic Adaptive Card layouts per item?▼

Use a template_selector property to dynamically select different Adaptive Card layouts per item, embedding multiple templates in the API payload so Copilot renders each record with its matching card design.

Can I combine static and dynamic Adaptive Card templates for my MCP API?▼

Combine static and dynamic Adaptive Card templates by defining a default static_template for consistent records while supporting a template_selector for per-item dynamic rendering when custom layouts are needed.

Does Microsoft 365 Copilot support conditional rendering and actions in Adaptive Cards?▼

Microsoft 365 Copilot supports conditional rendering, formatting, and optional action elements like OpenUrl for drill-down in Adaptive Cards through binding expressions defined in your response_semantics properties.

Why are my MCP API results displaying as raw JSON in Copilot instead of cards?▼

MCP API results display as raw JSON when the ai-plugin.json response_semantics block lacks proper data_path, properties mapping, and static_template definitions required to render Adaptive Card layouts in Copilot.