Go Playground MCP Server
Related Servers
Alternatives to Go Playground MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides Go language tools for LLMs to analyze, test, and format Go code.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables compiling source code and exploring assembly outputs via the Godbolt Compiler Explorer API. Supports multiple languages, compilers, and optimization levels.5MIT
- AlicenseNot gradedqualityDmaintenanceProvides real-time access to Go package documentation, function signatures, and type definitions directly from pkg.go.dev. It enables LLMs to search for packages, retrieve specific versions, and access code examples from the official Go module ecosystem.7 npm2MIT

sandboxapi-mcpofficial
AlicenseNot gradedqualityFmaintenanceExecute code in 8 programming languages via gVisor-sandboxed Docker containers. Supports Python, JS, TS, Go, Java, C++, C, and Bash.2MIT- AlicenseNot gradedqualityDmaintenanceEnables secure cloud-based execution of code across 14+ programming languages within a sandboxed environment. It supports file management, standard input/output handling, and automatic generation of visual artifacts like plots and charts.MIT
- FlicenseNot gradedqualityDmaintenanceEnables execution of code in a sandbox environment with integrated web search capabilities. Provides a basic framework for running code safely, primarily designed for AI agents and research applications.13-
TDQS
Scored across 5 tools
Most tools have clear distinct purposes: run_go_code executes provided code, share_go_code returns a URL, read_go_playground_url fetches code from a URL, and execute_go_playground_url runs code from a URL. The only potential confusion is between run_go_code and run_and_share_go_code, since the latter is a superset that also shares, but this is explicitly described.
Tool names follow a consistent verb_noun pattern (run, share, read, execute) and clearly reference the object (go_code or go_playground_url). Minor inconsistency exists between 'go_code' and 'go_playground_url' but it is not confusing, and the compound 'run_and_share_go_code' remains readable.
Five tools is well-scoped for a Go Playground server. Each tool covers a distinct interaction mode (run, share, read from URL, execute from URL, and combined run+share) without redundancy or bloat.
The tool set covers the essential Go Playground workflows: running code, sharing code, retrieving code from a URL, executing code from a URL, and a combined convenience tool. No obvious gaps exist for the stated purpose.