App identity & plugin metadata
What clients discover automatically and what their publisher listing controls.
On this page
MCP server identity
Weeveo initialization advertises its title, description, website https://weeveo.com and brand icon. The description identifies Sayan. Clients that consume those standard metadata fields can display them automatically.
Publisher identity is host-managed
MCP and OAuth do not define a standard developer-name field that controls every host's listing. A custom ChatGPT connection can show a generic developer label even when the server metadata is correct. Deploying metadata cannot guarantee replacing that host-managed label or an already cached connection description.
Packaged integration
The source includes integrations/chatgpt/plugin.json and mcp.json with Sayan, website, descriptions, icon and OAuth dynamic-registration configuration. The portable package provides supported listing fields to hosts when uploaded; it is not automatically fetched from a bare MCP URL during consent.
Published listings
For an OpenAI plugin listing, use the host's packaging and submission flow. The displayed developer name uses the selected verified developer identity. Server tool updates and listing updates are separate. See the official plugin packaging and submission guidance.
Consent page
The consent page focuses on the requested agent, approved sites and permissions. Publisher metadata belongs to the integration listing, not an extra developer footer on the authorization form.
Still looking for an answer? Try troubleshooting or get in touch.