📦 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
Voyei

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago