Adaptive Cards Mcp
Wire your coding agent into Adaptive Card JSON so Teams, Outlook, and Copilot notifications render correctly without hand-tuning schema.
Overview
Adaptive Cards MCP is an MCP server for the Build phase that generates, validates, and optimizes Adaptive Card JSON for Teams, Outlook, and Copilot.
What is this MCP server?
- Generates Adaptive Card JSON from natural-language layout requests
- Validates payloads against Adaptive Cards schema before you ship to Teams or Outlook
- Optimization hints for Copilot and Microsoft 365 host constraints
- stdio npm package adaptive-cards-mcp at version 2.3.0
- Targets Teams, Outlook, and Copilot card hosts from one agent workflow
- Package version 2.3.0 on npm with stdio transport
- Registry identifier adaptive-cards-mcp
- Supports Teams, Outlook, and Copilot card scenarios per server description
Community signal: 27 GitHub stars.
What problem does it solve?
Hand-written Adaptive Cards break on different Microsoft hosts and waste hours in validate-and-redeploy cycles.
Who is it for?
Indie builders adding Teams or Outlook notifications to a SaaS bot, internal agent, or workflow automation.
Skip if: Teams that only need static HTML email or Slack Block Kit with no Microsoft 365 card surface.
What do I get? / Deliverables
Your agent outputs schema-checked card JSON you can drop into bots and messaging extensions with fewer host-specific surprises.
- Adaptive Card JSON payloads sized for your described UI
- Validation feedback on schema and common host issues
- Optimized card structure suggestions for Microsoft hosts
Recommended MCP Servers
Journey fit
Card generation and validation sit on the product surface where Microsoft 365 messaging integrations are implemented. This is an MCP bridge for Adaptive Cards schema work alongside bots and workflow connectors, not a launch or analytics task.
How it compares
MCP integration for Adaptive Cards authoring, not a general UI component library skill.
Common Questions / FAQ
Who is Adaptive Cards MCP for?
Solo and small-team developers wiring Claude or Cursor into Microsoft 365 messaging who want validated card JSON without living in the Adaptive Cards Designer.
When should I use Adaptive Cards MCP?
Use it during integration work when you are drafting or refactoring Teams, Outlook, or Copilot cards and need generate-and-validate loops inside your agent session.
How do I add Adaptive Cards MCP to my agent?
Install the npm package adaptive-cards-mcp (stdio transport), register it in your MCP client config pointing at that binary, then invoke card tools from your agent like any other MCP server.