la-caja-mcp

MCP system for accessing and debating La Caja (contextual memory). Repo B: consumer of La Caja (repo A). This repo does not touch the memory core; it communicates with it via API and exposes La Caja to agents.

What's Here

• src/la_caja_mcp/protocolo.py — agent-agent-human debate protocol. Claims, interference requests, rounds with deadlines, human adjudication. Deterministic and replayable (event-sourcing, same discipline as La Caja).

• src/la_caja_mcp/mcp_server.py — MCP server: debate tools + memory tools for La Caja (repo A, consumed via API), a single set of tools and two transports (local stdio / remote streamable HTTP).

• tests/ — mini-falsification of the state machine + integration with real MCP client via stdio (debate and memory).

• demo_debate.py — demo of debate that reaches consensus.

• smoke_http.py — smoke test of streamable HTTP transport.

• worker/ — portable ASGI host (uvicorn + Dockerfile) for remote MCP.

Related MCP server: Arena MCP Server

MCP Server

One set of tools, two transports:

# local (stdio): lo lanza el agente como subproceso
la-caja-mcp --transport stdio

# remoto (streamable HTTP): unico standard para MCP sobre red
la-caja-mcp --transport streamable-http --host 127.0.0.1 --port 8000

Debate: crear_sesion, mover (JSON payload), estado, ultimos_eventos, reproducir_sesion. Memory (requires pip install la-caja; repo A): procesar_consulta, declarar_relacion, consultar, contexto_primado, stats.

Memory is persistent with --caja-db <path> (SQLite, event-sourcing from La Caja) or LA_CAJA_DB; without these, purely in memory.

MCP Transports (Architecture Decision)

• Local = stdio (the agent launches the server as a subprocess).

• Remote = streamable HTTP (the only standard for remote MCP, + OAuth).

• worker/ is an example of a deployable host (VPS/Docker); no public hosted MCP.

Test

$env:PYTHONPATH="src"; python -m pytest tests -q