Agentic AI · MCP2026

Enterprise Knowledge Layer & MCP Agent

A governed knowledge layer that exposes KPI, schema, product, and semantic context through a reusable MCP tool surface.

MCPAzure AI SearchAzure AI FoundryFunction AppsEntra ID
Project summary

Impact

Shared grounding layer

one governed tool surface for product, KPI, schema, definition, and relationship context

Hiring signal

What this proves

MCP server design, enterprise retrieval, multi-index search, identity-aware Azure integration, and reusable knowledge-platform architecture.

My role

Ownership

Lead developer · solution architecture, MCP tool surface, orchestration backend, product-aware index resolution, multi-index retrieval, and Azure identity integration

Status

In development · architecture and source available

Development-stage architecture and trace.

The problem

What needed to change

Enterprise knowledge is distributed across KPI dictionaries, schema references, semantic relationships, definitions, documents, and product-specific metadata. Without a shared access layer, each AI workflow reimplements retrieval logic and receives inconsistent business context.

My approach

How I built it

The solution is organized into content-management, knowledge-store, and MCP-access layers. Curated definitions, KPI dictionaries, table and column metadata, semantic relationships, and product-specific context are indexed in Azure AI Search. A remote MCP server exposes this knowledge through focused Azure AI Foundry agents for product, KPI, schema, and relationship resolution.

Architecture judgment

Why this design

MCP provides a versioned, reusable contract for multiple consumers. Specialized agents keep product, KPI, and schema resolution independently testable, while the product registry selects the correct indexes without requiring downstream client changes.

Architecture

High-level system design

The complete execution path, service boundaries, data stores, security controls, validation stages, and operational telemetry.

Implementation

Key components

  • Remote MCP server hosted on Azure Function Apps
  • Product registry resolving product-specific search indexes
  • Azure AI Search indexes for KPI, schema, definitions, and relationships
  • Focused Foundry agents for product, schema, and KPI identification
  • Entra ID and Managed Identity for governed access

Technology

Tech stack

Agentic AI

Azure AI FoundryAzure OpenAIMCPRAG

Backend

PythonFastAPIAsyncIOPydantic

Cloud

Function AppsAzure AI SearchKey VaultMonitor

Security

Entra IDManaged IdentityOAuth 2.0RBAC

Development trace

How the planned flow behaves

development trace · MCP tool orchestration & multi-index lookup

Run the trace to see the main workflow stages.