The learn/guides/ai/MemoryCoreMcpApi.md guide was outdated, describing the Memory Core server as an Express.js-based REST API. This has been updated to reflect its current implementation as a tool server using the @modelcontextprotocol/sdk.
Key changes include:
- Architecture Update: The guide now correctly describes the server as an MCP SDK application that communicates over stdio, not an HTTP server.
- From Endpoints to Tools: The main body of the document was rewritten to describe the available tools (e.g.,
add_memory, query_summaries) instead of REST endpoints. The old curl-based examples were replaced with conceptual call_tool() examples.
- New Tools Table: A summary table of all available tools, grouped by category, was added for quick reference.
- Updated Error Handling: The section on error handling was updated to describe the
isError: true flag in an MCP tool response, replacing the obsolete information about HTTP status codes.
- Cleanup: The "Migration Path" section was removed as it's complete, and the path to the
openapi.yaml file was corrected. All references to Express, Swagger, and HTTP were removed.
The guide now accurately documents the current state and usage of the Memory Core MCP server.
The
learn/guides/ai/MemoryCoreMcpApi.mdguide was outdated, describing the Memory Core server as an Express.js-based REST API. This has been updated to reflect its current implementation as a tool server using the@modelcontextprotocol/sdk.Key changes include:
add_memory,query_summaries) instead of REST endpoints. The oldcurl-based examples were replaced with conceptualcall_tool()examples.isError: trueflag in an MCP tool response, replacing the obsolete information about HTTP status codes.openapi.yamlfile was corrected. All references to Express, Swagger, and HTTP were removed.The guide now accurately documents the current state and usage of the Memory Core MCP server.