intent-architect-mcp

Orchestrates Intent Architect MCP tools for model-driven design, code generation, and compilation verification.

23|10|Updated Aug 31, 2017
One-click install
npx skills add https://github.com/IntentArchitect/Intent.Modules --skill intent-architect-mcp-intentarchitect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: intent-architect-mcp
Source: https://github.com/IntentArchitect/Intent.Modules/tree/main/.opencode/skills/intent-architect-mcp
Command: npx skills add https://github.com/IntentArchitect/Intent.Modules --skill intent-architect-mcp-intentarchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with Intent Architect projects requires keeping visual models as the single source of truth while coordinating designer mutations, Software Factory runs, and code compilation. This Skill prevents common failure modes like hand-editing generated files, corrupting module manifests, or losing bespoke code during regeneration by enforcing a disciplined MCP-tool-driven workflow. ## Core Features & Use Cases - Model-First Workflow Enforcement: Routes all changes through Intent Architect MCP tools (run_designer_script, run_software_factory) instead of direct edits to .xml, .config, or .settings metadata files. - Phase-Based Server Skill Loading: Indexes the server-shipped skills (exploring-the-model, changing-the-model, generating-and-applying-code, and more) so the right operational guide is loaded before each phase of work. - Destructive Change Triage: Handles Software Factory changes flagged as destructive or unknown, guiding inspection of file diffs and model-based recovery rather than hand-restoring code. - Use Case: When adding a new DTO and endpoint to an Intent Architect application, the Skill bootstraps the session with get_status, loads the changing-the-model server skill, mutates the Services designer via run_designer_script, runs the Software Factory, and verifies the codebase compiles. ## Quick Start Ask the AI to add a new query and DTO to the Services designer of your Intent Architect application and run the Software Factory to apply the changes.

Frequently Asked Questions about intent-architect-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I modify an Intent Architect model with the MCP server?▼

Use run_designer_script after loading the changing-the-model server skill and calling get_designer_script_api for the authoritative scripting reference. The designer schema from get_designer_schema defines valid child element types, and changes persist only when the Software Factory runs.

What is the Intent Architect MCP workflow for generating code?▼

Load the generating-and-applying-code server skill, then call run_software_factory and inspect results with get_file_diffs using absolute paths. In staging mode, apply changes with apply_staged_file_changes; in write-through mode, changes are already on disk.

Can I edit Intent Architect .xml or .imodspec files directly?▼

Direct edits to .xml, .config, and .settings files in intent metadata folders are prohibited; changes must go through MCP tools so models stay the source of truth. The .imodspec is partially merged by the Software Factory, so only elements it never writes, like tags and authors, may be hand-edited.

Why does the Software Factory report destructive changes?▼

A destructive value of yes means a file was deleted or hand-written code was overwritten, while unknown means safety could not be verified. Load the resolve-destructive-changes server skill, inspect diffs with get_file_diffs, and reproduce losses through modelling rather than hand-restoring code.

How do I protect hand-written code from Intent Architect regeneration?▼

Apply [IntentIgnoreBody] to the member or [IntentManaged(Mode.Fully, Body = Mode.Ignore)] so the signature stays generated while the body is preserved. [IntentIgnore] protects an entire member or file, and [IntentManaged(Mode.Merge)] merges generated and hand-written content.

Why does install_or_update_modules fail in Intent Architect?▼

The target solution must be open before installing modules; call get_status, open the solution with open_solution using the absolutePath parameter, then retry. If it still fails after reopening, update the module from the Intent Architect UI Modules panel instead of editing modules.config.