Structurizr DSL Debugger for Cursor MCP Server
@ViperJuice
基本情報
Structurizr DSL Debugger for Cursor MCP Server について
Mcp server to connect to structurizer dsl rendered in the browser and return error messages regarding parsing to Cursor IDE
Structurizr DSL Debugger for Cursor MCP Server の設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"Structurizr-DSL-Debug-MCP": {
"command": "docker",
"args": [
"run",
"-it",
"--rm",
"-p",
"8080:8080",
"-v",
"/path/to/workspace:/workspace",
"structurizr/lite"
]
}
}
}Structurizr DSL Debugger for Cursor MCP Server のツール
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
概要
What is Structurizr DSL Debugger for Cursor?
A specialized tool for debugging Structurizr DSL syntax issues in Cursor IDE. It integrates with Cursor via the Model Context Protocol (MCP) to provide real-time error detection, analysis, and fix suggestions for Structurizr DSL files.
How to use Structurizr DSL Debugger for Cursor?
Install dependencies via npm install and run npm run setup for Cursor integration. Start Structurizr Lite (e.g., Docker), launch Chrome with remote debugging (--remote-debugging-port=9222), then start the debugger with npm start (or with custom port via STRUCTURIZR_PORT). In Cursor, use MCP tools like connectToBrowser, getDslErrors, clearDslErrors, and fixDslError. A simplified version is available via node simplified-dsl-debugger.js with shorter tool names.
Key features of Structurizr DSL Debugger for Cursor
- Real-time error detection for Structurizr DSL files
- Intelligent suggested fixes for common DSL
「開発者ツール」の他のコンテンツ

GripForge
gripforgeaiThe tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

Leadpages MCP
LeadpagesLeadpages MCP is a remote MCP server available at https://mcp.leadpages.com.

LastPing
LastPingKnow when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

Routebase
RoutebaseRoutebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

Mcp-Warden
ermolukLocal-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.
コメント