@lila-modeler/mcp 0.0.0-stage → 1.0.0-beta.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +202 -0
- package/NOTICE +15 -0
- package/README.md +71 -2
- package/bin/lila-mcp.js +15 -0
- package/dist/agent-tools.d.ts +15 -0
- package/dist/agent-tools.js +162 -0
- package/dist/bin.d.ts +3 -0
- package/dist/bin.js +10 -0
- package/dist/json-patch.d.ts +26 -0
- package/dist/json-patch.js +174 -0
- package/dist/scenario-input.d.ts +12 -0
- package/dist/scenario-input.js +40 -0
- package/dist/server.d.ts +18 -0
- package/dist/server.js +1077 -0
- package/package.json +52 -4
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/NOTICE
ADDED
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
Lila Modeler
|
|
2
|
+
Copyright 2026 Perfer Process
|
|
3
|
+
|
|
4
|
+
Licensed under the Apache License, Version 2.0 (see LICENSE).
|
|
5
|
+
|
|
6
|
+
Runtime dependencies are installed separately by npm and retain their own license files.
|
|
7
|
+
The wider project dependency inventory is available at:
|
|
8
|
+
https://github.com/AlambritoDito/lila-modeler/blob/main/THIRD_PARTY_LICENSES.md
|
|
9
|
+
|
|
10
|
+
The repository examples/bizagi-exports/ fixtures (not included in this package) come
|
|
11
|
+
from the BPMN MIWG test suite under CC BY 3.0. Their provenance is documented at:
|
|
12
|
+
https://github.com/AlambritoDito/lila-modeler/blob/main/examples/bizagi-exports/README.md
|
|
13
|
+
|
|
14
|
+
Bizagi and Bizagi Modeler are trademarks of Bizagi. Lila Modeler is an independent open-source
|
|
15
|
+
project, not affiliated with or endorsed by Bizagi.
|
package/README.md
CHANGED
|
@@ -1,3 +1,72 @@
|
|
|
1
|
-
#
|
|
1
|
+
# @lila-modeler/mcp
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
[MCP](https://modelcontextprotocol.io) server for [Lila Modeler](https://github.com/AlambritoDito/lila-modeler),
|
|
4
|
+
over stdio. It lets an AI agent model, validate, simulate and document BPMN processes with the same
|
|
5
|
+
engine as the app and the CLI ([`@lila-modeler/engine`](https://www.npmjs.com/package/@lila-modeler/engine)).
|
|
6
|
+
|
|
7
|
+
This is a beta. Node.js 22 or later.
|
|
8
|
+
|
|
9
|
+
## Run
|
|
10
|
+
|
|
11
|
+
```bash
|
|
12
|
+
npx -y @lila-modeler/mcp
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
The command starts the server and waits for an MCP client on stdin/stdout; it is meant to be
|
|
16
|
+
launched by the client, not used by hand. stdout carries only protocol messages; diagnostics go to
|
|
17
|
+
stderr.
|
|
18
|
+
|
|
19
|
+
## Client configuration
|
|
20
|
+
|
|
21
|
+
Claude Code:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
claude mcp add lila -- npx -y @lila-modeler/mcp
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
Claude Desktop (`claude_desktop_config.json`), Cursor and most other clients:
|
|
28
|
+
|
|
29
|
+
```json
|
|
30
|
+
{
|
|
31
|
+
"mcpServers": {
|
|
32
|
+
"lila": {
|
|
33
|
+
"command": "npx",
|
|
34
|
+
"args": ["-y", "@lila-modeler/mcp"],
|
|
35
|
+
"env": { "LILA_LANG": "en" }
|
|
36
|
+
}
|
|
37
|
+
}
|
|
38
|
+
}
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
Codex (`~/.codex/config.toml`):
|
|
42
|
+
|
|
43
|
+
```toml
|
|
44
|
+
[mcp_servers.lila]
|
|
45
|
+
command = "npx"
|
|
46
|
+
args = ["-y", "@lila-modeler/mcp"]
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Use an absolute path to `npx` when the client does not inherit your `PATH`. `LILA_LANG=es` (or
|
|
50
|
+
`LC_ALL`, `LC_MESSAGES`, `LANG`) picks Spanish messages; English is the default, and each tool also
|
|
51
|
+
accepts `locale: "en" | "es"`.
|
|
52
|
+
|
|
53
|
+
## Tools
|
|
54
|
+
|
|
55
|
+
Sixteen tools: `validate_bpmn`, `describe_process`, `run_simulation`, `compare_scenarios`,
|
|
56
|
+
`patch_scenario`, `create_process`, `get_process_outline`, `edit_process`, `export_diagram`,
|
|
57
|
+
`export_document`, `export_results`, `annotate_element`, `get_raci_matrix`,
|
|
58
|
+
`import_scenario_sheet`, `export_scenario_template`, `create_project`.
|
|
59
|
+
|
|
60
|
+
All file paths are read and written on the disk of the machine that runs the server; relative
|
|
61
|
+
paths resolve against the server's working directory, so prefer absolute paths. Simulation is
|
|
62
|
+
synchronous and there is no cancellation.
|
|
63
|
+
|
|
64
|
+
Tool contracts, examples and limits:
|
|
65
|
+
[docs/MCP.md](https://github.com/AlambritoDito/lila-modeler/blob/main/docs/MCP.md). The
|
|
66
|
+
[agent guide](https://github.com/AlambritoDito/lila-modeler/blob/main/docs/AGENT_GUIDE.md) walks an
|
|
67
|
+
agent through the whole flow: interview, outline, scenario, run and document.
|
|
68
|
+
|
|
69
|
+
## License
|
|
70
|
+
|
|
71
|
+
Apache-2.0. "Lila Modeler" and its logos are not covered by the license grant; see
|
|
72
|
+
[NOTICE](https://github.com/AlambritoDito/lila-modeler/blob/main/NOTICE).
|
package/bin/lila-mcp.js
ADDED
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
// Envoltorio del bin, igual al de @lila-modeler/engine: existe en el repositorio para que `npm install`
|
|
3
|
+
// cree `node_modules/.bin/lila-mcp` ya en la primera instalación, aunque `dist/` no exista todavía.
|
|
4
|
+
try {
|
|
5
|
+
await import('../dist/bin.js');
|
|
6
|
+
} catch (error) {
|
|
7
|
+
// Solo un módulo ausente significa "falta compilar"; cualquier otro fallo de arranque se
|
|
8
|
+
// reporta tal cual, o el usuario se queda compilando un paquete que ya estaba compilado.
|
|
9
|
+
console.error(
|
|
10
|
+
error?.code === 'ERR_MODULE_NOT_FOUND'
|
|
11
|
+
? 'lila-mcp: falta compilar el paquete. Ejecuta `npm run build` en la raíz del repo.'
|
|
12
|
+
: `lila-mcp: ${error instanceof Error ? error.message : String(error)}`,
|
|
13
|
+
);
|
|
14
|
+
process.exit(1);
|
|
15
|
+
}
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* The modelling tools of #99, #403 and #514: `annotate_element`, `get_raci_matrix`,
|
|
3
|
+
* `import_scenario_sheet`, `export_scenario_template` and `create_project`. Thin layers over
|
|
4
|
+
* `@lila-modeler/engine/project-fs`, like `lila process annotate|raci` and
|
|
5
|
+
* `lila scenario import|template`; registered by `createServer` (`server.ts`).
|
|
6
|
+
*
|
|
7
|
+
* As in the rest of the server, the schemas stay loose where a tighter one would make the SDK
|
|
8
|
+
* answer in English only (a RACI type, a scenario that is not an object): the engine refuses those
|
|
9
|
+
* in the caller's language, with nothing written.
|
|
10
|
+
*/
|
|
11
|
+
import type { Locale } from '@lila-modeler/engine/messages';
|
|
12
|
+
import type { McpServer } from '@modelcontextprotocol/server';
|
|
13
|
+
/** Registers the tools on `server`; `localeOf` turns a call's `locale` into the one to answer in. */
|
|
14
|
+
export declare function registerAgentTools(server: McpServer, localeOf: (locale: Locale | undefined) => Locale): void;
|
|
15
|
+
//# sourceMappingURL=agent-tools.d.ts.map
|
|
@@ -0,0 +1,162 @@
|
|
|
1
|
+
import { annotateLilaElement, createLilaProject, importLilaScenarioSheet, lilaRaciMatrix, lilaScenarioTemplate, writeExportFile, } from '@lila-modeler/engine/project-fs';
|
|
2
|
+
import { z } from 'zod';
|
|
3
|
+
function textResult(payload) {
|
|
4
|
+
return { content: [{ type: 'text', text: JSON.stringify(payload, null, 2) }], isError: false };
|
|
5
|
+
}
|
|
6
|
+
function failure(tool, error) {
|
|
7
|
+
return { content: [{ type: 'text', text: `${tool}: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
|
|
8
|
+
}
|
|
9
|
+
/** Registers the tools on `server`; `localeOf` turns a call's `locale` into the one to answer in. */
|
|
10
|
+
export function registerAgentTools(server, localeOf) {
|
|
11
|
+
const localeSchema = z
|
|
12
|
+
.enum(['en', 'es'])
|
|
13
|
+
.optional()
|
|
14
|
+
.describe('Language of the texts this call returns. Defaults to the server locale (LILA_LANG).');
|
|
15
|
+
const projectSchema = z.string().describe('Path to the .lila, relative to the cwd of the server process.');
|
|
16
|
+
const processSchema = z
|
|
17
|
+
.string()
|
|
18
|
+
.optional()
|
|
19
|
+
.describe('Slug of the process when the .lila holds several; implicit when it holds one.');
|
|
20
|
+
const dryRunSchema = z.boolean().optional().describe('Report what would change and write nothing.');
|
|
21
|
+
server.registerTool('annotate_element', {
|
|
22
|
+
title: 'Annotate element',
|
|
23
|
+
description: 'Writes the description, RACI responsibilities, catalog references and extended attribute ' +
|
|
24
|
+
'values of one element (task, event, gateway, flow, lane, pool, the process…) of a process ' +
|
|
25
|
+
'of a .lila, by its BPMN id, and saves the project atomically. `documentation` replaces ' +
|
|
26
|
+
'the description ("" removes it); `responsibilities` replaces the whole RACI list ([] ' +
|
|
27
|
+
'clears it); each kind in `refs` replaces that kind; `attributes` are merged by attribute ' +
|
|
28
|
+
'id or name ("" removes a value) and checked against the project\'s attribute definitions. ' +
|
|
29
|
+
'Writes where the app reads: a pool\'s description goes to the process it references ' +
|
|
30
|
+
'(`documentationOn`), and the RACI and references of a process inside a pool belong to ' +
|
|
31
|
+
'the pool (annotating them on the process is refused). Returns `before` and `after` as the ' +
|
|
32
|
+
'app shows the element; `dryRun` writes nothing. Like `lila process annotate`.',
|
|
33
|
+
inputSchema: z.object({
|
|
34
|
+
project: projectSchema,
|
|
35
|
+
process: processSchema,
|
|
36
|
+
elementId: z.string().describe('The BPMN id of the element.'),
|
|
37
|
+
documentation: z.string().optional().describe('The element\'s description; "" removes it.'),
|
|
38
|
+
responsibilities: z
|
|
39
|
+
.array(z.object({
|
|
40
|
+
type: z.string().describe('R, A, C or I.'),
|
|
41
|
+
roleRef: z.string().describe('The role, e.g. "cashier".'),
|
|
42
|
+
}))
|
|
43
|
+
.optional()
|
|
44
|
+
.describe('The whole RACI list of the element; [] clears it.'),
|
|
45
|
+
refs: z
|
|
46
|
+
.record(z.string(), z.array(z.string()))
|
|
47
|
+
.optional()
|
|
48
|
+
.describe('By kind (systemRef, documentRef, riskRef, controlRef, kpiRef, input, output): the ids it references.'),
|
|
49
|
+
attributes: z
|
|
50
|
+
.record(z.string(), z.string())
|
|
51
|
+
.optional()
|
|
52
|
+
.describe('Extended attribute values by attribute id or name; "" removes one.'),
|
|
53
|
+
dryRun: dryRunSchema,
|
|
54
|
+
locale: localeSchema,
|
|
55
|
+
}),
|
|
56
|
+
}, async ({ project, process, elementId, documentation, responsibilities, refs, attributes, dryRun, locale }) => {
|
|
57
|
+
try {
|
|
58
|
+
return textResult(await annotateLilaElement({
|
|
59
|
+
file: project, process, elementId, documentation, responsibilities, refs, attributes, dryRun, locale: localeOf(locale),
|
|
60
|
+
}));
|
|
61
|
+
}
|
|
62
|
+
catch (error) {
|
|
63
|
+
return failure('annotate_element', error);
|
|
64
|
+
}
|
|
65
|
+
});
|
|
66
|
+
server.registerTool('get_raci_matrix', {
|
|
67
|
+
title: 'Get RACI matrix',
|
|
68
|
+
description: 'The RACI matrix of a process of a .lila: `roles` (every roleRef, in order of appearance) ' +
|
|
69
|
+
'and `rows`, one per element with responsibilities, in the order of the process document ' +
|
|
70
|
+
'(id, name, lane, the raw `responsibilities` and `cells`: role -> "R", "A, C"…). Like ' +
|
|
71
|
+
'`lila process raci --json`.',
|
|
72
|
+
inputSchema: z.object({ project: projectSchema, process: processSchema, locale: localeSchema }),
|
|
73
|
+
}, async ({ project, process, locale }) => {
|
|
74
|
+
try {
|
|
75
|
+
return textResult(await lilaRaciMatrix({ file: project, process, locale: localeOf(locale) }));
|
|
76
|
+
}
|
|
77
|
+
catch (error) {
|
|
78
|
+
return failure('get_raci_matrix', error);
|
|
79
|
+
}
|
|
80
|
+
});
|
|
81
|
+
server.registerTool('import_scenario_sheet', {
|
|
82
|
+
title: 'Import scenario sheet',
|
|
83
|
+
description: 'Applies a scenario sheet (.xlsx, or a .csv/.txt table; the template of ' +
|
|
84
|
+
'`export_scenario_template`, docs/SCENARIO_SHEETS.md) to a scenario of a .lila, exactly ' +
|
|
85
|
+
'like the app\'s Import Excel/CSV: `changes` (each with before, after and a readable ' +
|
|
86
|
+
'`text`) and `issues` (rows not applied, notes, and `lint` errors the result would have). ' +
|
|
87
|
+
'The scenario is saved atomically unless `dryRun`, nothing changes, or there is a `lint` ' +
|
|
88
|
+
'issue (then it is an error and nothing is written). As in the app, the valid rows are ' +
|
|
89
|
+
'written even when other rows are not applied: read `issues` before calling the import ' +
|
|
90
|
+
'done. Like `lila scenario import`.',
|
|
91
|
+
inputSchema: z.object({
|
|
92
|
+
project: projectSchema,
|
|
93
|
+
process: processSchema,
|
|
94
|
+
scenario: z.string().describe('A scenario of the process: its file name (with or without .scenario.json) or its "name".'),
|
|
95
|
+
sheet: z.string().describe('Path to the .xlsx, .csv or .txt, relative to the cwd of the server process.'),
|
|
96
|
+
dryRun: dryRunSchema,
|
|
97
|
+
locale: localeSchema,
|
|
98
|
+
}),
|
|
99
|
+
}, async ({ project, process, scenario, sheet, dryRun, locale }) => {
|
|
100
|
+
try {
|
|
101
|
+
return textResult(await importLilaScenarioSheet({ file: project, process, scenario, sheet, dryRun, locale: localeOf(locale) }));
|
|
102
|
+
}
|
|
103
|
+
catch (error) {
|
|
104
|
+
return failure('import_scenario_sheet', error);
|
|
105
|
+
}
|
|
106
|
+
});
|
|
107
|
+
server.registerTool('export_scenario_template', {
|
|
108
|
+
title: 'Export scenario template',
|
|
109
|
+
description: 'Writes the scenario sheet of a scenario of a .lila as .xlsx (Elements, Arrivals, ' +
|
|
110
|
+
'Resources, Assignments, Calendars), filled in with its current values, like the app\'s ' +
|
|
111
|
+
'Download template: hand it to a person to fill in, then `import_scenario_sheet`. Never ' +
|
|
112
|
+
'overwrites an existing file unless `overwrite`. Like `lila scenario template`.',
|
|
113
|
+
inputSchema: z.object({
|
|
114
|
+
project: projectSchema,
|
|
115
|
+
process: processSchema,
|
|
116
|
+
scenario: z.string().describe('A scenario of the process: its file name or its "name".'),
|
|
117
|
+
saveTo: z.string().describe('Path of the .xlsx to write.'),
|
|
118
|
+
overwrite: z.boolean().optional().describe('Replace an existing file. Default false.'),
|
|
119
|
+
locale: localeSchema,
|
|
120
|
+
}),
|
|
121
|
+
}, async ({ project, process, scenario, saveTo, overwrite, locale }) => {
|
|
122
|
+
const language = localeOf(locale);
|
|
123
|
+
try {
|
|
124
|
+
const template = await lilaScenarioTemplate({ file: project, process, scenario, locale: language });
|
|
125
|
+
const file = writeExportFile(saveTo, template.data, { overwrite, source: template.file, locale: language });
|
|
126
|
+
return textResult({ file, project: template.file, process: template.process, scenario: template.scenario });
|
|
127
|
+
}
|
|
128
|
+
catch (error) {
|
|
129
|
+
return failure('export_scenario_template', error);
|
|
130
|
+
}
|
|
131
|
+
});
|
|
132
|
+
server.registerTool('create_project', {
|
|
133
|
+
title: 'Create project',
|
|
134
|
+
description: 'Creates a new .lila project from a BPMN model (inline XML, or a path to a .bpmn) and ' +
|
|
135
|
+
'optional scenarios, without the app; the web and desktop apps open it. A model with ' +
|
|
136
|
+
'validation errors is refused. Scenarios are saved as given (a scenario without `model` ' +
|
|
137
|
+
'or `extends` gets "model.bpmn"): each comes back with `runnable` and its `errors`, so a ' +
|
|
138
|
+
'draft is kept but flagged. Written atomically (no partial file on error); an existing ' +
|
|
139
|
+
'file is refused unless `overwrite`.',
|
|
140
|
+
inputSchema: z.object({
|
|
141
|
+
path: z.string().describe('Path of the new .lila, relative to the cwd of the server process.'),
|
|
142
|
+
name: z.string().describe('Name of the project.'),
|
|
143
|
+
bpmn: z.string().describe('BPMN 2.0 XML, or a path to a .bpmn.'),
|
|
144
|
+
scenarios: z
|
|
145
|
+
.array(z.object({
|
|
146
|
+
name: z.string().describe('Saved as <name>.scenario.json.'),
|
|
147
|
+
scenario: z.unknown().describe('The scenario JSON object (docs/SCENARIO_FORMAT.md).'),
|
|
148
|
+
}))
|
|
149
|
+
.optional(),
|
|
150
|
+
overwrite: z.boolean().optional().describe('Replace an existing file. Default false.'),
|
|
151
|
+
locale: localeSchema,
|
|
152
|
+
}),
|
|
153
|
+
}, async ({ path, name, bpmn, scenarios, overwrite, locale }) => {
|
|
154
|
+
try {
|
|
155
|
+
return textResult(await createLilaProject({ path, name, bpmn, scenarios, overwrite, locale: localeOf(locale) }));
|
|
156
|
+
}
|
|
157
|
+
catch (error) {
|
|
158
|
+
return failure('create_project', error);
|
|
159
|
+
}
|
|
160
|
+
});
|
|
161
|
+
}
|
|
162
|
+
//# sourceMappingURL=agent-tools.js.map
|
package/dist/bin.d.ts
ADDED
package/dist/bin.js
ADDED
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
/**
|
|
3
|
+
* Punto de entrada stdio del bin `lila-mcp`. `lila mcp` (LILA-056) llama a la misma función, pero
|
|
4
|
+
* pasando el idioma que resolvió de `--lang`; aquí no hay línea de comandos, así que sale del
|
|
5
|
+
* entorno con la misma regla (`LILA_LANG`, `LC_ALL`, `LC_MESSAGES`, `LANG`; inglés si no hay).
|
|
6
|
+
*/
|
|
7
|
+
import { resolveLocale } from '@lila-modeler/engine/messages';
|
|
8
|
+
import { startStdioServer } from './server.js';
|
|
9
|
+
await startStdioServer({ locale: resolveLocale(undefined, process.env) });
|
|
10
|
+
//# sourceMappingURL=bin.js.map
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* JSON Patch (RFC 6902) mínimo para `patch_scenario` (LILA-055): `add`/`replace`/`remove`/`test`
|
|
3
|
+
* sobre objetos y arrays planos, con punteros RFC 6901. Sin `move`/`copy` (ponytail): son las dos
|
|
4
|
+
* operaciones que leen de una ubicación distinta a la que escriben, duplicarían la navegación, y
|
|
5
|
+
* ningún caso de uso de `patch_scenario` las necesita — documentado en `docs/MCP.md`.
|
|
6
|
+
*
|
|
7
|
+
* También arma el delta mínimo de un patch, para el modo "crear escenario con `extends`" de
|
|
8
|
+
* `patch_scenario`: la ruta de cada operación, anidada, con una clave borrada traducida a `null`
|
|
9
|
+
* (mismo borrado que usa `extends`, `docs/SCENARIO_FORMAT.md` § 6) y un array tocado en cualquier
|
|
10
|
+
* profundidad reemplazado entero (los arrays no se fusionan por índice en `extends`).
|
|
11
|
+
*/
|
|
12
|
+
export interface JsonPatchOp {
|
|
13
|
+
op: string;
|
|
14
|
+
path: string;
|
|
15
|
+
value?: unknown;
|
|
16
|
+
from?: string | undefined;
|
|
17
|
+
}
|
|
18
|
+
/** Aplica el patch a una copia profunda de `target`; nunca muta el original. */
|
|
19
|
+
export declare function applyJsonPatch(target: unknown, patch: readonly JsonPatchOp[]): unknown;
|
|
20
|
+
/**
|
|
21
|
+
* Delta mínimo de un patch: solo las rutas que tocó alguna operación, leídas del documento **ya
|
|
22
|
+
* parcheado** (`patchedRoot`) para reflejar el estado final aunque varias operaciones compongan la
|
|
23
|
+
* misma ruta. Una clave que ya no existe en `patchedRoot` (un `remove`) se traduce a `null`.
|
|
24
|
+
*/
|
|
25
|
+
export declare function buildPatchDelta(patch: readonly JsonPatchOp[], patchedRoot: Record<string, unknown>): Record<string, unknown>;
|
|
26
|
+
//# sourceMappingURL=json-patch.d.ts.map
|