go-common-mcp-server
v1.0.14
Published
MCP server for browsing go-common modules, examples, and documentation.
Maintainers
Readme
go-common MCP Server
MCP server for browsing the modules, examples, source files, and documentation in thanhbvha/go-common.
Run
npx -y go-common-mcp-serverMCP client configuration:
{
"mcpServers": {
"go-common": {
"command": "npx",
"args": ["-y", "go-common-mcp-server"]
}
}
}Tools
list_modules: list root Go modules.list_examples: list runnable examples.list_module_files: list indexed files for a module.list_example_files: list indexed files for an example.read_module_file: fetch an indexed module file from GitHub.read_example_file: fetch an indexed example file from GitHub.
Example files are indexed recursively. Tools can therefore list and read root files such as main.go and README.md, nested Go files such as client/main.go and internal/exampleconfig/config.go, and supported configuration files such as .env, config.yaml, and JSON files.
The file registry is regenerated and validated during npm run build, npm pack, and npm publish, so each package release indexes the source tree from the matching repository release. This includes the current EventBus core, transports, drivers, runnable examples, tests, documentation, and configuration files, as well as the WebSocket core, adapters, broker implementations, tests, documentation, load generator, and configuration examples.
Source Availability
File reads use the main branch of the GitHub repository. Publish the matching repository commit before publishing this npm package so every indexed path is available remotely.
1.0.14 source update
The registry includes source changes through go-common v1.11.0:
- Verified-TLS gRPC clients, streaming interceptors, bounded shutdown and Foundation wiring.
- Separate server/client/foundation/certgen examples with YAML/env configuration.
- Renamed examples
grpcandgraphql, including regenerated protocol code and docs. - Bounded GraphQL HTTP runtime and request-scoped loaders from
v1.10.0.
Private *.local.yaml / *.local.yml files are excluded from the generated registry.
Use list_example_files with example_name: "grpc" or "graphql" for the new paths.
1.0.13 source update
The registry includes database changes through go-common v1.9.0:
- PostgreSQL, MySQL/InnoDB, and SQLite ORM backend adapters and capability contracts.
- Guarded transactions, bounded repositories, admission, lifecycle, and telemetry.
- Fourteen SQL demos and updated English database documentation.
- MongoDB production APIs and examples introduced in go-common
v1.8.0.
Use list_module_files with module_name: "db" and list_example_files with
example_name: "db" or "db_mongodb" to discover these files.
1.0.12 source update
The registry includes the WebSocket changes through go-common v1.7.2:
- Targeted routing, Redis session registry fast paths, Redis/NATS delivery, and the EventBus bridge.
- Gateway lease renewal, reconnect fencing, bounded unregister retries, shutdown cleanup, and regression tests.
- Resolve/Register/Renew benchmark documentation and the Redis fast-path A/B report under
websocket/benchmarks/. Raw.txtoutput is outside the supported file extensions. - Cluster gateway configuration, authenticated aggregate stats, and
config.loadtest.yaml. - Loadtest ping/pong, stable reconnect sessions, group fanout, configurable rates, and client receipt validation.
Use list_module_files with module_name: "websocket" to discover routing and
benchmark files. Use list_example_files with example_name: "websocket" to
discover the cluster, loadtest and configuration files, then read them with the
corresponding read_*_file tool. The 1,000-connection profile is a test setup,
not a measured production capacity guarantee.
Local verification
From the repository root:
npm --prefix mcp run build
npm --prefix mcp test
npm pack ./mcp --dry-runThe build regenerates src/registry.ts before compiling build/. Validation
checks the recursive example inventory, required WebSocket release files, and
version consistency between the package, lockfile and MCP handshake metadata.
An already-running MCP process must be restarted to load the rebuilt registry.
