Skip to content

FOUR-34328: [EPIC] Processmaker MCP - #18

Draft
pmPaulis wants to merge 26 commits into
masterfrom
feature/FOUR-34328
Draft

pmPaulis wants to merge 26 commits into
masterfrom
feature/FOUR-34328

Conversation

@pmPaulis

Copy link
Copy Markdown

No description provided.

caleeli and others added 22 commits February 27, 2024 18:45
Reorder create-project wizard so option 1 and option 2 share ProcessMaker
URL, API token, and MCP endpoints (processes + screens).

Write .mcp.json, .cursor/mcp.json, .env.example, and optional .env from
NAYRA_SERVER / PM_SYNC_TOKEN. Scaffold migration dirs and docs for option 1.

https://processmaker.atlassian.net/browse/FOUR-34377
…ills

Expose deploy-script, deploy-screen, and deploy-process endpoints on the
generated package (plus pull helpers). Port BPMN portable ref resolution from
package-plg, ship .agents upsert skills, feature tests, and document publish
order in README and migration AGENTS.

https://processmaker.atlassian.net/browse/FOUR-34377
feat(FOUR-34377): align migration with shared MCP and PM4 target config
docs: decouple from PLG; restore screen/custom-vue patterns with package slug.
feat(rename): preserve upsert skills after npx skills install.
feat: add Shared domain Model and ValidatesWithJsonSchema with swaggest.

https://processmaker.atlassian.net/browse/FOUR-34392
fix(FOUR-34392): align agents, hexagonal base, and create-project wizard
Remove deploy controllers, services, feature tests, and package routes. Point upsert skills and docs at core /api/1.0/deploy-*; keep package-skeleton BC aliases documented.

https://processmaker.atlassian.net/browse/FOUR-34395
refactor(FOUR-34395): move deploy sync APIs to ProcessMaker core
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants