Open API MCP

🔍 Problem Statement

As an AI agent or AI-powered application, I cannot consume Pelcro's public Open API as MCP tools, which blocks Pelcro from being used in any AI-native CX, ops, or self-serve experience.

💡 User Story

As a developer, I want a remote MCP server at a public Pelcro URL that exposes every public OPEN API endpoint as an MCP tool, so that I can connect Pelcro to Claude.ai (or any MCP-compatible client) without writing a custom MCP client.

As a subscriber, I want a built-in chat experience in the default Pelcro front-end UI that talks to this MCP server, so that I can do anything I would normally do on the dashboard — manage subscriptions, update addresses etc — by simply asking for it in natural language.

🎯 Definition of Done (DoD)

✔ Open API documentation on README aligns with code as the source of truth, and aligns with Core API documentation.

✔ Open API specs is up-to-date, and aligns with Core API's OpenAPI specs (eg: same thorough example payload, example return responses, same OpenAPI spec version used, etc.)

✔ Every endpoint in Pelcro's public OpenAPI spec (docs.pelcro.com/reference) is exposed as an MCP tool, auto-generated from the spec.

✔ The MCP server is reachable at a public URL (e.g. (new dedicated public hostname, or via https://mcp.pelcro.com/{something}) over HTTP/SSE