mcpc
A Model Context Protocol (MCP) client — library and CLI — written in Go with
zero third-party dependencies. It connects to any MCP server over stdio
(launching it as a child process) or HTTP, and is the paired client for
mcpkit.
Power your agent
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
A Model Context Protocol (MCP) client — library and CLI — written in Go with
zero third-party dependencies. It connects to any MCP server over stdio
(launching it as a child process) or HTTP, and is the paired client for
mcpkit.
Zero-dependency Model Context Protocol (MCP) client for Go — library + CLI, over stdio or HTTP. Paired client for mcpkit.
There is an official MCP Go SDK, and for most production clients it's the right choice. mcpc is a deliberate alternative — a from-scratch, zero-dependency implementation built to make the interesting part legible: the concurrency.
One connection, many in-flight requests, responses arriving out of order, plus
server-initiated notifications. mcpc solves this with a single background read
loop that demultiplexes responses to their waiting callers by request id — so you
can fan out calls from as many goroutines as you like, with per-call timeouts and
cancellation that propagates to the server as notifications/cancelled. It's all
on the standard library, so the read loop and the cancellation plumbing are here
to read, not hidden behind a dependency.
2025-06-18: initialize handshake, tools,
resources, prompts, logging and cancellation.pending map keyed by
id, and first-class context timeouts.CallToolRetry with exponential backoff, a ProgressTracker
for streaming progress, and a Pool of server processes for CPU-bound work.ping, tools, describe, call, run and an interactive
repl.${1} feeds one step's result into the next).mcpkit.# Build the CLI
make build
# List a server's tools (launches mcpkit as a child process)
mcpc -server mcpkit tools
# Call a tool
mcpc -server mcpkit call calculate expression="2 ^ 10 + sqrt(81)"
# Run a scripted plan
mcpc -server mcpkit run examples/plan.json
# Interactive session
mcpc -server mcpkit repl
Against a running HTTP gateway instead:
mcpc -http http://localhost:8080/rpc ping
ctx := context.Background()
c, info, err := client.DialCommand(ctx, "mcpkit", nil)
if err != nil {
log.Fatal(err)
}
defer c.Close()
tools, _ := c.ListTools(ctx)
res, _ := c.CallTool(ctx, "calculate", map[string]string{"expression": "6*7"})
fmt.Println(res.Content[0].(mcp.TextContent).Text) // 42
cmd/mcpc/ the command-line client
client/ the reusable client: read loop, retry, progress, pool
agent/ scripted plan parser and runner with output chaining
transport/ subprocess, HTTP and in-memory pipe transports
mcp/ MCP protocol types
jsonrpc/ JSON-RPC 2.0 core
internal/ config, logging, metrics, version
docs/ architecture, protocol, cli, library, transports, agent
examples/ a library example and sample plans
mcpc is developed alongside the mcpkit
server. Build mcpkit and point the live integration test at it:
go build -o /tmp/mcpkit github.com/adam-eques/mcpkit/cmd/mcpkit
MCPKIT_BIN=/tmp/mcpkit go test ./client -run TestLiveServer
MIT — see LICENSE.
Zero-dependency Model Context Protocol (MCP) client for Go — library + CLI, over stdio or HTTP. Paired client for mcpkit.
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Mcpc runs locally over stdio.
Last checked 2026-10-27. Zero-dependency Model Context Protocol (MCP) client for Go — library + CLI, over stdio or HTTP. Paired client for mcpkit.