ReMe/integrations
jinliyl 3d2ecc60d2
feat(service): expose MCP through HTTP backend (#498)
* feat(service): expose MCP through HTTP backend

Serve JSON/SSE job endpoints and streamable HTTP MCP from one FastAPI application, sharing the same jobs and application lifecycle. Preserve the standalone MCP backend, add configurable MCP HTTP settings, update startup metadata and integration docs, and cover routing, lifecycle, configuration, and compatibility behavior with unit tests.

* fix(service): preserve MCP request protections

Route the exact MCP path through the complete FastMCP ASGI application so its middleware and state remain active. Reject non-literal MCP paths and validate reserved Job conflicts before tolerant service registration. Add regression coverage for middleware preservation, route syntax, and startup failure.

* fix(service): reject encoded MCP paths

Reject percent signs in mcp_path so ASGI path decoding cannot turn an accepted configuration into an unreachable route. Cover encoded slash, space, and double-encoded slash inputs.
2026-08-27 17:23:11 +08:00
..
claude_code feat(service): expose MCP through HTTP backend (#498) 2026-08-27 17:23:11 +08:00
hermes_agent feat: add DSH memory integration and organize extensions (#461) 2026-08-20 15:31:51 +08:00
README.md refactor(packaging): reorganize published packages (#495) 2026-08-27 14:02:09 +08:00

Agent Integrations

This directory contains host-specific adapters that connect external agents to ReMe. An integration may use the host's plugin API, hooks, MCP configuration, or client interface, but it does not extend ReMe's runtime through the reme.plugins entry-point group.

The shared TypeScript client and the DeepSeek Harness and OpenClaw adapters live in ../typescript.

Installable extensions of ReMe itself include Auto Fin and Daily Paper.