@miraigent/free-ai-ops-mcp 0.1.7 → 0.1.10
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 +26 -0
- package/README.md +67 -0
- package/examples/mcp-json-rpc-session/README.md +35 -0
- package/examples/mcp-json-rpc-session/sample-session.jsonl +3 -0
- package/examples/prompt-risk-review/README.md +33 -0
- package/examples/prompt-risk-review/run-example.mjs +28 -0
- package/examples/prompt-risk-review/sample-request.jsonl +1 -0
- package/mcp/free-ai-ops-server.mjs +1 -1
- package/package.json +2 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,31 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.1.10] - 2026-06-14
|
|
4
|
+
|
|
5
|
+
### Changed
|
|
6
|
+
|
|
7
|
+
- Added a README tool picker so npm/GitHub visitors can choose the first MCP
|
|
8
|
+
tool by workflow risk before opening issues or integrating the package.
|
|
9
|
+
|
|
10
|
+
## [0.1.9] - 2026-06-13
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
|
|
14
|
+
- Added a copy-ready JSON-RPC MCP session example so developers can verify
|
|
15
|
+
initialize, tools/list, and a human_review_gate call before integrating with a
|
|
16
|
+
desktop MCP client.
|
|
17
|
+
- Added README guidance for using the session example as a public-safe smoke
|
|
18
|
+
test when opening GitHub issues.
|
|
19
|
+
|
|
20
|
+
## [0.1.8] - 2026-06-12
|
|
21
|
+
|
|
22
|
+
### Added
|
|
23
|
+
|
|
24
|
+
- Added a copy-ready prompt_risk_review example for developers checking
|
|
25
|
+
customer-facing prompts before AI use.
|
|
26
|
+
- Added README input/output for the prompt risk workflow and a matching npm
|
|
27
|
+
example script.
|
|
28
|
+
|
|
3
29
|
## [0.1.7] - 2026-06-10
|
|
4
30
|
|
|
5
31
|
### Added
|
package/README.md
CHANGED
|
@@ -16,6 +16,9 @@ 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
|
+
For a complete public-safe MCP session that covers initialize, tools/list, and
|
|
20
|
+
one tool call, see examples/mcp-json-rpc-session/.
|
|
21
|
+
|
|
19
22
|
If you are not a developer and only want the spreadsheet/checklist version
|
|
20
23
|
first, download the free review kit:
|
|
21
24
|
|
|
@@ -51,6 +54,20 @@ Claude Desktop config location:
|
|
|
51
54
|
- Teams prototyping human-in-the-loop AI workflows before integrating real data.
|
|
52
55
|
- Operators who can run npm/npx and want a small public MCP example.
|
|
53
56
|
|
|
57
|
+
## Pick Your First Tool
|
|
58
|
+
|
|
59
|
+
Start with the tool that matches the first unsafe handoff in your workflow:
|
|
60
|
+
|
|
61
|
+
- AI draft may reach a customer: use `human_review_gate`.
|
|
62
|
+
- Repeated support questions should become a public FAQ: use
|
|
63
|
+
`faq_candidate_review`.
|
|
64
|
+
- CRM notes mix facts, AI suggestions, and human decisions: use
|
|
65
|
+
`ai_safe_crm_note`.
|
|
66
|
+
- A prompt may touch customer data or public output: use `prompt_risk_review`.
|
|
67
|
+
|
|
68
|
+
All examples use synthetic data. Keep private customer records, secrets,
|
|
69
|
+
internal policy text, and paid product files out of public issues and screenshots.
|
|
70
|
+
|
|
54
71
|
## What To Do Next
|
|
55
72
|
|
|
56
73
|
- Try one tool with synthetic data.
|
|
@@ -114,6 +131,52 @@ Use this as a small public proof before building a larger AI support workflow.
|
|
|
114
131
|
See examples/human-review-gate/ for copy-ready JSON-RPC examples and a sample
|
|
115
132
|
decision log that match the free Gumroad kit.
|
|
116
133
|
|
|
134
|
+
## Copy-Ready MCP Session
|
|
135
|
+
|
|
136
|
+
Use this when you want to confirm the package responds like an MCP server before
|
|
137
|
+
connecting it to Claude Desktop, Cursor, or your own MCP client:
|
|
138
|
+
|
|
139
|
+
npm run mcp < examples/mcp-json-rpc-session/sample-session.jsonl
|
|
140
|
+
|
|
141
|
+
The session sends three JSON-RPC messages:
|
|
142
|
+
|
|
143
|
+
- initialize: confirms protocolVersion, capabilities, and serverInfo.
|
|
144
|
+
- tools/list: confirms the four public alpha tools are visible.
|
|
145
|
+
- tools/call: runs human_review_gate with synthetic support-reply data.
|
|
146
|
+
|
|
147
|
+
If you open a GitHub issue, copy only synthetic input shapes and returned status
|
|
148
|
+
fields. Do not paste private customer records, secrets, tokens, internal policy
|
|
149
|
+
text, or MIRAI Memory behavior.
|
|
150
|
+
|
|
151
|
+
## Check A Prompt Before AI Use
|
|
152
|
+
|
|
153
|
+
Use prompt_risk_review before a support, CRM, FAQ, or workflow prompt is sent to
|
|
154
|
+
AI. It helps developers decide whether a prompt can proceed with a checklist,
|
|
155
|
+
needs human review, or should stop before use because it touches sensitive data
|
|
156
|
+
or customer-facing output.
|
|
157
|
+
|
|
158
|
+
Example input:
|
|
159
|
+
|
|
160
|
+
{
|
|
161
|
+
"operation": "support automation",
|
|
162
|
+
"promptSummary": "Draft a customer reply from inquiry details and suggest the next support step.",
|
|
163
|
+
"dataTypes": ["customer email", "inquiry body", "plan name"],
|
|
164
|
+
"customerFacing": true,
|
|
165
|
+
"riskLevel": "medium"
|
|
166
|
+
}
|
|
167
|
+
|
|
168
|
+
Expected result:
|
|
169
|
+
|
|
170
|
+
{
|
|
171
|
+
"recommendation": "human_review_required",
|
|
172
|
+
"riskFlags": ["customer_facing", "sensitive_data_possible"],
|
|
173
|
+
"boundary": "This tool is a prompt risk helper. It is not legal advice and does not call an AI API."
|
|
174
|
+
}
|
|
175
|
+
|
|
176
|
+
Run the copy-ready example:
|
|
177
|
+
|
|
178
|
+
npm run example:prompt-risk-review
|
|
179
|
+
|
|
117
180
|
## Launch Flow
|
|
118
181
|
|
|
119
182
|
See LAUNCH_FLOW.md for the first public posting plan, issue collection flow, and
|
|
@@ -140,6 +203,10 @@ Run the public FREE-004 example:
|
|
|
140
203
|
|
|
141
204
|
npm run example:human-review-gate
|
|
142
205
|
|
|
206
|
+
Run the prompt risk review example:
|
|
207
|
+
|
|
208
|
+
npm run example:prompt-risk-review
|
|
209
|
+
|
|
143
210
|
## npm Package
|
|
144
211
|
|
|
145
212
|
Package name: @miraigent/free-ai-ops-mcp
|
|
@@ -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"}}}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# Prompt Risk Review Example
|
|
2
|
+
|
|
3
|
+
This example shows how to call the public prompt_risk_review MCP tool before an
|
|
4
|
+
operational prompt is sent to AI.
|
|
5
|
+
|
|
6
|
+
Use it when a support, CRM, FAQ, or workflow automation prompt might include
|
|
7
|
+
customer-facing output or sensitive data.
|
|
8
|
+
|
|
9
|
+
## Run
|
|
10
|
+
|
|
11
|
+
From the repository root:
|
|
12
|
+
|
|
13
|
+
npm run example:prompt-risk-review
|
|
14
|
+
|
|
15
|
+
The example sends sample-request.jsonl to the MCP server and prints the
|
|
16
|
+
prompt_risk_review result.
|
|
17
|
+
|
|
18
|
+
## What To Look For
|
|
19
|
+
|
|
20
|
+
The sample includes a customer-facing support operation and customer email data,
|
|
21
|
+
so the tool should return:
|
|
22
|
+
|
|
23
|
+
- recommendation: human_review_required or stop_before_ai_use
|
|
24
|
+
- riskFlags: customer_facing and sensitive_data_possible
|
|
25
|
+
- saferNextStep: a human-reviewed data-handling step before real use
|
|
26
|
+
|
|
27
|
+
## Safe Use
|
|
28
|
+
|
|
29
|
+
Use synthetic examples only. Do not paste private customer records, secrets,
|
|
30
|
+
contracts, payment details, or internal policy text into public issues,
|
|
31
|
+
examples, or screenshots.
|
|
32
|
+
|
|
33
|
+
This is an operations review helper, not legal or compliance advice.
|
|
@@ -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/prompt-risk-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":"prompt_risk_review","arguments":{"operation":"support automation","promptSummary":"Draft a customer reply from inquiry details and suggest the next support step.","dataTypes":["customer email","inquiry body","plan name"],"customerFacing":true,"riskLevel":"medium"}}}
|
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.10",
|
|
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",
|
|
@@ -24,6 +24,7 @@
|
|
|
24
24
|
"check": "node --check mcp/free-ai-ops-server.mjs && node --check scripts/smoke-test.mjs && node --check scripts/secret-scan.mjs && node scripts/secret-scan.mjs",
|
|
25
25
|
"test": "node scripts/smoke-test.mjs",
|
|
26
26
|
"example:human-review-gate": "node examples/human-review-gate/run-example.mjs",
|
|
27
|
+
"example:prompt-risk-review": "node examples/prompt-risk-review/run-example.mjs",
|
|
27
28
|
"mcp": "node mcp/free-ai-ops-server.mjs"
|
|
28
29
|
},
|
|
29
30
|
"keywords": [
|