@miraigent/free-ai-ops-mcp 0.1.20 → 0.1.22

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [0.1.22] - 2026-06-22
+
+### Changed
+
+- Added response-reading guidance to the MCP JSON-RPC session example so npm and
+  GitHub users can tell whether the package is running before debugging desktop
+  MCP client configuration.
+
+## [0.1.21] - 2026-06-21
+
+### Changed
+
+- Added an MCP client troubleshooting checklist to README so Claude Desktop,
+  Cursor, and other MCP users can separate terminal package success from client
+  configuration issues before opening public-safe feedback issues.
+
 ## [0.1.20] - 2026-06-20
 
 ### Added

package/README.md

@@ -80,6 +80,26 @@ Claude Desktop config location:
 - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
 - Windows: `%APPDATA%\Claude\claude_desktop_config.json`
 
+## MCP Client Troubleshooting Checklist
+
+If the package runs from the terminal but does not appear inside Claude Desktop,
+Cursor, or another MCP client, check the connection in this order:
+
+- Run `npx -y free-ai-ops-mcp@npm:@miraigent/free-ai-ops-mcp --help` in the
+  same shell account that launches the MCP client.
+- Confirm the client config uses `command: "npx"` and the exact args shown in
+  this README.
+- Restart the MCP client after saving the config. Most desktop clients read MCP
+  server config only on startup.
+- Run the one-command smoke test with the public JSON-RPC session before
+  changing private workflows.
+- If `tools/list` works in the terminal but not in the client, open a Tried It
+  feedback issue with the client name, operating system, command shape, and the
+  returned public-safe status fields.
+
+Do not paste real customer records, secrets, internal policy text, paid product
+files, or private memory behavior into client logs or GitHub issues.
+
 ## What Success Looks Like
 
 Use this quick check before connecting private systems or opening an issue:

package/examples/mcp-json-rpc-session/README.md

@@ -23,6 +23,23 @@ include a human_review_gate result with:
 - reviewOwner: support lead
 - boundary: this tool is a review helper and does not send messages
 
+## Read The Responses
+
+Use the response shape as a quick acceptance check before changing a desktop MCP
+client config:
+
+- Response 1 should include `serverInfo.name` set to
+  `miraigent-free-ai-ops-mcp`.
+- Response 2 should include four tool names:
+  `human_review_gate`, `faq_candidate_review`, `ai_safe_crm_note`, and
+  `prompt_risk_review`.
+- Response 3 should return a `human_review_gate` content block whose JSON text
+  includes `gateStatus`, `reviewOwner`, `nextAction`, and `boundary`.
+
+If those fields appear in the terminal but not in Claude Desktop, Cursor, or
+another client, the package is likely running and the next thing to check is the
+client config, restart behavior, or command path.
+
 ## Public-Safe Feedback
 
 If the output is unclear, open a Tried It feedback issue and include only:

package/mcp/free-ai-ops-server.mjs

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 
-const serverInfo = { name: 'miraigent-free-ai-ops-mcp', version: '0.1.20' };
+const serverInfo = { name: 'miraigent-free-ai-ops-mcp', version: '0.1.22' };
 
 const tools = [
   {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@miraigent/free-ai-ops-mcp",
-  "version": "0.1.20",
+  "version": "0.1.22",
   "description": "Free MCP server for developers adding human review gates, prompt risk checks, FAQ review, and CRM note safety to AI tools.",
   "homepage": "https://github.com/Miraigent/miraigent-free-ai-ops-mcp",
   "type": "module",