포괄적인 스트리밍 HTTP 지원으로 Model Context Protocol (MCP)의 이동 구현. 이 라이브러리는 클라이언트 애플리케이션과 도구/자료 간의 효율적인 통신을 가능하게 합니다.

특징

핵심 특징

• ** 풀 MCP 사양 지원 ** : MCP 구현, 프로토콜 버전 지원 2025-03-26 (예 : 클라이언트 호환성에 대한 2024-11-05와 기본).
• Streaming Support: Server-Sent Events(SSE)와 실시간 데이터 스트리밍 -Tool Framework: Structured 매개 변수 처리와 도구 실행
• Struct-First API: 유형의 안전으로 Go struct에서 스키마를 자동으로 생성
• ** 자원 관리**: RESTful 인터페이스를 가진 텍스트와 바이너리 리소스를 Serve -Prompt 템플릿: LLM 상호 작용에 대한 신속한 템플릿 생성 및 관리
• 진행 알림: 긴 실행 작업에 대한 진행 업데이트에 대한 내장 지원
• Logging System: 구성 수준과 통합 로깅

수송 선택권

trpc-mcp-go는 다른 배포 시나리오에 대한 세 가지 운송 메커니즘을 지원합니다.

####STDIO 운송 -Use Case: 로컬 통합, 명령줄 도구, 크로스 언어 호환성

tRPC MCP Go: Model Context Protocol Implementation with Streaming HTTP Support

A Go implementation of the Model Context Protocol (MCP) with comprehensive streaming HTTP support. This library enables efficient communication between client applications and tools/resources.

Features

Core Features

• Full MCP Specification Support: Implements MCP, supporting protocol versions up to 2025-03-26 (defaulting to 2024-11-05 for client compatibility in examples).
• Streaming Support: Real-time data streaming with Server-Sent Events (SSE)
• Tool Framework: Register and execute tools with structured parameter handling
• Struct-First API: Generate schemas automatically from Go structs with type safety
• Resource Management: Serve text and binary resources with RESTful interfaces
• Prompt Templates: Create and manage prompt templates for LLM interactions
• Progress Notifications: Built-in support for progress updates on long-running operations
• Logging System: Integrated logging with configurable levels

Transport Options

trpc-mcp-go supports three transport mechanisms for different deployment scenarios:

STDIO Transport

• Use Case: Local integrations, command-line tools, cross-language compatibility
• Communication: Standard input/output streams with JSON-RPC
• Process Model: Client launches server as subprocess
• Benefits: Simple, cross-platform, supports TypeScript/Python servers

Streamable HTTP Transport (Recommended)

• Use Case: Web integrations, multi-client servers, production deployments
• Communication: HTTP POST requests with optional SSE streaming
• Features: Session management, resumable connections, scalability
• Response Modes:
  • JSON responses for simple request-response
  • SSE streaming for real-time operations
• Server Notifications: Optional GET SSE endpoint for server-initiated messages

SSE Transport (Legacy)

• Use Case: Backward compatibility with MCP protocol version 2024-11-05
• Communication: HTTP POST requests + dedicated SSE endpoint for server messages
• Features: Always stateful with session management and persistent SSE connections
• Status: Deprecated in favor of Streamable HTTP, maintained for compatibility

Connection Modes

Streamable HTTP Transport supports multiple connection modes:

• Stateless: Simple request-response pattern without persistent sessions
• Stateful: Session management with user context and persistent connections

SSE Transport is always stateful by design with persistent connections.

STDIO Transport uses process-based communication (no HTTP sessions).

Experimental Tasks client

See Tasks client scope, usage and validation for the opt-in SEP-2663 client and explicit stateless HTTP discovery.

Installation

go get trpc.group/trpc-go/trpc-mcp-go

Quick Start