Repository navigation
[Feature]: MCP Server Mode (Headless + Tool Exposure) #274
Description
Enable Open CoDesign to run as a Model Context Protocol (MCP) server, so it can be used by external MCP clients.
🎯 Motivation
It would be highly valuable to support server mode, enabling:
- Integration with external MCP clients (Claude, custom agents)
- Automated design workflows
- Headless usage in pipelines
🧠 Proposed Solution
Add a CLI flag to run as MCP server:
open-codesign --mcp-server
Expose tools like:
- generate_design
- update_component
- export_html
- export_react
💡 Use Cases
- AI agents generating UI automatically
- CI/CD pipelines generating pages
- Integration with MCP ecosystem
🙋 Willing to contribute
Happy to help design or test this feature.
Proposed solution
🧠 Proposed Solution
Add a CLI flag to run as MCP server:
open-codesign --mcp-server
Expose tools like:
generate_design
update_component
export_html
export_react
🔌 Example MCP Config
{
"mcpServers": {
"open-codesign": {
"command": "uvx",
"args": [Here Argument]
}
}
}
Alternatives considered
No response
Scope
Provider / model
Hard-constraints check
- I have read the hard constraints in AGENTS.md or CLAUDE.md, and this proposal does not conflict with any of them.
Activity
github-actions commentedon May 2, 2026
Thank you for the detailed feature request! Adding an MCP server mode is an interesting idea that aligns with the v0.2 direction of exposing Open CoDesign's agentic tools programmatically.
What we've verified from the codebase:
pi-agent-coreandpi-aias the agent runtime (packages/coredepends on@mariozechner/pi-agent-coreand@mariozechner/pi-ai). PerCLAUDE.md/AGENTS.mdhard constraint feat(exporters): real PDF/PPTX/ZIP via system Chrome + pptxgenjs + zip-lib (lazy-loaded) #7, we should reuse pi primitives where possible. This means any MCP server should ideally delegate tool execution to pi's existing built-in tools and Open CoDesign's design tools (ask,scaffold,preview,gen_image,tweaks,todos,done) rather than duplicating logic.apps/desktopis an Electron app, and there's no existing--mcp-serverflag. This would be a new addition, likely as a separate entry point or package.generate_design,update_component,export_html,export_react) map roughly to existing design tools, but the exact mapping would need design.A few questions to help scope the implementation:
uvxconfig example) or HTTP/SSE? Both are valid MCP transports.ask,scaffold,preview,gen_image,tweaks,todos,done) or a curated subset focused on generation/export?apps/desktop(enabled via flag) or as a separate package (e.g.,packages/mcp-server) that can be installed independently?We're happy to review a concrete design or prototype if you'd like to contribute further. Thanks again for the thoughtful proposal!
Open-CoDesign Bot
feat: add agent-native CLI and background UI sessions (#510)