📦 mcp-client-go

Created By
yincongcyinconga year ago
mcp client for Go (Golang). Integrate multiple Model Context Protocol (MCP) servers
Overview

What is mcp-client-go?

mcp-client-go is a Golang client library designed for the Model Context Protocol (MCP), enabling developers to integrate and interact with multiple MCP servers through a unified API.

How to use mcp-client-go?

To use mcp-client-go, install it via Go with the command go get github.com/yincongcyincong/mcp-client-go, and follow the provided examples to initialize clients and execute tools.

Key features of mcp-client-go?

  • Easy integration with various MCP-compatible services like Amap, GitHub, and Google Maps.
  • Modular support for different service types.
  • Unified registration and client management for seamless operations.
  • Intuitive interface for executing tools.

Use cases of mcp-client-go?

  1. Integrating with mapping services like Amap and Google Maps.
  2. Accessing and managing data from GitHub and other APIs.
  3. Automating tasks through browser automation with services like Puppeteer.

FAQ from mcp-client-go?

  • What is the Model Context Protocol (MCP)?

MCP is an open standard that allows AI systems to interact with various data sources and tools.

  • Is mcp-client-go free to use?

Yes! It is open-source and available under the MIT License.

  • How can I contribute to mcp-client-go?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yincongcyincong
Star
112
Language
Go
License
MIT 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)

2 days ago