Retiring the ChatGPT Connector
We have retired meo-gpt-connector, the bridge that let a Custom GPT use Meo
Mai Moi through ChatGPT Actions.
The experiment gave us one unusually clear number: the GPT marketplace brought Meo Mai Moi zero organic registrations. The connector worked, but running a separate service, OAuth flow, test environment, and deployment pipeline for it was no longer justified.
The useful work was not lost. Building the connector taught us how to turn pet care tasks into semantic tools, keep Meo Mai Moi as the authority, and put permission checks around assistant access. Those lessons went into meo-mcp.
One entry point for agents
MCP is now the common entry point for agents that work with Meo Mai Moi. It is not tied to one marketplace or one chat product. Any compatible OAuth-capable client can connect to:
https://mcp.meo-mai-moi.com/mcpThe gateway exposes the user-facing Meo Mai Moi tools through narrow scopes and an explicit consent flow. Meo Mai Moi still owns the data, permissions, and product rules.
The old connector repository remains available as a historical reference, but its containers, public endpoints, and deployment pipeline are gone. The OAuth bridge and consent page came out of the app itself in v1.19.0.
Nothing else changed for anyone integrating with Meo Mai Moi. The REST API and personal API tokens are still there, still documented, and still the right tool for a script. What went away is one bridge to one chat product that nobody walked across.
This is a small correction, and an honest one. Six months in a marketplace brought this project zero people. Meanwhile the maintenance cost was real every week: a separate service to patch, an OAuth flow to keep working, a test environment, a pipeline.
I would rather spend those evenings on a protocol that lets many kinds of agents connect than on a storefront that nobody browsed.