Thin client edges
- @answer-engine/mcp-server
- @answer-engine/cli
- Install command and client wiring
- Public repository split tracked for launch follow-up
Answer Engine is open where developers need inspectable client edges: the MCP server and CLI packages. The hosted engine, indexes, billing, and evaluation systems are managed infrastructure. That split lets teams audit the install surface without pretending the entire memory service is an open-source project.
npx answer-engine-mcp ae sync run @answer-engine/mcp-server @answer-engine/cli The split is explicit because developer trust breaks when the word open-source quietly expands past the code that is actually available to inspect.
Answer Engine does not imply that the hosted engine, index, billing, or eval system is open source. Those are managed surfaces of the service.
Open-source means the MCP server and CLI edge packages are visible. It does not mean the managed memory engine, vector/index layer, credit system, or evaluation infrastructure is published as an open-source service.
These answers are rendered as static HTML for evaluators and answer engines.
No. The MCP server and CLI are the open client edges. The hosted engine, indexes, billing, and evaluation systems remain managed infrastructure.
Developers can inspect the documented install contracts, MCP tools, CLI flow, and managed/open boundary while the public repository split remains a launch follow-up.
The launch split keeps the install surface auditable while keeping the hosted memory service, tenant isolation, billing, and evaluation systems managed.
Start with the MCP server package, then use the product and security pages to evaluate the managed layer behind it.