moneiai/mcp repository overview

⁠Monei MCP service image

The separate Bun service packages the public Streamable HTTP MCP endpoint, OAuth protected-resource metadata, generated tool metadata and a health check. The authenticated internal Agent endpoint must not be published through a public reverse proxy. MCP passes the caller's bearer token to Supabase; never provide a database-owner or service-role credential as the user's identity.

The canonical product, configuration, security, handoff and deployment contract is the MCP guide⁠. The current environment-variable names and local placeholders are in .env.example⁠; the authoritative runtime parser is src/config.ts⁠. Configure the exact MCP_APP_ORIGIN in the service environment for Open Finance handoff and use a server-only shared signing secret for the internal Agent endpoint; the guide describes validation and failure behavior. Use public HTTPS origins outside loopback development.

⁠Package commands

Install the root workspaces from the repository root with bun install. From the root, bun run dev:mcp starts only MCP and needs a complete standalone configuration; bun run dev launches MCP alongside Vite with derived local settings. bun run --cwd mcp build checks TypeScript and bun run --cwd mcp test runs MCP's Bun unit suite. The disposable HTTP/GoTrue integration suite is bun run e2e:mcp and needs the documented local stack; it is not a substitute for checking a public deployment. See the testing guide⁠ for CI and coverage ownership.

The supported self-hosted service definition and image configuration live in docker/compose.yaml⁠, with installation and update commands in docker/README.md⁠. Hosted routing and secret delivery are owned by IaC⁠, not by this README.