What transports does the MCP Go SDK support?
It supports stdio, WebSocket, and Server-Sent Events (SSE) transports, each configurable with endpoints and settings.
@SetiabudiResearch
Basic information
This SDK provides a Go implementation of the Machine Control Protocol (MCP), enabling bidirectional communication between clients and servers for tool execution, resource access, and prompt handling. Based on
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
The MCP Go SDK provides a Go implementation of the Model Context Protocol (MCP), enabling bidirectional communication between clients and servers for tool execution, resource access, and prompt handling. It is designed for Go developers building MCP-compatible applications.
Install the SDK with go get github.com/SetiabudiResearch/mcp-go-sdk. Then create a server instance using server.NewServer(), add tools, resources, or prompts using the provided methods, and start a transport (stdio, WebSocket, or SSE). See the Quick Start section for a minimal example.
files/{path})It supports stdio, WebSocket, and Server-Sent Events (SSE) transports, each configurable with endpoints and settings.
Use `srv.AddTool()` for synchronous tools or `srv.AddAsyncTool()` for long-running operations, providing a name, handler function, and description.
The SDK depends only on the Go standard library and the module itself; it is a pure Go implementation.
Yes, resources support pattern matching like `files/{path}` or `api/{version}/{endpoint}` with multiple parameters.
Yes, the repository contains an `examples` directory with a file server, calculator, and chatbot examples.

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.
Set up and manage the Eddyter AI rich text editor by talking to your AI agent — for Claude, Cursor, Codex and other MCP tools. A Model Context Protocol server that lets AI tools add Eddyter to a React, Next.js, Vite or R

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.
Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up
CronWatch records every run of your scheduled jobs in your own database, and speaks up when one is missed, fails, gets stuck, runs slow or costs too much. CronWatch is free and open-source.
Comments