Scaled MCP Server

Name: Scaled MCP Server
Author: sardonicfusa

@sardonicfusa

リポジトリ

Scaled MCP Server について

ScaledMCP is a horizontally scalabled MCP and A2A Server. You know, for AI. a2a, ai, mcp, mcp-client, mcp-server

#mcp #ai #server

基本情報

カテゴリ

その他

ライセンス

AGPL-3.0 license

ランタイム

トランスポート

stdio

公開者

sardonicfusa

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Scaled MCP Server?

The Scaled MCP Server is a Go library that implements the MCP 2025-03 specification with support for horizontal scaling. It provides a horizontally scalable MCP server designed to be embedded in applications, supporting load-balanced deployments with flexible configuration.

How to use Scaled MCP Server?

Install the library with go get github.com/traego/scaled-mcp@latest (requires Go 1.24 or higher). Create a server with config.DefaultConfig(), configure session storage (in-memory for testing or Redis for production), create a tool registry (static or dynamic), and start the server with srv.Start(). The library also supports using an external HTTP server via a custom router.

Key features of Scaled MCP Server

HTTP transport with main /mcp endpoint and optional SSE endpoint
Distributed session management using Redis or in-memory store
Actor-based architecture for session handling and message routing
Horizontal scaling support for load-balanced multi-node deployments
Static and dynamic tool registry options
Embeddable Go library requiring only Go 1.24+

Use cases of Scaled MCP Server

Build a scalable AI assistant that exposes tools and prompts via MCP
Deploy a load-balanced MCP server across multiple nodes for high availability
Integrate custom tool registries (e.g., calculator, weather) with dynamic updates
Use an existing HTTP server infrastructure (e.g., Chi router) with MCP transport

FAQ from Scaled MCP Server

What Go version is required?

The library requires Go 1.24 or higher.

What session stores are supported?

Redis is recommended for production deployments to support horizontal scaling. An in-memory session store is available for development and testing only.

Does Scaled MCP Server support dynamic tool registration?

Yes, it provides a dynamic tool registry that allows tools to be added or changed at runtime, alongside a static registry for fixed tools.

What transport does Scaled MCP Server use?

It uses HTTP transport with a main /mcp endpoint and an optional SSE endpoint, including capabilities negotiation.

Can I use my own HTTP server?

Yes, you can attach the MCP transport to an external router (e.g., Chi) and manage your own HTTP server, though CORS must be configured on your router.