Visual Loop MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEBOX_URL | Yes | Base URL of your Judge0/Codebox instance | |
| CODEBOX_TOKEN | No | Auth token for the Codebox API (omit if no auth) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_and_renderA | Execute source code via Codebox (Judge0) for logic validation and render it as HTML in a headless browser via Playwright, returning the console output and a screenshot. Use this to write full-stack UI code and instantly verify both its logic and visual appearance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of ambiguity or confusion with other tools.
With a single tool, naming consistency is not a concern; the name 'execute_and_render' clearly describes its function.
One tool is on the lower end of reasonable count, but it serves a specific combined purpose of execution and rendering, which may justify the minimal surface.
The single tool covers both code execution and visual rendering, but lacks separate tools for execution-only or rendering-only tasks, limiting flexibility.