문제 해결

##1. 생산에 MCP 서버를 확장 표준 FastMCP 프레임 워크는 생산 환경에서 중요한 과제를 직면합니다.

• State Management: Traditional FastMCP 서버는 메모리에 상태 유지, 수평 스케일링 어려운
• Serverless 제한: Serverless 환경은 FastMCP가 설계되지 않은 최첨단 아키텍처를 요구합니다.
• Multi-tenant Support: 동일한 서버에서 여러 개의 열거를 실행하면 복잡한 세션 관리가 필요합니다.

##2. 위임된 OAuth 지원 MCP 서버의 인증은 복잡합니다. -Tool-Level Auth: 사용자는 도구가 필요할 때만 인증해야 합니다.

• Third-Party Integration: Notion, Slack 등과 같은 서비스에 대한 OAuth 지원은 복잡한 토큰 관리가 필요합니다.
• Security: 보안을 유지하면서 다중 인증 흐름 관리

우리의 해결책

MCP 도구 키트는 FastMCP와 전체 호환성을 유지하면서 이러한 문제를 해결하는 생산 ready 프레임 워크를 제공합니다. 어떻게 작동하나요?

이 건축 다이어그램은 MCPToolKit가 생산 관련 MCP 서버를 가능하게하는 방법을 설명합니다.

1.LLM 클라이언트 (예:.

MCPToolKit - Production-Ready MCP Server Framework

The Problems We Solve

1. Scaling MCP Servers in Production

The standard FastMCP framework faces significant challenges in production environments:

• State Management: Traditional FastMCP servers maintain state in memory, making horizontal scaling difficult
• Serverless Limitations: Serverless environments require stateless architectures, which FastMCP wasn’t designed for
• Multi-tenant Support: Running multiple tenants on the same server requires complex session management

2. Delegated OAuth Support

Managing authentication for MCP servers is complex:

• Tool-Level Auth: Users should only authenticate when a tool requires it
• Third-Party Integration: Supporting OAuth for services like Notion, Slack, etc. requires complex token management
• Security: Managing multiple authentication flows while maintaining security is challenging

Our Solution

MCPToolKit provides a production-ready framework that solves these problems while maintaining full compatibility with FastMCP. Here’s how it works:

graph TD
    A[LLM Cliente.g. Claude, ChatGPT, Cursor] --> B[Load Balancer]
    B --> C[MCP Server Instance 1with Redis State]
    B --> D[MCP Server Instance 2with Redis State]
    B --> E[MCP Server Instance Nwith Redis State]
    C --> F[RedisSession State & OAuth Tokens]
    D --> F
    E --> F
    C --> H[MCP Authorization ServerOAuth 2.1 & PKCE]
    D --> H
    E --> H
    H --> G[OAuth ProvidersNotion, Slack, etc.]
    style H fill:#f9f,stroke:#333,stroke-width:2px

This architecture diagram illustrates how MCPToolKit enables production-ready MCP servers:

1. LLM Clients (e.g., Claude, ChatGPT, Cursor) initiate requests to the MCP server. These clients can be any application that needs to interact with MCP tools.

2. Load Balancer distributes incoming requests across multiple MCP server instances, enabling horizontal scaling and high availability.

3. MCP Server Instances (1 through N) handle tool execution and resource access. Each instance:

   • Maintains its own Redis state for session persistence
   • Can handle requests independently
   • Shares the same codebase and configuration
   • Can be scaled horizontally based on demand

4. Redis serves as the central state store, providing:

   • Session state persistence across server restarts
   • OAuth token storage and management
   • Shared state between server instances
   • Enables stateless server instances

5. MCP Authorization Server (highlighted in pink) manages all OAuth-related operations:

   • Implements OAuth 2.1 with PKCE for secure authentication
   • Handles token issuance and refresh
   • Manages consent flows
   • Centralizes OAuth logic for all server instances