MCP Go SDK

Created By
SetiabudiResearcha year ago
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
Overview

What is MCP Go SDK?

MCP Go SDK is a software development kit that 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.

How to use MCP Go SDK?

To use MCP Go SDK, install it via Go package manager with go get github.com/SetiabudiResearch/mcp-go-sdk, and follow the usage guide to create servers, add tools, resources, and configure transports.

Key features of MCP Go SDK?

  • Multiple transport options (stdio, SSE, WebSocket)
  • Bidirectional communication capabilities
  • Tool registration and execution
  • Resource pattern matching and access
  • Prompt template rendering and session management

Use cases of MCP Go SDK?

  1. Building a file server that handles file access requests.
  2. Creating a calculator service that processes mathematical operations.
  3. Developing a chat bot that interacts with users through prompts.

FAQ from MCP Go SDK?

  • Is MCP Go SDK easy to integrate into existing Go applications?

Yes! MCP Go SDK is designed to be easily integrated into any Go application with minimal setup.

  • What transport options are available?

MCP Go SDK supports stdio, WebSocket, and Server-Sent Events for flexible communication.

  • Can I contribute to the MCP Go SDK?

Absolutely! Contributions are welcome, and you can submit a Pull Request on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
SetiabudiResearch
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 minutes ago