{"slug":"connectors/MCP","title":"MCP","section":"connectors","sectionLabel":"Connectors","status":"unclassified","type":"document","path":"connectors/MCP.mdx","bytes":3040,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Tier C — Historical.** This document is a point-in-time snapshot preserved for reference. For current architecture, see [CANONICAL_PLATFORM_ARCHITECTURE.md](../architecture/CANONICAL_PLATFORM_ARCHITECTURE.md).\n\nStatus: CURRENT\nScope: MCP protocol boundary, role, endpoints, authorization, integration blockers\nCanonical Owner: Platform / MCP\nLast Verified: 2026-07-11\nEvidence Basis: docs/CANON.md, docs/FINAL_E2E_SYSTEM.md, docs/platform-specs/19-api-contracts.md, docs/ip/tech/MCP_OAUTH_ARCHITECTURE.md, docs/internal/operations/API_REFERENCE.md, docs/internal/operations/CUSTOMER_ZERO_FLOW_TEST.md, wrangler manifests for mcp-connector and webhook-ingress, Option B divergence audit, documented MCP auth evidence\nSupersedes: none\nSuperseded By: none\n\n---\n\n## 1. MCP IS A PROTOCOL, NOT A PRODUCT DATA PLANE\n\nMCP is a protocol/tool boundary.\n\n```text\nL1 PRODUCT\n      ↓\nPLATFORM FACADE / GATEWAY\n```\n\n```text\nMCP CLIENT / AGENT\n      ↓\nMCP CONNECTOR\n      ↓\nTOOLS / PLATFORM CAPABILITY\n```\n\nMCP must not be documented as the normal L1 product data plane.\n\nMCP is an externally authenticated protocol surface connecting AI assistants and tools to governed IntegrateWise capability.\n\n---\n\n## 2. CURRENT RUNTIME BOUNDARIES\n\nCurrent wrangler manifests show:\n\n- services/mcp-connector exposes route `mcp.integratewise.ai`\n\nCurrent repo must not assume other MCP pools or secondary MCP home names unless explicitly documented in tenant/runtime evidence.\n\n---\n\n## 3. CURRENT AUTHORIZATION STATE\n\nReported unresolved MCP client authorization issue:\n\n- tenant: integratewise\n- client: kiro-iw\n- result: 403\n\nClassification: Current integration blocker if reproduction is still valid.\n\nDocumentation must not classify MCP as required for Customer Zero activation unless verified.\n\nInbound MCP configuration documentation must not be published before tenant and client registration are authorized and verified.\n\n---\n\n## 4. MCP POOL DOCUMENTATION BAN\n\nThe `iw-mcppool-mcp-server` must not be documented as the Customer Zero backend unless actual product routing proves it.\n\nCustomer Zero activation documentation must use verified Spine/Gateway paths unless alternative paths are explicitly tested and authorized.\n\n---\n\n## 5. DO NOT TREAT MCP AS DEFAULT L1 BACKEND\n\nMCP is not automatically the default Customer Zero backend.\n\nMCP is not a fallback connection for the L1 product when Gateway/projection paths are uncertain.\n\nMCP is:\n\n- an AI and tool access boundary\n- a governed discovery, capability query, and action invocation surface\n- a protocol path for authorized tenants/clients\n\nIf Customer Zero or onboarding needs a non-MCP path, document that fact explicitly.\n\n---\n\n## 6. DOCUMENTS THAT PRECEDE THIS\n\n- docs/FINAL_E2E_SYSTEM.md §5\n- docs/platform-specs/19-api-contracts.md\n- docs/ip/tech/MCP_OAUTH_ARCHITECTURE.md\n- docs/ip/tech/MCP_ADK_ROUTING_SPINE_MEMORY_ARCHITECTURE.md\n- docs/archive/MCP_ADK_SPINE_CACHE_ARCHITECTURE.md\n\nWhen conflict arises between this document and those documents, this document is canonical.\n"}