Adaptive MCP Server

Generate, validate, and optimize Adaptive Cards for Teams, Outlook, and Copilot.

Local serverstdioTypeScript

What is the Adaptive MCP server?

Generate, validate, and optimize Adaptive Cards for Teams, Outlook, and Copilot. That is what the adaptive mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP server that helps AI assistants generate valid, accessible Adaptive Cards for Teams, Outlook, Copilot, and other Microsoft surfaces. 9 tools, 3 guided workflows, 924 tests.

The tools it exposes

The server publishes 11 tools. What each one is for:

  • generate_card — Natural language / data → valid Adaptive Card v1.6 JSON
  • validate_card — Schema validation + accessibility score + host compatibility + suggested fixes
  • data_to_card — Auto-select Table / FactSet / Chart / List from data shape
  • optimize_card — Improve accessibility, performance, modernize actions
  • template_card — Static card → ${expression} data-bound template
  • transform_card — Version upgrade/downgrade, host-config adaptation
  • suggest_layout — Recommend best layout pattern for a description
  • generate_and_validate — Generate + validate + optionally optimize in one call
  • card_workflow — Multi-step pipeline: generate → optimize → template → transform
  • Configuration — The Configuration tool exposed by this server
  • Architecture — The Architecture tool exposed by this server

Getting it running

Installation goes through your MCP client rather than a global install: point it at adaptive-cards-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: MCP_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, AZURE_OPENAI_API_KEY, OLLAMA_BASE_URL, POSTHOG_API_KEY, POSTHOG_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Adaptive's toolset — generate_card, validate_card, data_to_card and 8 more — is a fair guide to whether it matches your workflow. It is maintained by VikrantSingh01; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Adaptive.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
generate_cardNatural language / data → valid Adaptive Card v1.6 JSON
validate_cardSchema validation + accessibility score + host compatibility + suggested fixes
data_to_cardAuto-select Table / FactSet / Chart / List from data shape
optimize_cardImprove accessibility, performance, modernize actions
template_cardStatic card → ${expression} data-bound template
transform_cardVersion upgrade/downgrade, host-config adaptation
suggest_layoutRecommend best layout pattern for a description
generate_and_validateGenerate + validate + optionally optimize in one call
card_workflowMulti-step pipeline: generate → optimize → template → transform
ConfigurationThe Configuration tool exposed by this server.
ArchitectureThe Architecture tool exposed by this server.

How to install the Adaptive MCP server

{
  "mcpServers": {
    "adaptive-cards": {
      "command": "npx",
      "args": ["-y", "adaptive-cards-mcp"],
      "env": {
        "MCP_API_KEY": "your-value",
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value",
        "AZURE_OPENAI_API_KEY": "your-value",
        "OLLAMA_BASE_URL": "your-value",
        "POSTHOG_API_KEY": "your-value",
        "POSTHOG_HOST": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MCP_API_KEYCredential the server authenticates with.Yes
ANTHROPIC_API_KEYCredential the server authenticates with.Yes
OPENAI_API_KEYCredential the server authenticates with.Yes
AZURE_OPENAI_API_KEYCredential the server authenticates with.Yes
OLLAMA_BASE_URLEndpoint or connection string the server talks to.Yes
POSTHOG_API_KEYCredential the server authenticates with.Yes
POSTHOG_HOSTEndpoint or connection string the server talks to.Optional

Example prompts to try

  • Use Adaptive to generate card.
  • Use Adaptive to validate card.
  • Use Adaptive to data to card.

Frequently asked questions

It connects Adaptive to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (generate_card, validate_card, data_to_card, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Adaptive directly.