Goに組み込まれた本番対応のMCP(Model Context Protocol)サーバーテンプレート(OAUS認証付き)で、主要な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式に基づいてクレームのローカル検証

• 📋 アクセスログはフィールドを除外または編集できます

• 🚀 本番対応:CI用の完全な例、Dockerfile、Helm Chart、GitHubアクションを含む

• ⚡ 非常に簡単に伸ばせる:良いジュースに添加された生産用ビタミン:mcp-go

展開

###制作 🚀 [chart/ディレクトリにあるHelm chartを使って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