ChatGPT app submission: how to get your SaaS into ChatGPT's Plugins Directory
How to submit a SaaS app to ChatGPT's Plugins Directory: who can submit, each step in OpenAI's portal, what reviewers check, and a checklist to run first.
- ChatGPT
How to submit a SaaS app to ChatGPT's Plugins Directory: who can submit, each step in OpenAI's portal, what reviewers check, and a checklist to run first.
How to test an MCP server before you submit it: the MCP Inspector, raw curl requests, the error cases to check, and a CI gate, with outputs from a live server.
MCP server best practices for SaaS teams: job-shaped tools, plain names, honest descriptions, explicit hints, small results and errors an agent can act on.
What the Model Context Protocol is, how hosts, clients and servers fit together, what a server exposes, and what MCP means for a SaaS product, from the spec.
Where to launch an MCP connector first, by where your users work and what each directory asks for: Claude, ChatGPT, Cursor, and the MCP Registry alongside them.
How to choose between building an MCP connector in-house, using a hosted MCP platform or generator, and hiring a studio, by what each leaves your team to own.
How a SaaS MCP server and its authorization server meet the MCP spec: protected resource metadata, Client ID Metadata Documents, a DCR fallback and API keys.
The attacks a SaaS company's MCP server is exposed to, from prompt injection to tool poisoning and SSRF, and the defenses the MCP spec and OWASP set out.
What an MCP server adds on top of your API: runtime tool discovery, descriptions the model reads, per-user OAuth, and tools designed around jobs, not endpoints.
The rules each directory's reviewers check for MCP connectors and plugins on Claude, ChatGPT and Cursor, from the platforms' docs, and how to check them first.