Provides tools to list Go module versions, retrieve the latest version, fetch version metadata, and get raw go.mod files from Google's Go module proxy (proxy.golang.org).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@pkg-go-dev list versions of gorilla/mux"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Go modules MCP — version list + metadata for any importable Go module. No auth.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
list_versions(module_path) — all tagged versions
latest_version(module_path) — most recent version
get_module_info(module_path, version) — version metadata
get_go_mod(module_path, version) — raw go.mod file
Related MCP server: mcp-golang-server
https://proxy.golang.org/ — the official Google-run Go module proxy. Returns text/json.
Module paths are import paths (e.g. github.com/gin-gonic/gin, golang.org/x/net).
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"pkg-go-dev": {
"url": "https://gateway.pipeworx.io/pkg-go-dev/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/pkg-go-dev/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Pkg Go Dev data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Go module proxy — module info, versions, go.mod
Go vulns: CVEs per module, fixed versions. $0.01/query. Register in-session — free testnet funds.
deps.dev — Google's package metadata + dependency graph API
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
