feat: implement MCP prompts support

[ezynda3]

Summary

• Adds support for Model Context Protocol (MCP) prompts, which enable servers to define reusable prompt templates and workflows that clients can easily surface to users and LLMs. They provide a powerful way to standardize and share common LLM interactions.
• Implements fetching prompts from MCP servers, registering them as commands, and handling structured responses with resources.

Test plan

• Verify MCP prompts appear in the command list
• Test executing prompts with and without arguments
• Verify structured responses with resources are properly displayed

🤖 Generated with opencode

[thdxr]

closing as we rewrote the codebase - appreciate it though!

[groeimetai]

✅ Fixed in v9.0.166

This issue has been fully resolved. All console.log statements in the servicenow-mcp-unified MCP server have been converted to console.error to comply with the MCP protocol specification.

Changes Made

Core initialization files:

• shared/tool-registry.ts - 6 statistics lines → stderr
• server.ts - 10 statistics lines → stderr
• index.ts - 2 SIGINT/SIGTERM handlers → stderr
• shared/permission-validator.ts - 5 permission logs → stderr

Tool execution files:

• ml_train_incident_classifier.ts - 3 training logs → stderr
• ml_train_anomaly_detector.ts - 1 epoch log → stderr
• ml_train_change_risk.ts - 1 epoch log → stderr
• snow_create_rest_message.ts - 1 fallback log → stderr

Verification

The enterprise-proxy MCP server was already compliant (only using console.error).

After this fix, running:

node dist/mcp/servicenow-mcp-unified/index.js 2>/dev/null

Should produce no output on stdout, ensuring clean JSON-RPC communication with Claude Desktop.

Update

npm install -g snow-flow@latest

Commit:serac-labs/serac@b4715b00
Release:https://github.com/groeimetai/snow-flow/releases/tag/v9.0.166