Skip to content

v0.2.2 - Local MCP server and client registration

Latest
Latest

Choose a tag to compare

View all tags
@pioneerjeff pioneerjeff released this 03 Jul 15:00
v0.2.2
c6e23bb

Patch release focused on exposing Emotion Engine through a local stdio MCP server and making client registration harder to misconfigure.

Highlights

  • Added a zero-dependency local stdio MCP server for Emotion Engine runtime/protocol tools, including status, compact summaries, record policy, advisory appraisal, session lifecycle, turn recording, trust settlement, and recent log inspection.
  • Bundled the MCP server into the Codex skill package while keeping Agent Harness responsibilities out of the MCP boundary: install refresh, doctor, repair, manifest checks, and sidecar drift remain Agent Harness work.
  • Added MCP client registration examples for Codex CLI, Claude Code, Claude Desktop, and project-level .mcp.json.
  • Added scripts/register_mcp_client.py so users can register the local stdio server without hand-writing MCP config.
  • Clarified state path rules: generic projects use .emotion-engine/emotion-state.json, while Codex and Agent Harness targets use .emotion-engine/codex-state.json so wrappers and MCP clients do not split state.

Verification

  • PYTHONDONTWRITEBYTECODE=1 python3 tests/test_mcp_registration.py -> 6 tests OK
  • PYTHONDONTWRITEBYTECODE=1 python3 tests/test_mcp_server.py -> 5 tests OK
  • PYTHONDONTWRITEBYTECODE=1 python3 tests/test_demo_static.py -> 6 tests OK
  • python3 -m py_compile scripts/emotion_engine_mcp.py scripts/register_mcp_client.py tests/test_mcp_server.py tests/test_mcp_registration.py -> OK
  • PYTHONDONTWRITEBYTECODE=1 python3 tests/test_codex_integration.py -> 7 tests OK
  • PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tests -> 82 tests OK
  • git diff --check -> OK
Assets 2
Loading