code2mcp
Related Servers
Alternatives to code2mcp
No user-submitted related servers found.
Related Servers
TDQS
Scored across 1 tool
The single tool 'execute_code' has a clearly distinct purpose: executing TypeScript code with access to MCP tool APIs. Since there is only one tool, there is no ambiguity or overlap with other tools. The tool's description is specific and focused on code execution within a sandbox environment.
With only one tool named 'execute_code', naming consistency is inherently perfect. The tool follows a clear verb_noun pattern (execute_code), and there are no other tools to compare or create inconsistencies with.
The server has only one tool, which feels too thin for its apparent scope. The tool description mentions access to multiple MCP tool APIs (context7, playwright, chrome-devtools), suggesting a broader purpose of code execution with various integrations, but the tool surface is limited to a single generic execution tool. This could lead to agent confusion or inefficiency in handling specific tasks.
The server is severely incomplete for its implied domain. While 'execute_code' provides a generic execution capability, there are no dedicated tools for common operations like listing available APIs, managing the sandbox environment, or handling errors. The tool relies on embedded API calls within code, which may cause gaps in agent workflows and reduce usability for specific tasks.