Adeptia MCP Server

Model Context Protocol

AI-powered access to the Adeptia Connect integration platform. Design, build, validate, and deploy integrations through any MCP-compatible client.

%%{init: {
  'theme': 'dark',
  'themeVariables': {
    'primaryColor': '#1e1e3f',
    'primaryTextColor': '#ffffff',
    'primaryBorderColor': '#0A4ECD',
    'lineColor': '#3C7BEF',
    'secondaryColor': '#16213e',
    'tertiaryColor': '#0f3460',
    'fontSize': '14px'
  }
}}%%
%% Adeptia MCP Server Architecture - Strangler Fig Pattern
%% Reference: /kb-development/core/02-standards/diagrams/
%% Updated: January 13, 2026 - Added ai-agent as H2 2026 foundation

flowchart LR
    subgraph clients[" "]
        direction TB
        c_title["AI APPLICATIONS
Any MCP-compatible client"] assistants["Claude, Cody, Zed
AI Assistants"] ides["Cursor, Replit, VS Code
AI Code Editors"] forge["Adeptia v6 Forge
AI Integration"] end subgraph transports[" "] direction TB tr_title["DEPLOYMENT"] customer["Customer Network
On-premises"] cloud["Adeptia Cloud
SaaS"] end subgraph mcp[" "] direction TB m_title["ADEPTIA MCP SERVER"] mcpcore["MCP
Standardized Protocol"] end subgraph tools[" "] direction TB t_title["MCP TOOLS"] discovery["Discovery
Connectors & Templates"] validation["Validation
Config & Mapping"] workflow["Workflow
Create & Deploy"] monitoring["Monitoring
Dashboard & Logs"] end subgraph router[" "] direction TB r_title["BACKEND ROUTER
Strangler Fig Pattern"] route["Route by Capability
Feature flags"] end subgraph api[" "] direction TB a_title["API LAYER"] connect_api["Connect v5 API
WebRunner (read) / Runtime (execute)"] new_api["ai-agent Services
LangGraph + FastAPI (H2 2026)"] end subgraph backend[" "] direction TB b_title["EXECUTION"] platform["Connect v5
Current Runtime"] future["v6 Platform
Future"] end assistants --> customer ides --> customer forge --> cloud customer --> mcpcore cloud --> mcpcore mcpcore --> discovery & validation & workflow & monitoring discovery & validation & workflow & monitoring --> route route --> connect_api route -.-> new_api connect_api --> platform new_api -.-> platform new_api -..-> future classDef titleStyle fill:none,stroke:none,color:#64748b,font-size:12px classDef clientBox fill:#1e293b,stroke:#3b82f6,stroke-width:2px,color:#fff classDef transportBox fill:#1e293b,stroke:#22c55e,stroke-width:2px,color:#fff classDef mcpBox fill:#1e1e3f,stroke:#0A4ECD,stroke-width:3px,color:#fff classDef toolsBox fill:#1e3a5f,stroke:#3b82f6,stroke-width:2px,color:#fff classDef routerBox fill:#2d1f3d,stroke:#a855f7,stroke-width:2px,color:#fff classDef connectApiBox fill:#2d2a1a,stroke:#f59e0b,stroke-width:2px,color:#fff classDef newApiBox fill:#1a2e1a,stroke:#22c55e,stroke-width:2px,stroke-dasharray:5 5,color:#fff classDef backendBox fill:#0d2847,stroke:#64748b,stroke-width:2px,color:#fff classDef futureBox fill:#1a2e1a,stroke:#22c55e,stroke-width:2px,stroke-dasharray:8 4,color:#86efac classDef invisible fill:none,stroke:none class c_title,tr_title,m_title,t_title,r_title,a_title,b_title titleStyle class assistants,ides,forge clientBox class customer,cloud transportBox class mcpcore mcpBox class discovery,validation,workflow,monitoring toolsBox class route routerBox class connect_api connectApiBox class new_api newApiBox class platform backendBox class future futureBox class clients,transports,mcp,tools,router,api,backend invisible

AI Applications → Transports → MCP Server → Backend Router → API Layer → Execution

Operational
/status
Status dashboard
/mcp
MCP protocol
/health
Health JSON