Support native Streamable HTTP access to the MCP read tools

Funes currently exposes its read tools through a stdio MCP server launched by each client. I would like to connect Claude Code and Codex to a running Funes server over Streamable HTTP, so they can share one server process without a separate stdio-to-HTTP proxy.

Would native Streamable HTTP be a welcome addition? The proposed interface is `funes mcp --transport streamable-http`, with a localhost default and a configurable listen address. It would expose the existing tools and memory-selection behavior, while keeping stdio as the default. Authentication and deployment would remain external.

Start at the existing stdio MCP server behind `funes mcp` and trace how the read tools and memory-selection behavior are wired. Verify that `--transport streamable-http` supports a localhost default and configurable listen address while stdio remains the default; done means clients can use the existing tools without a stdio-to-HTTP proxy.

Written by the indexing model from the issue text.