feat(mcp): expose streamable http tools#71
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OpenCortex can now be used by MCP clients over the current Streamable HTTP transport. The new
/mcpendpoint exposes the cleaned write and recall chain as JSON-RPC tools without reintroducing the legacy HTTP+SSE transport.The endpoint supports
initialize,ping,tools/list, andtools/call. Tool calls are backed by the existing memory/resource/session/forget/search flows, so MCP requests share the same runtime dependencies, identity context, worker side effects, and retrieval behavior as the REST API.Details
POST /mcpreturns JSON-RPC JSON responses, whileGET /mcpreturns405because SSE sessions are not implemented.Content-Type: application/jsonandAccept: application/json, text/event-stream.opencortex.search,opencortex.store_memory,opencortex.store_resource,opencortex.forget,opencortex.session_message, andopencortex.session_endwith Pydantic-derived input schemas.src/opencortex/mcp/so the REST routes stay focused on HTTP API concerns.Validation
uv run --group dev ruff format --check src/opencortex tests/opencortexuv run --group dev ruff check src/opencortex tests/opencortexuv run --group dev pytest -q