
Mcp Create Adaptive Cards
- 8.7k installs
- 37.1k repo stars
- Updated July 28, 2026
- github/awesome-copilot
mcp-create-adaptive-cards is an agent skill that Skill converted from mcp-create-adaptive-cards.prompt.md.
About
Skill converted from mcp-create-adaptive-cards prompt md name mcp-create-adaptive-cards description Skill converted from mcp-create-adaptive-cards prompt md prompt mode agent tools changes search codebase edit editFiles problems description Add Adaptive Card response templates to MCP-based API plugins for visual data presentation in Microsoft 365 Copilot model gpt-4 1 tags mcp adaptive-cards m365-copilot api-plugin response-templates Create Adaptive Cards for MCP Plugins Add Adaptive Card response templates to MCP-based API plugins to enhance how data is presented visually in Microsoft 365 Copilot Adaptive Card Types Static Response Templates Use when API always returns items of the same type and format doesn't change often Define in response_semantics static_template in ai-plugin json json functions name GetBudgets description Returns budget details including name and available funds capabilities response_semantics data_path properties title name subtitle availableFunds static_template type AdaptiveCard schema http adaptivecards io schemas adaptive-card json version 1 5 body type Container data root items type TextBlock text Name if name name N A wrap true type TextBlock text Ava.
- Create Adaptive Cards for MCP Plugins
- Use single columns for narrow viewports
- Avoid multi-column layouts when possible
- Ensure cards work at minimum viewport width
- Don't assign fixed widths to elements
Mcp Create Adaptive Cards by the numbers
- 8,652 all-time installs (skills.sh)
- +22 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #159 of 2,184 Testing & QA skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
mcp-create-adaptive-cards capabilities & compatibility
- Capabilities
- create adaptive cards for mcp plugins · use single columns for narrow viewports · avoid multi column layouts when possible · ensure cards work at minimum viewport width · don't assign fixed widths to elements
- Use cases
- documentation
What mcp-create-adaptive-cards says it does
## Adaptive Card Types ### Static Response Templates Use when API always returns items of the same type and format doesn't change often.
] }, { "type": "Column", "width": "stretch", "items": [ ...
Are all items the same type (static) or different types (dynamic)?
Should there be actions (e.g., "View Details")?
npx skills add https://github.com/github/awesome-copilot --skill mcp-create-adaptive-cardsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 8.7k |
|---|---|
| repo stars | ★ 37.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | github/awesome-copilot ↗ |
What problem does mcp-create-adaptive-cards solve for developers using this skill?
Skill converted from mcp-create-adaptive-cards.prompt.md
Who is it for?
Developers who need mcp-create-adaptive-cards patterns described in the cached skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill's documented scope.
When should I use this skill?
Skill converted from mcp-create-adaptive-cards.prompt.md
What you get
Actionable workflows and conventions from SKILL.md for mcp-create-adaptive-cards.
- Adaptive Card JSON templates
- updated plugin response mappings
By the numbers
- Covers static and dynamic Adaptive Card response template types
Files
````prompt --- mode: 'agent' tools: ['changes', 'search/codebase', 'edit/editFiles', 'problems'] description: 'Add Adaptive Card response templates to MCP-based API plugins for visual data presentation in Microsoft 365 Copilot' model: 'gpt-4.1' tags: [mcp, adaptive-cards, m365-copilot, api-plugin, response-templates] ---
Create Adaptive Cards for MCP Plugins
Add Adaptive Card response templates to MCP-based API plugins to enhance how data is presented visually in Microsoft 365 Copilot.
Adaptive Card Types
Static Response Templates
Use when API always returns items of the same type and format doesn't change often.
Define in response_semantics.static_template in ai-plugin.json:
{
"functions": [
{
"name": "GetBudgets",
"description": "Returns budget details including name and available funds",
"capabilities": {
"response_semantics": {
"data_path": "$",
"properties": {
"title": "$.name",
"subtitle": "$.availableFunds"
},
"static_template": {
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.5",
"body": [
{
"type": "Container",
"$data": "${$root}",
"items": [
{
"type": "TextBlock",
"text": "Name: ${if(name, name, 'N/A')}",
"wrap": true
},
{
"type": "TextBlock",
"text": "Available funds: ${if(availableFunds, formatNumber(availableFunds, 2), 'N/A')}",
"wrap": true
}
]
}
]
}
}
}
}
]
}Dynamic Response Templates
Use when API returns multiple types and each item needs a different template.
ai-plugin.json configuration:
{
"name": "GetTransactions",
"description": "Returns transaction details with dynamic templates",
"capabilities": {
"response_semantics": {
"data_path": "$.transactions",
"properties": {
"template_selector": "$.displayTemplate"
}
}
}
}API Response with Embedded Templates:
{
"transactions": [
{
"budgetName": "Fourth Coffee lobby renovation",
"amount": -2000,
"description": "Property survey for permit application",
"expenseCategory": "permits",
"displayTemplate": "$.templates.debit"
},
{
"budgetName": "Fourth Coffee lobby renovation",
"amount": 5000,
"description": "Additional funds to cover cost overruns",
"expenseCategory": null,
"displayTemplate": "$.templates.credit"
}
],
"templates": {
"debit": {
"type": "AdaptiveCard",
"version": "1.5",
"body": [
{
"type": "TextBlock",
"size": "medium",
"weight": "bolder",
"color": "attention",
"text": "Debit"
},
{
"type": "FactSet",
"facts": [
{
"title": "Budget",
"value": "${budgetName}"
},
{
"title": "Amount",
"value": "${formatNumber(amount, 2)}"
},
{
"title": "Category",
"value": "${if(expenseCategory, expenseCategory, 'N/A')}"
},
{
"title": "Description",
"value": "${if(description, description, 'N/A')}"
}
]
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json"
},
"credit": {
"type": "AdaptiveCard",
"version": "1.5",
"body": [
{
"type": "TextBlock",
"size": "medium",
"weight": "bolder",
"color": "good",
"text": "Credit"
},
{
"type": "FactSet",
"facts": [
{
"title": "Budget",
"value": "${budgetName}"
},
{
"title": "Amount",
"value": "${formatNumber(amount, 2)}"
},
{
"title": "Description",
"value": "${if(description, description, 'N/A')}"
}
]
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json"
}
}
}Combined Static and Dynamic Templates
Use static template as default when item doesn't have template_selector or when value doesn't resolve.
{
"capabilities": {
"response_semantics": {
"data_path": "$.items",
"properties": {
"title": "$.name",
"template_selector": "$.templateId"
},
"static_template": {
"type": "AdaptiveCard",
"version": "1.5",
"body": [
{
"type": "TextBlock",
"text": "Default: ${name}",
"wrap": true
}
]
}
}
}
}Response Semantics Properties
data_path
JSONPath query indicating where data resides in API response:
"data_path": "$" // Root of response
"data_path": "$.results" // In results property
"data_path": "$.data.items"// Nested pathproperties
Map response fields for Copilot citations:
"properties": {
"title": "$.name", // Citation title
"subtitle": "$.description", // Citation subtitle
"url": "$.link" // Citation link
}template_selector
Property on each item indicating which template to use:
"template_selector": "$.displayTemplate"Adaptive Card Template Language
Conditional Rendering
{
"type": "TextBlock",
"text": "${if(field, field, 'N/A')}" // Show field or 'N/A'
}Number Formatting
{
"type": "TextBlock",
"text": "${formatNumber(amount, 2)}" // Two decimal places
}Data Binding
{
"type": "Container",
"$data": "${$root}", // Break to root context
"items": [ ... ]
}Conditional Display
{
"type": "Image",
"url": "${imageUrl}",
"$when": "${imageUrl != null}" // Only show if imageUrl exists
}Card Elements
TextBlock
{
"type": "TextBlock",
"text": "Text content",
"size": "medium", // small, default, medium, large, extraLarge
"weight": "bolder", // lighter, default, bolder
"color": "attention", // default, dark, light, accent, good, warning, attention
"wrap": true
}FactSet
{
"type": "FactSet",
"facts": [
{
"title": "Label",
"value": "Value"
}
]
}Image
{
"type": "Image",
"url": "https://example.com/image.png",
"size": "medium", // auto, stretch, small, medium, large
"style": "default" // default, person
}Container
{
"type": "Container",
"$data": "${items}", // Iterate over array
"items": [
{
"type": "TextBlock",
"text": "${name}"
}
]
}ColumnSet
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": "auto",
"items": [ ... ]
},
{
"type": "Column",
"width": "stretch",
"items": [ ... ]
}
]
}Actions
{
"type": "Action.OpenUrl",
"title": "View Details",
"url": "https://example.com/item/${id}"
}Responsive Design Best Practices
Single-Column Layouts
- Use single columns for narrow viewports
- Avoid multi-column layouts when possible
- Ensure cards work at minimum viewport width
Flexible Widths
- Don't assign fixed widths to elements
- Use "auto" or "stretch" for width properties
- Allow elements to resize with viewport
- Fixed widths OK for icons/avatars only
Text and Images
- Avoid placing text and images in same row
- Exception: Small icons or avatars
- Use "wrap": true for text content
- Test at various viewport widths
Test Across Hubs
Validate cards in:
- Teams (desktop and mobile)
- Word
- PowerPoint
- Various viewport widths (contract/expand UI)
Complete Example
ai-plugin.json:
{
"functions": [
{
"name": "SearchProjects",
"description": "Search for projects with status and details",
"capabilities": {
"response_semantics": {
"data_path": "$.projects",
"properties": {
"title": "$.name",
"subtitle": "$.status",
"url": "$.projectUrl"
},
"static_template": {
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.5",
"body": [
{
"type": "Container",
"$data": "${$root}",
"items": [
{
"type": "TextBlock",
"size": "medium",
"weight": "bolder",
"text": "${if(name, name, 'Untitled Project')}",
"wrap": true
},
{
"type": "FactSet",
"facts": [
{
"title": "Status",
"value": "${status}"
},
{
"title": "Owner",
"value": "${if(owner, owner, 'Unassigned')}"
},
{
"title": "Due Date",
"value": "${if(dueDate, dueDate, 'Not set')}"
},
{
"title": "Budget",
"value": "${if(budget, formatNumber(budget, 2), 'N/A')}"
}
]
},
{
"type": "TextBlock",
"text": "${if(description, description, 'No description')}",
"wrap": true,
"separator": true
}
]
}
],
"actions": [
{
"type": "Action.OpenUrl",
"title": "View Project",
"url": "${projectUrl}"
}
]
}
}
}
}
]
}Workflow
Ask the user: 1. What type of data does the API return? 2. Are all items the same type (static) or different types (dynamic)? 3. What fields should appear in the card? 4. Should there be actions (e.g., "View Details")? 5. Are there multiple states or categories requiring different templates?
Then generate:
- Appropriate response_semantics configuration
- Static template, dynamic templates, or both
- Proper data binding with conditional rendering
- Responsive single-column layout
- Test scenarios for validation
Resources
- Adaptive Card Designer - Visual design tool
- Adaptive Card Schema - Full schema reference
- Template Language - Binding syntax guide
- JSONPath - Path query syntax
Common Patterns
List with Images
{
"type": "Container",
"$data": "${items}",
"items": [
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": "auto",
"items": [
{
"type": "Image",
"url": "${thumbnailUrl}",
"size": "small",
"$when": "${thumbnailUrl != null}"
}
]
},
{
"type": "Column",
"width": "stretch",
"items": [
{
"type": "TextBlock",
"text": "${title}",
"weight": "bolder",
"wrap": true
}
]
}
]
}
]
}Status Indicators
{
"type": "TextBlock",
"text": "${status}",
"color": "${if(status == 'Completed', 'good', if(status == 'In Progress', 'attention', 'default'))}"
}Currency Formatting
{
"type": "TextBlock",
"text": "$${formatNumber(amount, 2)}"
}````
Related skills
How it compares
Use mcp-create-adaptive-cards when Copilot must render MCP API output as cards rather than adding generic REST response wrappers.
FAQ
What does mcp-create-adaptive-cards do?
Skill converted from mcp-create-adaptive-cards.prompt.md
When should I use mcp-create-adaptive-cards?
Skill converted from mcp-create-adaptive-cards.prompt.md
Is mcp-create-adaptive-cards safe to install?
Review the Security Audits panel on this page before installing in production.