Skip to content

Commit fbe8425

Browse files
authored
update mcp pattern (#52)
1 parent f978cc1 commit fbe8425

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

_posts/2025-06-10-mcp-pattern.markdown

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ tag: MCP
1717
- [MCP Server Patterns](#mcp-server-patterns)
1818
- [Capability-Level MCP Server - _**"Goal-Oriented – abstracts business-level intents"**_](#capability-level-mcp-server---_goal-oriented--abstracts-business-level-intents_)
1919
- [Product-Level MCP Server - _**"System-Oriented – wraps complete product APIs"**_](#product-level-mcp-server---_system-oriented--wraps-complete-product-apis_)
20-
- [Component-Level MCP Server - _"Function-Oriented – exposes individual service functionality"_](#component-level-mcp-server---_function-oriented--exposes-individual-service-functionality_)
20+
- [Component-Level MCP Server - _**"Function-Oriented – exposes individual service functionality"**_](#component-level-mcp-server---_function-oriented--exposes-individual-service-functionality_)
2121
- [Concluion and Key Take Aways](#concluion-and-key-take-aways)
2222

2323
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
@@ -31,9 +31,9 @@ As AI agents mature from research demos to production grade orchestration platfo
3131

3232
<!-- To address this, the MCP Server Pattern introduces three architectural levels:-->
3333
To address this, we explore three architectural patterns:
34-
1) Capability-Level MCP Server for high-level business intent abstraction
35-
2) Product-Level MCP Server for wrapping stable product APIs
36-
3) Component-Level MCP Server for fine-grained, microservice-level automation
34+
- Capability-Level MCP Server for high-level business intent abstraction
35+
- Product-Level MCP Server for wrapping stable product APIs
36+
- Component-Level MCP Server for fine-grained, microservice-level automation
3737

3838
This layered approach enables cross product orchestration, simplifies agent development, supports modular evolution, and aligns well with team-based ownership in modern DevOps organizations.
3939

@@ -176,7 +176,7 @@ _**Key Benefits of this Architectural Pattern**_
176176
- **Plug-and-Play Modularity:** New products or services can be integrated by simply deploying a new agent and MCP server pair. Therefore, no changes required to existing agents or orchestration logic.
177177
- **LLM-Aware Orchestration:** Enables LLMs to reason across tools and compose semantically rich, multi-step workflows. Thereby, improving accuracy, adaptability, and intent resolution.
178178

179-
### Component-Level MCP Server - _"Function-Oriented – exposes individual service functionality"_
179+
### Component-Level MCP Server - _**"Function-Oriented – exposes individual service functionality"**_
180180

181181
A **Component-Level MCP Server** wraps and exposes the internal APIs of a single product component or microservice. It is ideal for **fine-grained automation, internal AI agents**, or when capabilities are distributed across modular components.
182182

0 commit comments

Comments
 (0)