Go에 내장된 운영 준비 MCP(모델 컨텍스트 프로토콜) 서버 템플릿(OAUTH 권한 포함)으로, 주요 AI 제공업체와 함께 작동합니다.

동기

MCP 사양은 비교적 최근에 개발되어 Go로 완전한 서버를 구축하는 포괄적인 문서가 부족합니다.
이 템플릿은 Claude Web, OpenAI와 같은 원격 제공자와 원활하게 통합되는 완전 호환 MCP 서버를 제공합니다.
하지만 Claude Desktop 같은 지역 제공업체와도 함께합니다.

특징

• 🔐 OAuth RFC 8414 및 RFC 9728 준수

• .well-known/oauth-protected-resource 및 .well-known/oauth-authorization-server 엔드포인트 지원

• 두 엔드포인트 모두 구성 가능합니다

• 🛡️ 여러 JWT 검증 방법

• Istio와 같은 외부 시스템에 위임됨

• JWKS URI 및 CEL 표현식을 기반으로 한 지역 검증

• 📋 접근 로그는 필드를 제외하거나 편집할 수 있습니다

• 🚀 운영 준비: 전체 예제, Dockerfile, Helm Chart, GitHub Actions for CI 포함

• ⚡ 매우 쉽게 확장할 수 있습니다: 좋은 주스에 첨가된 생산 비타민: mcp-go

배치

제작 🚀

chart/ 디렉터리에 있는 Helm 차트를 사용하여 Kubernetes에 배포하세요.

---

MCP Forge

A production-ready MCP (Model Context Protocol) server template (oauth authorization included) built in Go that works with major AI providers.

Motivation

The MCP specification is relatively new and lacks comprehensive documentation for building complete servers in Go. This template provides a fully compliant MCP server that integrates seamlessly with remote providers like Claude Web, and OpenAI, but with local providers like Claude Desktop too.

Features

• 🔐 OAuth RFC 8414 and RFC 9728 compliant

  • Support for .well-known/oauth-protected-resource and .well-known/oauth-authorization-server endpoints
  • Both endpoints are configurable

• 🛡️ Several JWT validation methods

  • Delegated to external systems like Istio
  • Locally validated based on JWKS URI and CEL expressions for claims

• 📋 Access logs can exclude or redact fields

• 🚀 Production-ready: Included full examples, Dockerfile, Helm Chart and GitHub Actions for CI

• ⚡ Super easy to extend: Production vitamins added to a good juice: mcp-go

Deployment

Production 🚀

Deploy to Kubernetes using the Helm chart located in the chart/ directory.

---

Our recommendations for remote servers in production:

• Use a consistent hashring HTTP proxy in front of your MCP server when using MCP Sessions

• Use an HTTP proxy that performs JWT validation in front of the MCP instead of using the included middleware:

  • Protect your MCP exactly in the same way our middleware does, but with a super tested and scalable proxy instead
  • Improve your development experience as you don’t have to do anything, just develop your MCP tools

• Use an OIDP that:

  • Cover Oauth Dynamic Client Registration
  • Is able to custom your JWT claims.

👉 Keycloak covers everything you need in the Oauth2 side

👉 Istio covers all you need to validate the JWT in front of your MCP

👉 Hashrouter uses a configurable and truly consistent hashring to route the traffic, so your sessions are safe with it. It has been tested under heavy load in production scenarios

How to develop your MCP

Prerequisites

• Go 1.24+

Modify the code and run