go-mcp-servers
Production-ready Model Context Protocol (MCP) servers in Go — filesystem, PostgreSQL, Redis, shell, HTTP, and Home Assistant. Embed as static binaries or import as Go packages.
接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
Production-ready Model Context Protocol (MCP) servers in Go — filesystem, PostgreSQL, Redis, shell, HTTP, and Home Assistant. Embed as static binaries or import as Go packages.
Production-ready Model Context Protocol (MCP) servers in Go. Filesystem, PostgreSQL, Redis, shell, HTTP & Home Assistant. Embeddable as binaries or packages.
go-mcp-servers fills the gap left by the official MCP reference servers — which only ship in TypeScript and Python. Use these in Claude Desktop, Cursor, custom Go agents, or any MCP-compatible host. Each server is a single static binary (~9 MB) and also importable as a Go package.
git clone https://github.com/dimasd-angga/go-mcp-servers
cd go-mcp-servers
make build-all
# binaries appear in ./bin/
FS_ROOT=$HOME/workspace ./bin/mcp-filesystem
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"filesystem": {
"command": "/absolute/path/to/bin/mcp-filesystem",
"env": { "FS_ROOT": "/Users/me/workspace" }
}
}
}
Restart Claude Desktop. The filesystem tools appear automatically. Ask: "Read README.md and summarize it."
The official modelcontextprotocol/servers repo ships only TypeScript and Python. For Go-native AI agent runtimes — like Tauri desktop agents, Ollama-adjacent Go services, or anything embedding MCP into a Go process — that's a friction point. go-mcp-servers exists so Go projects can:
go vet, race detector, gosec — production-ready guarantees from the toolchain.If you're on TypeScript or Python, use the official reference servers. If you're on Go, use this.
{
"mcpServers": {
"filesystem": { "command": "/usr/local/bin/mcp-filesystem", "env": { "FS_ROOT": "/Users/me/workspace" } },
"postgres": { "command": "/usr/local/bin/mcp-postgres", "env": { "POSTGRES_DSN": "postgres://reader:secret@db:5432/app?sslmode=require" } },
"shell": { "command": "/usr/local/bin/mcp-shell", "env": { "SHELL_WORKDIR": "/Users/me/workspace", "SHELL_ALLOWED_CMDS": "go,npm,git,make" } },
"redis": { "command": "/usr/local/bin/mcp-redis", "env": { "REDIS_ADDR": "localhost:6379", "REDIS_PREFIX": "claude:" } },
"http": { "command": "/usr/local/bin/mcp-http", "env": { "HTTP_ALLOWED_HOSTS": "api.github.com,httpbin.org" } },
"homeassistant": { "command": "/usr/local/bin/mcp-homeassistant", "env": { "HA_URL": "http://homeassistant.local:8123", "HA_TOKEN": "..." } }
}
}
Each server is also a Go package — import it and host the MCP server in-process.
package main
import (
"log"
fsserver "github.com/dimasd-angga/go-mcp-servers/servers/filesystem"
"github.com/mark3labs/mcp-go/server"
)
func main() {
fs, err := fsserver.NewFilesystemServer()
if err != nil {
log.Fatal(err)
}
if err := server.ServeStdio(fs.MCP()); err != nil {
log.Fatal(err)
}
}
flowchart LR
Host["MCP host<br/>Claude Desktop / Cursor / custom Go agent"]
Transport["JSON-RPC 2.0<br/>stdio or SSE"]
Host --> Transport
Transport --> Filesystem["mcp-filesystem binary"]
Transport --> Postgres["mcp-postgres binary"]
Transport --> Redis["mcp-redis binary"]
Transport --> Shell["mcp-shell binary"]
Transport --> HTTP["mcp-http binary"]
Transport --> HomeAssistant["mcp-homeassistant binary"]
Filesystem --> FS["Filesystem root"]
Postgres --> PG["Postgres database"]
Redis --> RD["Redis instance"]
Shell --> SH["Sandboxed shell"]
HTTP --> API["HTTP endpoints"]
HomeAssistant --> HA["Home Assistant API"]
Filesystem -. logs .-> Stderr["stderr"]
Postgres -. logs .-> Stderr
Redis -. logs .-> Stderr
Shell -. logs .-> Stderr
HTTP -. logs .-> Stderr
HomeAssistant -. logs .-> Stderr
MCP host (Claude Desktop / Cursor / your Go agent)
│
▼ JSON-RPC 2.0 (stdio or SSE)
go-mcp-server binary
│
▼
External resource (filesystem, Postgres, Redis, shell, HTTP, HA)
--transport=sse --port=N).MCP_AUTH_TOKEN enables bearer-token gating across servers.Pick the one that fits your stack.
# Bring up Postgres + Redis on alternate ports (55432, 56379) to avoid host clashes
docker compose -f deploy/docker-compose.yml up -d postgres redis
# Run everything
export POSTGRES_TEST_DSN="postgres://mcptest:[email protected]:55432/mcptest?sslmode=disable"
export REDIS_TEST_ADDR="127.0.0.1:56379"
export POSTGRES_DSN="$POSTGRES_TEST_DSN"
export REDIS_ADDR="$REDIS_TEST_ADDR"
make test-all # unit + integration tests
make build-all # build into ./bin/
make smoke # exercise each binary via real stdio JSON-RPC
make verify # lint + test-all + smoke (release gate)
CI runs the same make verify on every push.
mongodb serverslack server (Slack Web API)github server (REST + GraphQL)ghcr.ioVote in Discussions.
MIT — see LICENSE.
mark3labs/mcp-go — the MCP protocol library underneath every server here.modelcontextprotocol/servers — the TS/Python reference implementations these complement.Production-ready Model Context Protocol (MCP) servers in Go. Filesystem, PostgreSQL, Redis, shell, HTTP & Home Assistant. Embeddable as binaries or packages.
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Go MCP Servers 透過 stdio 在本機執行。
上次檢查時間:2026-10-28。 Production-ready Model Context Protocol (MCP) servers in Go. Filesystem, PostgreSQL, Redis, shell, HTTP & Home Assistant. Embeddable as binaries or packages.