@miraigent/free-ai-ops-mcp 0.1.8 → 0.1.11
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 +25 -0
- package/README.md +59 -3
- package/examples/faq-candidate-review/README.md +33 -0
- package/examples/faq-candidate-review/run-example.mjs +28 -0
- package/examples/faq-candidate-review/sample-request.jsonl +1 -0
- package/examples/mcp-json-rpc-session/README.md +35 -0
- package/examples/mcp-json-rpc-session/sample-session.jsonl +3 -0
- package/mcp/free-ai-ops-server.mjs +1 -1
- package/package.json +2 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,30 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.1.11] - 2026-06-15
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
|
|
7
|
+
- Added a copy-ready faq_candidate_review example so developers can test the
|
|
8
|
+
repeated-support-question to FAQ candidate path before opening workflow
|
|
9
|
+
requests or connecting private support data.
|
|
10
|
+
|
|
11
|
+
## [0.1.10] - 2026-06-14
|
|
12
|
+
|
|
13
|
+
### Changed
|
|
14
|
+
|
|
15
|
+
- Added a README tool picker so npm/GitHub visitors can choose the first MCP
|
|
16
|
+
tool by workflow risk before opening issues or integrating the package.
|
|
17
|
+
|
|
18
|
+
## [0.1.9] - 2026-06-13
|
|
19
|
+
|
|
20
|
+
### Added
|
|
21
|
+
|
|
22
|
+
- Added a copy-ready JSON-RPC MCP session example so developers can verify
|
|
23
|
+
initialize, tools/list, and a human_review_gate call before integrating with a
|
|
24
|
+
desktop MCP client.
|
|
25
|
+
- Added README guidance for using the session example as a public-safe smoke
|
|
26
|
+
test when opening GitHub issues.
|
|
27
|
+
|
|
3
28
|
## [0.1.8] - 2026-06-12
|
|
4
29
|
|
|
5
30
|
### Added
|
package/README.md
CHANGED
|
@@ -16,8 +16,20 @@ Run the public MCP server:
|
|
|
16
16
|
Then send a JSON-RPC tool call such as the copy-ready example in
|
|
17
17
|
examples/human-review-gate/.
|
|
18
18
|
|
|
19
|
-
|
|
20
|
-
|
|
19
|
+
For a complete public-safe MCP session that covers initialize, tools/list, and
|
|
20
|
+
one tool call, see examples/mcp-json-rpc-session/.
|
|
21
|
+
|
|
22
|
+
If the result is unclear, open a Tried It feedback issue with synthetic input
|
|
23
|
+
only. A useful issue can be as small as:
|
|
24
|
+
|
|
25
|
+
- the tool you ran
|
|
26
|
+
- the returned status or field that was confusing
|
|
27
|
+
- the review rule, risk flag, or example that would make the next run easier
|
|
28
|
+
|
|
29
|
+
https://github.com/Miraigent/miraigent-free-ai-ops-mcp/issues/new?template=tried_it_feedback.md
|
|
30
|
+
|
|
31
|
+
If you are not a developer and only want the spreadsheet/checklist version after
|
|
32
|
+
seeing the MCP example, download the free review kit:
|
|
21
33
|
|
|
22
34
|
https://miraigent.gumroad.com/l/human-review-gate-ai-drafts?utm_source=github&utm_medium=readme&utm_campaign=free-ai-ops-mcp-013
|
|
23
35
|
|
|
@@ -51,13 +63,36 @@ Claude Desktop config location:
|
|
|
51
63
|
- Teams prototyping human-in-the-loop AI workflows before integrating real data.
|
|
52
64
|
- Operators who can run npm/npx and want a small public MCP example.
|
|
53
65
|
|
|
66
|
+
## Pick Your First Tool
|
|
67
|
+
|
|
68
|
+
Start with the tool that matches the first unsafe handoff in your workflow:
|
|
69
|
+
|
|
70
|
+
- AI draft may reach a customer: use `human_review_gate`.
|
|
71
|
+
- Repeated support questions should become a public FAQ: use
|
|
72
|
+
`faq_candidate_review`.
|
|
73
|
+
- CRM notes mix facts, AI suggestions, and human decisions: use
|
|
74
|
+
`ai_safe_crm_note`.
|
|
75
|
+
- A prompt may touch customer data or public output: use `prompt_risk_review`.
|
|
76
|
+
|
|
77
|
+
Copy-ready examples:
|
|
78
|
+
|
|
79
|
+
- Human review gate: `npm run example:human-review-gate`
|
|
80
|
+
- FAQ candidate review: `npm run example:faq-candidate-review`
|
|
81
|
+
- Prompt risk review: `npm run example:prompt-risk-review`
|
|
82
|
+
|
|
83
|
+
All examples use synthetic data. Keep private customer records, secrets,
|
|
84
|
+
internal policy text, and paid product files out of public issues and screenshots.
|
|
85
|
+
|
|
54
86
|
## What To Do Next
|
|
55
87
|
|
|
56
88
|
- Try one tool with synthetic data.
|
|
89
|
+
- If you ran `npx @miraigent/free-ai-ops-mcp`, paste the public-safe result
|
|
90
|
+
shape into the Tried It feedback issue.
|
|
57
91
|
- Share what happened in the Tried It feedback issue if setup, JSON-RPC input,
|
|
58
92
|
or the returned gate decision was unclear.
|
|
59
93
|
- Open a workflow request if a risk flag, status, or output field is missing.
|
|
60
|
-
- Use the Gumroad kit
|
|
94
|
+
- Use the Gumroad kit after the MCP example if you want CSV/checklist files
|
|
95
|
+
instead of npm.
|
|
61
96
|
- Adapt the review-gate fields before connecting private systems or real users.
|
|
62
97
|
|
|
63
98
|
Issue entry points:
|
|
@@ -114,6 +149,23 @@ Use this as a small public proof before building a larger AI support workflow.
|
|
|
114
149
|
See examples/human-review-gate/ for copy-ready JSON-RPC examples and a sample
|
|
115
150
|
decision log that match the free Gumroad kit.
|
|
116
151
|
|
|
152
|
+
## Copy-Ready MCP Session
|
|
153
|
+
|
|
154
|
+
Use this when you want to confirm the package responds like an MCP server before
|
|
155
|
+
connecting it to Claude Desktop, Cursor, or your own MCP client:
|
|
156
|
+
|
|
157
|
+
npm run mcp < examples/mcp-json-rpc-session/sample-session.jsonl
|
|
158
|
+
|
|
159
|
+
The session sends three JSON-RPC messages:
|
|
160
|
+
|
|
161
|
+
- initialize: confirms protocolVersion, capabilities, and serverInfo.
|
|
162
|
+
- tools/list: confirms the four public alpha tools are visible.
|
|
163
|
+
- tools/call: runs human_review_gate with synthetic support-reply data.
|
|
164
|
+
|
|
165
|
+
If you open a GitHub issue, copy only synthetic input shapes and returned status
|
|
166
|
+
fields. Do not paste private customer records, secrets, tokens, internal policy
|
|
167
|
+
text, or MIRAI Memory behavior.
|
|
168
|
+
|
|
117
169
|
## Check A Prompt Before AI Use
|
|
118
170
|
|
|
119
171
|
Use prompt_risk_review before a support, CRM, FAQ, or workflow prompt is sent to
|
|
@@ -173,6 +225,10 @@ Run the prompt risk review example:
|
|
|
173
225
|
|
|
174
226
|
npm run example:prompt-risk-review
|
|
175
227
|
|
|
228
|
+
Run the FAQ candidate review example:
|
|
229
|
+
|
|
230
|
+
npm run example:faq-candidate-review
|
|
231
|
+
|
|
176
232
|
## npm Package
|
|
177
233
|
|
|
178
234
|
Package name: @miraigent/free-ai-ops-mcp
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# FAQ Candidate Review Example
|
|
2
|
+
|
|
3
|
+
This example shows how to call the public faq_candidate_review MCP tool when a
|
|
4
|
+
support question keeps repeating.
|
|
5
|
+
|
|
6
|
+
Use it before turning repeated inquiry patterns into a public FAQ, internal FAQ,
|
|
7
|
+
or human-review rule.
|
|
8
|
+
|
|
9
|
+
## Run
|
|
10
|
+
|
|
11
|
+
From the repository root:
|
|
12
|
+
|
|
13
|
+
npm run example:faq-candidate-review
|
|
14
|
+
|
|
15
|
+
The example sends sample-request.jsonl to the MCP server and prints the
|
|
16
|
+
faq_candidate_review result.
|
|
17
|
+
|
|
18
|
+
## What To Look For
|
|
19
|
+
|
|
20
|
+
The sample uses a low-risk pricing-plan question, so the tool should return:
|
|
21
|
+
|
|
22
|
+
- recommendedStatus: public_faq_candidate
|
|
23
|
+
- faqOutline: a question pattern and answer-scope hint
|
|
24
|
+
- reviewSignals: frequency, response cost, and risk level
|
|
25
|
+
|
|
26
|
+
## Safe Use
|
|
27
|
+
|
|
28
|
+
Use synthetic examples only. Do not paste private customer records, contracts,
|
|
29
|
+
payment details, internal policy text, or support inbox exports into public
|
|
30
|
+
issues, examples, or screenshots.
|
|
31
|
+
|
|
32
|
+
This is an operations review helper. It does not publish FAQ pages or send
|
|
33
|
+
customer replies.
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
import { spawn } from 'node:child_process';
|
|
2
|
+
import fs from 'node:fs';
|
|
3
|
+
|
|
4
|
+
const child = spawn(process.execPath, ['mcp/free-ai-ops-server.mjs'], {
|
|
5
|
+
stdio: ['pipe', 'pipe', 'inherit']
|
|
6
|
+
});
|
|
7
|
+
|
|
8
|
+
const request = fs.readFileSync('examples/faq-candidate-review/sample-request.jsonl', 'utf8');
|
|
9
|
+
let stdout = '';
|
|
10
|
+
|
|
11
|
+
child.stdout.on('data', (chunk) => {
|
|
12
|
+
stdout += chunk;
|
|
13
|
+
});
|
|
14
|
+
|
|
15
|
+
child.stdin.write(request.trim() + '\n');
|
|
16
|
+
child.stdin.end();
|
|
17
|
+
|
|
18
|
+
await new Promise((resolve, reject) => {
|
|
19
|
+
child.on('error', reject);
|
|
20
|
+
child.on('close', (code) => {
|
|
21
|
+
if (code !== 0) reject(new Error('server exited with ' + code));
|
|
22
|
+
else resolve();
|
|
23
|
+
});
|
|
24
|
+
});
|
|
25
|
+
|
|
26
|
+
const response = JSON.parse(stdout.trim());
|
|
27
|
+
const payload = JSON.parse(response.result.content[0].text);
|
|
28
|
+
console.log(JSON.stringify(payload, null, 2));
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"faq_candidate_review","arguments":{"inquiryPattern":"customers ask which pricing plan includes setup support","frequency":"high","responseCost":"medium","riskLevel":"low","currentAnswer":"Setup support is included in the team plan. Solo plans use the public setup checklist."}}}
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# MCP JSON-RPC Session Example
|
|
2
|
+
|
|
3
|
+
This example gives developers a copy-ready MCP session for the public
|
|
4
|
+
@miraigent/free-ai-ops-mcp package.
|
|
5
|
+
|
|
6
|
+
Use it before wiring the package into Claude Desktop, Cursor, or a custom MCP
|
|
7
|
+
client. It verifies that the server responds to:
|
|
8
|
+
|
|
9
|
+
- initialize
|
|
10
|
+
- tools/list
|
|
11
|
+
- tools/call for human_review_gate
|
|
12
|
+
|
|
13
|
+
## Run
|
|
14
|
+
|
|
15
|
+
From the repository root:
|
|
16
|
+
|
|
17
|
+
npm run mcp < examples/mcp-json-rpc-session/sample-session.jsonl
|
|
18
|
+
|
|
19
|
+
You should receive three JSON-RPC response lines. The final response should
|
|
20
|
+
include a human_review_gate result with:
|
|
21
|
+
|
|
22
|
+
- gateStatus: stop
|
|
23
|
+
- reviewOwner: support lead
|
|
24
|
+
- boundary: this tool is a review helper and does not send messages
|
|
25
|
+
|
|
26
|
+
## Public-Safe Feedback
|
|
27
|
+
|
|
28
|
+
If the output is unclear, open a Tried It feedback issue and include only:
|
|
29
|
+
|
|
30
|
+
- which command you ran
|
|
31
|
+
- the public-safe input shape
|
|
32
|
+
- the returned status or field that was unclear
|
|
33
|
+
|
|
34
|
+
Do not include secrets, credentials, private customer records, internal policy
|
|
35
|
+
text, or MIRAI Memory behavior.
|
|
@@ -0,0 +1,3 @@
|
|
|
1
|
+
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}
|
|
2
|
+
{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}
|
|
3
|
+
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"human_review_gate","arguments":{"draftType":"customer support reply","audience":"customer","riskFlags":["refund","complaint","personal data"],"reviewOwner":"support lead","sendMode":"manual"}}}
|
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.11",
|
|
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",
|
|
@@ -25,6 +25,7 @@
|
|
|
25
25
|
"test": "node scripts/smoke-test.mjs",
|
|
26
26
|
"example:human-review-gate": "node examples/human-review-gate/run-example.mjs",
|
|
27
27
|
"example:prompt-risk-review": "node examples/prompt-risk-review/run-example.mjs",
|
|
28
|
+
"example:faq-candidate-review": "node examples/faq-candidate-review/run-example.mjs",
|
|
28
29
|
"mcp": "node mcp/free-ai-ops-server.mjs"
|
|
29
30
|
},
|
|
30
31
|
"keywords": [
|