In-depth architectural comparison of the Dazzle and Ctx MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Dazzle
Developer Tools · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Ctx
Developer Tools · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Dazzle if you need specialized Developer Tools tools running via a local process. Choose Ctx if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Dazzle when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Run a dazzle CLI command. Use ["--help"] to discover available commands. Output is JSON.
edit_file
Edit a file in the stage workspace by exact string replacement. The old_string must match exactly once in the file. Use read_file first to see the current content.
guide
Get the complete Dazzle reference — getting started, CLI commands, content capabilities, and streaming setup. Read this before creating or modifying stage content.
list_files
List all files in the stage workspace (~/.dazzle/stages/{stage}/). Returns relative paths, one per line.
read_file
Read a file from the stage workspace (~/.dazzle/stages/{stage}/{path}).
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Dazzle is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Ctx belongs to Developer Tools using local stdio subprocess. Select Dazzle when you need capabilities focused on developer tools and Ctx when you require tools for developer tools.
Capture a screenshot of the stage's current browser output. Returns a PNG image.
sync
Sync the stage workspace (~/.dazzle/stages/{stage}/) to the live stage. Run this after writing files to push content. Equivalent to 'dazzle stage sync {workspace-dir}'.
write_file
Write a file to the stage workspace (~/.dazzle/stages/{stage}/{path}). Creates parent directories as needed. Use this to build up content that can then be synced to the stage.
Ctx Tools (6)
pack_repo
The repo as one context blob with `==== path ====` headers + token estimate
search_context
Only the passages matching `query`, each with file, line and score
list_files
JSON: the text files ctx would include, with byte sizes
get_file
The full text of a single file
pack_docs
A crawled docs site as one context blob (each page → Markdown)
search_docs
Only the docs passages matching `query`, each with page URL, line and score