@miragon/design-iq-mcp 5.3.0 → 5.5.0
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/README.md +4 -3
- package/dist/http.js +1 -1
- package/dist/server.js +1 -1
- package/dist/{tools-8vgJc4aD.js → tools-C47o0L3l.js} +10 -0
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -1,8 +1,9 @@
|
|
|
1
1
|
# @miragon/design-iq-mcp
|
|
2
2
|
|
|
3
|
-
designIQ's read-only MCP server: it exposes the models of a designIQ content repo
|
|
4
|
-
(
|
|
5
|
-
|
|
3
|
+
designIQ's read-only MCP server: it exposes the models of a designIQ content repo to any MCP
|
|
4
|
+
client (Claude Code, Claude Desktop, IDEs, ...): processes (BPMN), decisions (DMN), Wardley
|
|
5
|
+
Maps, Team Topologies, Event Storming boards, Context Maps, Value Chains and Markdown
|
|
6
|
+
documents, their diagrams as `mermaid` fences. A
|
|
6
7
|
content repo is a root `designiq.yml` naming its models folder (`models:`, legacy alias
|
|
7
8
|
`processes:`; the legacy file name `bpmiq.yml` is still read); a model IS a file with a
|
|
8
9
|
registered notation extension there (a process its `.bpmn`). Views are **derived from the
|
package/dist/http.js
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
|
-
import { n as createMcpServer, r as todosConfigFromEnv, t as DEFAULT_ROOT } from "./tools-
|
|
2
|
+
import { n as createMcpServer, r as todosConfigFromEnv, t as DEFAULT_ROOT } from "./tools-C47o0L3l.js";
|
|
3
3
|
import { createServer } from "node:http";
|
|
4
4
|
import { timingSafeEqual } from "node:crypto";
|
|
5
5
|
import { NodeStreamableHTTPServerTransport } from "@modelcontextprotocol/node";
|
package/dist/server.js
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
|
-
import { n as createMcpServer, r as todosConfigFromEnv, t as DEFAULT_ROOT } from "./tools-
|
|
2
|
+
import { n as createMcpServer, r as todosConfigFromEnv, t as DEFAULT_ROOT } from "./tools-C47o0L3l.js";
|
|
3
3
|
import { existsSync } from "node:fs";
|
|
4
4
|
import { resolve } from "node:path";
|
|
5
5
|
import { StdioServerTransport } from "@modelcontextprotocol/server/stdio";
|
|
@@ -1110,6 +1110,15 @@ const READ = {
|
|
|
1110
1110
|
readOnlyHint: true,
|
|
1111
1111
|
openWorldHint: false
|
|
1112
1112
|
};
|
|
1113
|
+
/**
|
|
1114
|
+
* Where a diagram goes: ONE text in both servers' instructions (the Live
|
|
1115
|
+
* Host's and the read-only server's), so the two never steer an assistant two
|
|
1116
|
+
* ways. A Mermaid diagram is a fence in a Markdown document; a process, a
|
|
1117
|
+
* decision or a model of any other notation is a model of its own (the
|
|
1118
|
+
* instructions list the notations just before this). It names no tool, so it
|
|
1119
|
+
* holds in every mode the instructions' drift tests run.
|
|
1120
|
+
*/
|
|
1121
|
+
const DIAGRAMS_IN_DOCUMENTS = "A Mermaid diagram (a diagram as code) goes into a Markdown document as a ```mermaid fence, next to the prose that explains it, never into a file of its own. A process, a decision, a Wardley Map or a model in any other notation above is a model of its own: link it from the document when the repository holds it (a relative link such as [Order to cash](order-to-cash.bpmn)), create it as a model when it does not, and never redraw it in Mermaid.";
|
|
1113
1122
|
//#endregion
|
|
1114
1123
|
//#region ../notations/derive.ts
|
|
1115
1124
|
/**
|
|
@@ -1591,6 +1600,7 @@ function readOnlyInstructions(on) {
|
|
|
1591
1600
|
return [
|
|
1592
1601
|
"designIQ is a Git-native workspace where teams model their business and their architecture together, live; this server reads one checkout of such a repository and never writes.",
|
|
1593
1602
|
`The repository keeps its models as files under the folder its designiq.yml names, one model per file with the file stem as its id, in these notations: ${NOTATION_FILES}.`,
|
|
1603
|
+
DIAGRAMS_IN_DOCUMENTS,
|
|
1594
1604
|
"Start with `list_models` to see which models it holds.",
|
|
1595
1605
|
"These tools are notation-neutral: `get_view` (the derived structure), `get_model` (the raw graph of nodes and edges), `enumerate_paths` and `find_cycles` (flow analysis where the notation has flow semantics) and `which_models_use` (which models reference a given one).",
|
|
1596
1606
|
"BPMN has deeper tooling: `list_processes`, `get_process` (the derived process view: roles, steps, flow, sub-process calls), `who_owns` (ownership from lanes) and `which_processes_use`" + (on.todos ? "; `list_todos` lists the open todos anchored to processes." : "."),
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@miragon/design-iq-mcp",
|
|
3
|
-
"version": "5.
|
|
3
|
+
"version": "5.5.0",
|
|
4
4
|
"description": "Read-only MCP server exposing a designIQ content repo's models — BPMN processes, DMN decisions, Wardley Maps, Team Topologies, Event Storming boards, Context Maps and more — to any MCP client. Discovered from designiq.yml, views derived from the models.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -44,16 +44,16 @@
|
|
|
44
44
|
"@modelcontextprotocol/server": "2.3.1",
|
|
45
45
|
"fast-xml-parser": "5.11.2",
|
|
46
46
|
"yaml": "2.9.1",
|
|
47
|
-
"zod": "4.6.
|
|
47
|
+
"zod": "4.6.7"
|
|
48
48
|
},
|
|
49
49
|
"devDependencies": {
|
|
50
50
|
"@modelcontextprotocol/client": "2.3.1",
|
|
51
|
-
"tsdown": "0.23.
|
|
52
|
-
"@designiq/contracts": "0.1.0",
|
|
53
|
-
"@designiq/notations": "0.1.0",
|
|
54
|
-
"@designiq/mcp-kit": "0.1.0",
|
|
51
|
+
"tsdown": "0.23.1",
|
|
55
52
|
"@designiq/github-app": "0.1.0",
|
|
56
|
-
"@designiq/
|
|
53
|
+
"@designiq/mcp-kit": "0.1.0",
|
|
54
|
+
"@designiq/http-kit": "0.1.0",
|
|
55
|
+
"@designiq/contracts": "0.1.0",
|
|
56
|
+
"@designiq/notations": "0.1.0"
|
|
57
57
|
},
|
|
58
58
|
"scripts": {
|
|
59
59
|
"start": "node server.ts",
|