@miraigent/free-ai-ops-mcp 0.1.4 → 0.1.6
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/CHANGELOG.md +20 -0
- package/LAUNCH_FLOW.md +21 -28
- package/README.md +10 -2
- package/mcp/free-ai-ops-server.mjs +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.1.6] - 2026-06-08
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
|
|
7
|
+
- Added a Tried It feedback issue template for users who run the MCP package and
|
|
8
|
+
want to report setup friction, unclear JSON-RPC input, or confusing output.
|
|
9
|
+
|
|
10
|
+
### Changed
|
|
11
|
+
|
|
12
|
+
- Added direct README links for Tried It feedback, workflow requests, and bug
|
|
13
|
+
reports so GitHub visitors have a clearer next action after running npx.
|
|
14
|
+
|
|
15
|
+
## [0.1.5] - 2026-06-07
|
|
16
|
+
|
|
17
|
+
### Changed
|
|
18
|
+
|
|
19
|
+
- Updated LAUNCH_FLOW.md so the package distribution route stays focused on
|
|
20
|
+
npm/GitHub developers and issue feedback.
|
|
21
|
+
- Removed remaining Agent Memories consumer routing from the npm package files.
|
|
22
|
+
|
|
3
23
|
## [0.1.4] - 2026-06-07
|
|
4
24
|
|
|
5
25
|
### Changed
|
package/LAUNCH_FLOW.md
CHANGED
|
@@ -2,8 +2,8 @@
|
|
|
2
2
|
|
|
3
3
|
This document defines the first public launch flow for Miraigent Free AI Ops MCP.
|
|
4
4
|
|
|
5
|
-
The goal is to distribute useful free MCP tools, collect public
|
|
6
|
-
and guide
|
|
5
|
+
The goal is to distribute useful free MCP tools to developers, collect public
|
|
6
|
+
GitHub issues, and guide implementation-heavy users toward Miraigent.
|
|
7
7
|
|
|
8
8
|
## Launch Position
|
|
9
9
|
|
|
@@ -21,7 +21,7 @@ The public promise is:
|
|
|
21
21
|
- keep CRM notes safer
|
|
22
22
|
- collect feedback in GitHub issues
|
|
23
23
|
- connect deeper implementation needs to Miraigent
|
|
24
|
-
-
|
|
24
|
+
- keep the npm package focused on developers who can run npm, npx, or MCP tools
|
|
25
25
|
|
|
26
26
|
## First Three MCPs
|
|
27
27
|
|
|
@@ -41,8 +41,8 @@ Why first:
|
|
|
41
41
|
|
|
42
42
|
Route:
|
|
43
43
|
|
|
44
|
-
GitHub free tool -> Issue feedback ->
|
|
45
|
-
|
|
44
|
+
GitHub/npm free tool -> Issue feedback -> developer adoption -> Miraigent free
|
|
45
|
+
diagnosis for company workflow design.
|
|
46
46
|
|
|
47
47
|
### 2. FAQ Candidate Review MCP
|
|
48
48
|
|
|
@@ -59,8 +59,8 @@ Why second:
|
|
|
59
59
|
|
|
60
60
|
Route:
|
|
61
61
|
|
|
62
|
-
GitHub free tool -> Qiita/Zenn example -> Miraigent resource hub -> free
|
|
63
|
-
diagnosis
|
|
62
|
+
GitHub/npm free tool -> Qiita/Zenn example -> Miraigent resource hub -> free
|
|
63
|
+
diagnosis for FAQ and inquiry-flow design.
|
|
64
64
|
|
|
65
65
|
### 3. AI-Safe CRM Notes MCP
|
|
66
66
|
|
|
@@ -77,8 +77,8 @@ Why third:
|
|
|
77
77
|
|
|
78
78
|
Route:
|
|
79
79
|
|
|
80
|
-
GitHub free tool ->
|
|
81
|
-
|
|
80
|
+
GitHub/npm free tool -> implementation article -> Miraigent free diagnosis for
|
|
81
|
+
real CRM/support workflow design.
|
|
82
82
|
|
|
83
83
|
### 4. Prompt Risk Review MCP
|
|
84
84
|
|
|
@@ -96,7 +96,7 @@ Why fourth:
|
|
|
96
96
|
|
|
97
97
|
Route:
|
|
98
98
|
|
|
99
|
-
GitHub free tool -> Issue feedback about missing risk flags -> Miraigent free
|
|
99
|
+
GitHub/npm free tool -> Issue feedback about missing risk flags -> Miraigent free
|
|
100
100
|
diagnosis for data-handling and review-rule design.
|
|
101
101
|
|
|
102
102
|
## Second Wave Candidates
|
|
@@ -162,19 +162,15 @@ Secondary URL:
|
|
|
162
162
|
|
|
163
163
|
https://miraigent.com/resources
|
|
164
164
|
|
|
165
|
-
### Step 4:
|
|
165
|
+
### Step 4: Developer Feedback Route
|
|
166
166
|
|
|
167
|
-
When a
|
|
168
|
-
|
|
167
|
+
When a developer wants another tool, output field, or review status, route them
|
|
168
|
+
to GitHub issues.
|
|
169
169
|
|
|
170
170
|
CTA language:
|
|
171
171
|
|
|
172
|
-
If
|
|
173
|
-
with
|
|
174
|
-
|
|
175
|
-
Primary URL:
|
|
176
|
-
|
|
177
|
-
https://agentmemories.jp/
|
|
172
|
+
If your AI agent or workflow needs another review field, open a public-safe
|
|
173
|
+
issue with the expected input and output.
|
|
178
174
|
|
|
179
175
|
## Posting Plan
|
|
180
176
|
|
|
@@ -250,20 +246,19 @@ CTA:
|
|
|
250
246
|
|
|
251
247
|
Use Prompt Risk Review MCP and open an issue if a risk flag is missing.
|
|
252
248
|
|
|
253
|
-
### Post 6:
|
|
249
|
+
### Post 6: Developer Feedback Bridge
|
|
254
250
|
|
|
255
251
|
Goal:
|
|
256
252
|
|
|
257
|
-
|
|
253
|
+
Turn developer use cases into public issues.
|
|
258
254
|
|
|
259
255
|
Hook:
|
|
260
256
|
|
|
261
|
-
If
|
|
262
|
-
memory.
|
|
257
|
+
If your AI agent needs a different review field, make the missing field public.
|
|
263
258
|
|
|
264
259
|
CTA:
|
|
265
260
|
|
|
266
|
-
Try the free MCP tools, then
|
|
261
|
+
Try the free MCP tools, then open an issue for missing fields or statuses.
|
|
267
262
|
|
|
268
263
|
## Suggested First Public Thread
|
|
269
264
|
|
|
@@ -323,10 +318,9 @@ https://miraigent.com/diagnosis
|
|
|
323
318
|
|
|
324
319
|
Post 6:
|
|
325
320
|
|
|
326
|
-
|
|
327
|
-
Agent Memories:
|
|
321
|
+
If your AI agent needs another review field, open a public-safe issue:
|
|
328
322
|
|
|
329
|
-
https://
|
|
323
|
+
https://github.com/Miraigent/miraigent-free-ai-ops-mcp/issues/new/choose
|
|
330
324
|
|
|
331
325
|
## Success Signals
|
|
332
326
|
|
|
@@ -338,7 +332,6 @@ Early signals:
|
|
|
338
332
|
- article views
|
|
339
333
|
- resource hub clicks
|
|
340
334
|
- free diagnosis clicks
|
|
341
|
-
- Agent Memories clicks
|
|
342
335
|
|
|
343
336
|
Do not over-optimize for stars only. Practical issues from real users are more
|
|
344
337
|
valuable.
|
package/README.md
CHANGED
|
@@ -32,10 +32,18 @@ https://miraigent.gumroad.com/l/human-review-gate-ai-drafts?utm_source=github&ut
|
|
|
32
32
|
## What To Do Next
|
|
33
33
|
|
|
34
34
|
- Try one tool with synthetic data.
|
|
35
|
-
-
|
|
35
|
+
- Share what happened in the Tried It feedback issue if setup, JSON-RPC input,
|
|
36
|
+
or the returned gate decision was unclear.
|
|
37
|
+
- Open a workflow request if a risk flag, status, or output field is missing.
|
|
36
38
|
- Use the Gumroad kit only if you want CSV/checklist files instead of npm.
|
|
37
39
|
- Adapt the review-gate fields before connecting private systems or real users.
|
|
38
40
|
|
|
41
|
+
Issue entry points:
|
|
42
|
+
|
|
43
|
+
- Tried It feedback: https://github.com/Miraigent/miraigent-free-ai-ops-mcp/issues/new?template=tried_it_feedback.md
|
|
44
|
+
- Workflow request: https://github.com/Miraigent/miraigent-free-ai-ops-mcp/issues/new?template=free_mcp_candidate_request.md
|
|
45
|
+
- Bug report: https://github.com/Miraigent/miraigent-free-ai-ops-mcp/issues/new?template=free_mcp_bug_report.md
|
|
46
|
+
|
|
39
47
|
## Alpha Tools
|
|
40
48
|
|
|
41
49
|
- human_review_gate: decide whether an AI draft should be sent, reviewed, or stopped.
|
|
@@ -87,7 +95,7 @@ decision log that match the free Gumroad kit.
|
|
|
87
95
|
## Launch Flow
|
|
88
96
|
|
|
89
97
|
See LAUNCH_FLOW.md for the first public posting plan, issue collection flow, and
|
|
90
|
-
|
|
98
|
+
developer-focused distribution route.
|
|
91
99
|
|
|
92
100
|
## Run
|
|
93
101
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@miraigent/free-ai-ops-mcp",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.6",
|
|
4
4
|
"description": "Free MCP server for developers adding human review gates, prompt risk checks, FAQ review, and CRM note safety to AI tools.",
|
|
5
5
|
"homepage": "https://github.com/Miraigent/miraigent-free-ai-ops-mcp",
|
|
6
6
|
"type": "module",
|