The part nobody writes down
Building the MCP server is the well-documented half. Getting it listed — into the Claude connector directory, the ChatGPT apps directory, and the Microsoft Copilot catalog — is where Node8 found the real friction when we ran this for a leading investment research firm (context: engagement overview). Three ecosystems, three different submission processes, three different prerequisite account types, and in one case documentation thin enough that the working plan was “submit and see what comes back.”
This is the playbook we wish we’d had.
Before you touch any submission form
All three directories review a running production server, not an application on paper. From the architecture work, you need in place:
- Your production domain, live under HTTPS. Not a dev URL on a partner’s cloud account — reviewers and OAuth registrations bind to the domain.
- OAuth 2.1 working end to end, including dynamic client registration, since each directory’s assistant registers as its own client.
- A published privacy policy on your domain. Provider app registration (Google, Microsoft) and directory review both check for it.
- Proof of domain ownership completed with the identity providers you use for login.
- Tool descriptions a stranger can evaluate. Reviewers will invoke your tools cold; ambiguous descriptions produce ambiguous rejections.
We also learned to sequence deliberately: we launched the Claude and Microsoft submissions in parallel, with OpenAI following as soon as account access was untangled. The reviews run on independent clocks; serializing them just adds weeks.
Anthropic Claude: the account type is the gotcha
The submission itself is straightforward — the prerequisite isn’t obvious. Anthropic’s directory submission runs through a Claude for Teams account. Not a personal Pro account, even one the company pays for. In our case, the firm had employees using Claude individually, and it took an IT-side inventory to confirm none of it qualified; a new Teams account had to be opened specifically for the submission.
Practical notes:
- Teams has a five-seat minimum. You don’t need the seats for the submission itself — you need the account class. Budget the five seats and hand the spares to the people testing the connector.
- Make the submission owner deliberate. Whoever owns the account will be the point of contact through review. We put the account under the client’s IT lead and added the engineering owner as a user, so the party doing the submission had standing access.
- You can ship value before listing. Claude supports adding custom connectors directly in a workspace, which is how the firm’s own team used the server throughout review.
OpenAI ChatGPT: it’s about platform permissions, not the form
OpenAI’s submission routes through the OpenAI platform dashboard — the same console developers use for API keys — not through ChatGPT itself. Which surfaces the real enterprise gotcha: who owns your OpenAI account?
In most companies, the OpenAI account was created ad hoc by whoever needed API access first. Ours was no different: a corporate account existed, developers were using it, but nobody in the room had owner or admin rights, and elevating permissions meant tracking down the original creator. That chase — not anything technical — was the OpenAI critical path.
Practical notes:
- Confirm early whether your corporate OpenAI account exists, what tier it is, and who holds the owner role. A standard business/team tier was sufficient for us; enterprise wasn’t required.
- OpenAI’s platform roles are granular; the person submitting needs sufficient entitlements in the org, so grant them deliberately rather than sharing credentials.
- Expect review to exercise your server’s compliance details (tool annotations, auth behavior). Treat a rejection as a punch list, not a verdict — resubmission is normal.
Microsoft Copilot: form-based, lightly documented, just submit
Microsoft’s process for getting an MCP connector into the Copilot ecosystem was, at the time we ran it, the least documented of the three. What we established, partly by asking Microsoft contacts directly:
- Submission is form-based. You provide connector details, endpoints, and organizational information through a submission form — there was no requirement to publish through a developer-portal packaging flow first for this path.
- Microsoft Partner verification is not required to submit. This one caused real confusion internally, because partner verification does gate cosmetic things — notably getting your logo onto the Microsoft sign-in screen. Functionality first, logo later; don’t let the partner process block the submission.
- The target model is a federated connector — your MCP server registered so Copilot tenants can discover and enable it. Some configuration accompanies this beyond “here’s the MCP URL,” and documentation of the end-to-end process is sparse; the advice we got from Microsoft, which proved right, was to submit and iterate on whatever came back.
- A corporate Microsoft 365 tenant is assumed. All the review and testing flows through it.
The compensating advantage of the Microsoft ecosystem: you don’t have to wait for the marketplace at all to start piloting — the Microsoft 365 admin center can connect a tenant directly to an MCP server, which is exactly how the firm ran its internal pilot while the submission processed. The admin-portal mechanics get their own page: Enterprise Copilot Agents and Connectors.
Run it like a project
The submissions took about as much coordination as a small engineering sprint, mostly across IT, security, and account owners rather than engineers. What worked:
- One tracked task per directory, each with an owner for account access, an owner for the submission, and the prerequisite list above.
- Parallel submissions, with a weekly checkpoint until every directory reached “submitted, awaiting review.”
- A pilot channel per ecosystem (Claude custom connector, Copilot direct MCP connection) so user feedback flowed in while reviews ran.
- OAuth logs open during review windows — a reviewer’s failed auth attempt looks like a bug report you never received.
Work with Node8
Node8 has run this exact gauntlet — one production MCP server, three directory submissions, and the enterprise rollout behind them — for a leading investment research firm. If you want your data listed inside Claude, ChatGPT, and Copilot without discovering each ecosystem’s gotchas the slow way, talk to us.