{
  "docId": "019dd923-5e88-73ef-bd5d-47815abb602b",
  "docSlug": "485b1e996a637b43",
  "documentTitle": "2025 AI Agents and the Model Context Protocol",
  "authorId": "BCG",
  "authorName": "BCG",
  "documentKindSlug": "consulting-deck",
  "documentKindLabel": "Consulting deck",
  "sourceTypeSlug": "strategy_consulting",
  "sourceTypeLabel": "Strategy consulting",
  "presentationDate": null,
  "orientation": "landscape",
  "aspectRatio": 1.778,
  "pageNumber": 34,
  "pageCount": 37,
  "prevPage": 33,
  "nextPage": 35,
  "slideType": "comparison_table",
  "function": "compare_options",
  "density": "dense",
  "nDataPoints": 0,
  "notes": "The slide uses a visual comparison to illustrate architectural anti-patterns for MCP (Model Context Protocol) servers.",
  "elementsJson": [
    "headline_text",
    "process_diagram",
    "paragraph"
  ],
  "metadataConfidence": 1,
  "imagePath": null,
  "slideHref": "/slides/019dd923-5e88-73ef-bd5d-47815abb602b/34",
  "deckHref": "/decks/019dd923-5e88-73ef-bd5d-47815abb602b",
  "deckJsonHref": "/decks/019dd923-5e88-73ef-bd5d-47815abb602b.json",
  "deckAnchorHref": "/decks/019dd923-5e88-73ef-bd5d-47815abb602b#slide-34",
  "components": [
    {
      "bbox": null,
      "kind": "callout",
      "text": "Monolith MCP servers bundle multiple tool integrations or functions into one server across service boundaries, potentially overloading the agent with too many choices; Microservice MCP servers host a subset of tools, which can lead to a highly complex, unmanageable agent architecture, undermining interoperability and reusability.",
      "attrs": null,
      "subkind": null,
      "toolName": "Visual emphasis",
      "toolSlug": "visual-emphasis",
      "confidence": null,
      "componentId": "019dd952-47c7-738e-b702-423a408aa81e",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.4,
        "w": 0.45,
        "x": 0.55,
        "y": 0.35
      },
      "kind": "diagram",
      "text": "Microservice MCP pattern diagram",
      "attrs": null,
      "subkind": "other",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "3841fb0a-531e-4e4d-85d9-ee2617201fef",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.4,
        "w": 0.45,
        "x": 0.05,
        "y": 0.35
      },
      "kind": "diagram",
      "text": "Monolith MCP pattern diagram",
      "attrs": null,
      "subkind": "other",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "d60e8956-1ee9-446b-b766-1883d734e2d0",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.15,
        "w": 0.4,
        "x": 0.55,
        "y": 0.78
      },
      "kind": "paragraph",
      "text": "Microservice MCP servers host a subset of tools, which can lead to a highly complex, unmanageable agent architecture, undermining interoperability and reusability",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "06145b09-cbc1-4ce7-904a-8aa95a3755f3",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.15,
        "w": 0.4,
        "x": 0.05,
        "y": 0.78
      },
      "kind": "paragraph",
      "text": "Monolith MCP servers bundle multiple tool integrations or functions into one server across service boundaries, potentially overloading the agent with too many choices",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "eafff5f8-d726-4e56-890c-28147c5a4124",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.05,
        "w": 0.9,
        "x": 0.05,
        "y": 0.09
      },
      "kind": "title",
      "text": "Avoid monoliths or microservices at the extremes when building MCP servers",
      "attrs": null,
      "subkind": "headline",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "9808d660-df83-42e4-9c93-c8a4914a7e9e",
      "frameworkName": null,
      "frameworkSlug": null
    }
  ],
  "metrics": [],
  "tools": [
    {
      "name": "Antithesis",
      "slug": "antithesis",
      "agent": "Storyteller",
      "layer": "loop",
      "matchId": "019dd95a-121f-71e6-8e86-8c238ec6e78b",
      "evidence": "Parallel descriptions juxtapose 'overloading the agent' vs 'undermining interoperability'",
      "confidence": 70
    },
    {
      "name": "Contrast Pairs",
      "slug": "contrast-pairs",
      "agent": "Storyteller",
      "layer": "loop",
      "matchId": "019dd95a-121f-71e6-8e86-88f6c70bb9cb",
      "evidence": "Monolith vs Microservice paired diagrams set up the paradox",
      "confidence": 80
    },
    {
      "name": "Action Titles",
      "slug": "action-titles",
      "agent": "Architect",
      "layer": "slide",
      "matchId": "019dd95a-121f-71e6-8e86-816fb3708ce0",
      "evidence": "Title 'Avoid monoliths or microservices at the extremes' is prescriptive",
      "confidence": 85
    },
    {
      "name": "Comparison frame",
      "slug": "comparison-frame",
      "agent": null,
      "layer": "slide",
      "matchId": "075af7a7-5d75-4a85-be59-1b41dac32d5a",
      "evidence": "Monolith MCP servers vs Microservice MCP servers",
      "confidence": 0.7
    },
    {
      "name": "Contrast Principle",
      "slug": "contrast-principle",
      "agent": "Designer",
      "layer": "slide",
      "matchId": "019dd95a-121f-71e6-8e86-8589059745a7",
      "evidence": "Two side-by-side mirrored architecture diagrams",
      "confidence": 80
    }
  ],
  "frameworks": [
    {
      "name": "Monolith vs Microservice MCP Patterns",
      "slug": null,
      "matchId": "019dd95a-1ca5-70bb-bba3-7ceecce356c9",
      "evidence": "Two named patterns drawn side by side as the architectural choice",
      "confidence": 85
    }
  ],
  "arcBeats": [],
  "loops": [
    {
      "to": 35,
      "from": 33,
      "name": "Paradox Resolver",
      "slug": "20-paradox-resolver",
      "bestFor": "Strategic pivots, innovation pitches, challenging conventional wisdom",
      "matchId": "019dd95a-088b-72c8-b7e0-0f0030d8184b",
      "evidence": "p33 best-practices framing, p34 contrasts both extremes, p35 prescribes 'lean MCP servers' middle path",
      "position": 9,
      "objective": "Reconcile monolith vs microservice MCP extremes",
      "structure": "The Apparent Contradiction -> Why Both Seem True -> The Deeper Truth That Reconciles",
      "confidence": 70,
      "description": "Introduce a seeming contradiction that captures attention, then resolve it with a deeper truth"
    }
  ],
  "imagePathAlt": null,
  "thumbSrc": null,
  "thumbSrcAlt": null,
  "locked": true
}