doobidoo/mcp-memory-service v8.62.13

v8.62.13 - HTTP-MCP Bridge API Endpoint Fix

on GitHub

HTTP-MCP Bridge API Endpoint Fix - Remote Deployments Restored

Fixed

• HTTP-MCP Bridge API Endpoint Fix (Based on PR #315 by @timkjr)
  • Problem: HTTP-MCP bridge completely broken with 405 Method Not Allowed errors
    • Bridge was using old GET endpoints (/search?q=..., /search/by-tag?tags=...)
    • Current API uses POST endpoints with JSON body payloads
    • Remote deployments using the bridge were unable to search or retrieve memories
  • Root Cause: Bridge code not updated when API migrated from GET to POST endpoints
  • Solution:
    • Updated examples/http-mcp-bridge.js to use POST /search and POST /search/by-tag
    • Changed from query parameters to JSON request bodies
    • Fixed response payload structure to match current API
    • Updated integration tests to verify POST endpoints
  • Impact: HTTP-MCP bridge now works correctly for remote MCP deployments
  • Files Changed:
    • examples/http-mcp-bridge.js (+34/-19 lines)
    • tests/integration/test_bridge_integration.js (+6/-1 lines)
  • Testing: All 9 integration tests passing (test_bridge_integration.js)

Installation

pip install --upgrade mcp-memory-service

What's Changed

• Fix HTTP-MCP bridge to use POST endpoints instead of deprecated GET endpoints
• Update integration tests to verify bridge functionality with current API
• Based on work from PR #315 by @timkjr

Full Changelog: v8.62.12...v8.62.13

Acknowledgments

Thank you to @timkjr for identifying this critical issue and providing the initial fix in PR #315.