Fill in the form on Connectors — your server URL, the copy people will read in the directory, and a version number. We scan the URL to check it speaks MCP and to see how it authenticates. Then submit it for review.
Review is a real step, not a formality. A published connector's tool descriptions become instructions inside other people's model context, and whatever it returns comes back as text their assistant acts on, so we read what a server actually does before listing it. Expect us to look at the description you wrote, since that is what someone reads when deciding whether to hand you access to their account.
Each submission is a version, numbered like 1.0.0. The version is what gets reviewed — not the connector — so your live release stays exactly as it is while the next one is read. When we approve a version, its copy becomes what the directory shows and what users connect to.
A new version has to be numbered higher than the one that is published, and carries release notes describing what changed. Submit a new version whenever your tools change behaviour; that is one of the things you affirm when you submit.
| State | What it means |
|---|---|
| draft | Yours to edit. Not visible to anyone else. |
| in review | In the queue. Frozen while we read it — withdraw to make changes. |
| live | Approved and in the catalog. Anyone can find and connect it. |
| superseded | Approved, but a later version replaced it. |
| changes needed | Not listed, with a note saying why. Fix it and submit again. |