@thierry-gilgen-ict/engawa-mcp
v0.1.1
Published
MCP server adapter for Engawa agent-native websites
Readme
@thierry-gilgen-ict/engawa-mcp
MCP server adapter for Engawa using @modelcontextprotocol/server v2 (MCP spec baseline 2026-07-28).
Stability: Early v0.x. Public read-only surface only in v0.1.
When you need this package
Expose a public Streamable HTTP MCP endpoint with registered resources and search_site.
When you don't
Agent-only sites that publish markdown + llms.txt without MCP.
Install
npm install @thierry-gilgen-ict/[email protected]Requires Node.js 24+ (with engawa-core 0.1.1+). Depends on @thierry-gilgen-ict/engawa-core.
Minimal example
import { createEngawa, StaticContentAdapter } from "@thierry-gilgen-ict/engawa-core";
import { createEngawaPublicMcpServer } from "@thierry-gilgen-ict/engawa-mcp";
// ... config + adapter
const engawa = createEngawa(config, adapter);
const server = await createEngawaPublicMcpServer(engawa);
// Wire server to your HTTP frameworkFor fetch-style handlers:
import { createEngawaPublicMcpHandler } from "@thierry-gilgen-ict/engawa-mcp";
const handler = createEngawaPublicMcpHandler(engawa);Public v0.1 API
| Export | Purpose |
| ------------------------------ | ------------------------- |
| createEngawaPublicMcpServer | MCP McpServer instance |
| createEngawaPublicMcpHandler | HTTP handler factory |
| assertPublicAgentInterface | Fail closed if not public |
| EngawaAgentInterfaceError | Config guard error |
Tools: search_site only (read-only). Resources: adapter corpus + _meta JSON.
Requires agentInterface.enabled and agentInterface.public.
Security
- No mutating tools in public handler
- Host/origin validation belongs in your route layer
- Rate limiting belongs in your application or edge
- See security model
Documentation
License
MIT
