I1: MCP server wrapping repi tools

[VarunGitGood]

Why

Users of Claude Desktop, Cursor, Zed, and other MCP-aware clients already have an AI surface they like. Exposing repi's investigation tools (search_logs, scan_window, get_timeline, get_service_summary) over the Model Context Protocol lets them investigate logs from their existing tool, without a separate UI.

Scope

• Add a repi mcp-serve subcommand that exposes the investigation tools over MCP stdio transport.
• Each MCP tool is a thin wrapper around the existing functions in repi/investigation/tools.py, sharing the same DB pool.
• Provide a sample claude_desktop_config.json snippet in the docs showing how to wire it up.
• Tools should expose resource hints where useful (e.g. known services from get_all_services).

Acceptance

• Claude Desktop (or any MCP client) can be configured to use repi as an MCP server.
• A query like "find errors in api-gateway in the last hour" produces a sensible answer using the repi tools.

[Rupert1987]

To expose the tools, use the official MCP Python SDK to register each function from investigation/tools.py as an MCP tool with stdio transport. Share the DB pool by creating it once in the server entrypoint and injecting it into handlers. Resource hints can be added via get_all_services results on relevant tools. A minimal claude_desktop_config.json entry points the command to your new subcommand.

Full disclosure, I'm working on Alya Hub: https://alya.replit.app/p/Q6SeOQjXg6F4OLB0PxiaWQ

[VarunGitGood]

Hey @Rupert1987 Thanks for commenting i'm still grooming some issues and these aren't finalised yet