Onecompiler APIs MCP Server
Related Servers
Alternatives to Onecompiler APIs MCP Server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityBmaintenanceEnables dynamic creation and execution of custom tools/functions in multiple programming languages at runtime, exposing them to MCP clients like Claude.46 npm45MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to execute commands, edit files, run Git workflows, and perform validated independent reviews in real development environments through Docker-based runtimes with separated developer and auditor permissions.MIT
- AlicenseBqualityAmaintenanceBridges MCP clients to OpenCode's headless API, enabling AI to delegate autonomous coding tasks like building features, debugging, and refactoring across multiple projects.8723,279 npm138MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to compile, test, run, hot-swap, and debug Java applications incrementally through MCP, providing runtime feedback for verifying code changes.42MIT
- AlicenseNot gradedqualityBmaintenanceEnables developers to build, test, debug, and operate MCP servers from VS Code or CI, while also exposing trusted MCP capabilities to AI agents.MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'execute_code' has a clearly defined and distinct purpose.
The naming is trivially consistent as there is only one tool. It follows a clear verb_noun pattern ('execute_code'), which would be a good standard if more tools were added.
A single tool is too few for a server named 'Onecompiler APIs MCP Server', which suggests a broader scope related to code execution and possibly compilation APIs. This feels thin and under-scoped for the apparent domain.
The tool surface is severely incomplete for a compiler/execution API server. It lacks obvious operations like listing supported languages, getting code execution status or results separately, managing sessions, or handling compilation-specific tasks, which are typical in such domains.