Guides · Checked November 8, 2026
Getting into GitHub Copilot, Gemini, Microsoft Copilot, Muse and Grok
Beyond ChatGPT, Claude, Cursor and Perplexity, most AI apps with an MCP directory pick their listings by hand. Some take forms, some take pull requests, and a few have no way in at all. Almost all of them let users add your server by URL anyway.
GitHub Copilot and VS Code
GitHub's registry at github.com/mcp feeds the MCP gallery in VS Code and GitHub Copilot. Getting in takes two steps:
- Publish to the official MCP Registry. Install
mcp-publisher, runmcp-publisher initto create aserver.json, prove you own the package (anmcpNameinpackage.jsonfor npm, or aremotesentry for a hosted server), sign in with GitHub or your own domain, and runmcp-publisher publish. There's no review. - Ask GitHub to add you, in this discussion or at [email protected]. Include your registry name and version, the package or remote endpoint and how it signs in, the repository, the license, a one- or two-line description, and proof it's in the official registry, like the output of
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=your-server".
Publishing to the official registry doesn't add you to GitHub's on its own. GitHub confirmed in May 2026 that new servers are still picked by hand, and once you're in, new versions sync automatically (GitHub). The discussion has more than 500 requests, some unanswered after 39 days, and in May 2026 the gallery still showed only about 100 servers. To check whether you're in: https://api.mcp.github.com/v0.1/servers?search=your-server.
Google Gemini
Google has two separate places.
Connected Apps, for the Gemini app and Search. Google announced it on October 28, 2026, and is letting developers in "in phases": apply for access at developers.google.com/connected-apps (Google). What you need (Google):
- A public Streamable HTTP server, at one worldwide address (not one per region)
- A token at
/.well-known/google-connected-appsto prove you own the domain - A description under 30 words, a 512 by 512 icon, at least 3 capabilities, and at least 3 example prompts: two starting with
@YourAppand one that mentions it naturally - Terms of service and a privacy policy
- A test account with data and two-factor sign-in turned off, or Google may reject you
- A category, which you can't change later
You build and test it in Connected Console with Gmail testers and Gemini's developer mode, then send it for review. Google rejects apps that ask for more location or context than they need, or that it can't fully test (Google). Approval doesn't publish it: you do that yourself.
Gemini CLI extensions. No form at all. Add a gemini-extension.json to the root of a public GitHub repository and give the repo the gemini-cli-extension topic. A crawler checks tagged repositories daily, and extensions that pass its checks appear at geminicli.com/extensions (Google). People report it takes a few days to a week. Remove the topic and you disappear.
Microsoft 365 Copilot
Microsoft certifies MCP servers for Copilot Studio, Azure Foundry and Copilot chat (Microsoft):
- Who can apply: a Partner Center account with a verified business, enrolled in the Microsoft 365 and Copilot program, that owns the service behind the server. Independent developers wrapping someone else's API can't.
- What you send: a manifest, a
mcptools.json, anintro.md, icons, and your OAuth client details stored in Azure Key Vault, with read access for Microsoft's service account. Dynamic client registration and PKCE aren't supported. - How it goes: submit the intake form, Microsoft emails you instructions, then automated checks and a review of sign-in, security, compliance and responsible AI. Sending your own evaluation results speeds it up.
- Capacity: "due to high submission volume during preview, only a limited number of submissions can be processed", and Microsoft contacts you if yours is picked up. The previous certification process stays open until November 18, 2026.
Any Copilot Studio user can still add your server by URL, as long as it uses Streamable HTTP.
Meta Muse
Meta opened its Muse Connector Platform on September 18, 2026, and received more than 1,500 applications in less than a week (Technspire). You apply at platform.muse.ai with a work email, then complete a business check, a data-processing questionnaire, tool documentation and a test account (Manufact).
Meta's guidelines are strict about usefulness:
- The connector has to finish the task. Sending users to your site to check out doesn't count.
- It has to do more than Muse's browser can. A wrapper around public web pages doesn't qualify.
- Mark each tool as Read, Write or Sensitive write, and keep instructions to the model out of descriptions.
- No new tools that move money or trade.
- Tell Meta about security incidents within 48 hours.
Review has three stages: a risk assessment, a review of each tool (unapproved tools are left out), and testing from start to finish. Status shows only in the portal, and Meta doesn't answer emails about it. Being featured is a separate editorial decision. Partners like Dropbox launched their connectors for users in the US and Canada.
Grok
xAI's form at x.ai/bot/marketplace/submit-a-plugin lists plugins in Grok Bot and Cursor, with Grok itself "coming soon". It asks for your organization, a square logo, an MCP URL or public GitHub repo, a 600-character description and testing instructions, and submitting accepts Cursor's publisher terms: free plugins, permissive licenses only (MCP Tower). There are no published criteria or timelines. On grok.com, users can add any public server under Connectors (xAI).
The rest
- Slack: Slackbot can use MCP servers from Slack apps. Build a Slack app with the
mcp:connectscope and a server on a domain you own, then go through Slack Marketplace review. Vague or misleading tool names and descriptions get rejected (Slack). - Kiro: submit a "Power" at kiro.dev/powers/submit, as a plugin in a public repo with a README that links your privacy policy and support contact. No beta servers. Kiro gets in touch if it's a fit.
- Zed: extensions are added by pull request to
zed-industries/extensions, but Zed is moving its MCP servers to the official registry (Zed). Publish there instead. - Raycast: open a pull request adding your server to its MCP Registry extension (Raycast).
- Devin Desktop (formerly Windsurf): plugins come from the
CognitionAI/devin-marketplacerepo. Companies can ask to be listed through devin.ai/partners. - AWS Marketplace: list your server as a SaaS product of type MCP Server, with an AWS seller account (AWS).
- No way in: Mistral's Le Chat and Notion have short lists of built-in connectors and no public process for joining them, and JetBrains has no MCP directory at all. Users of all three can still add a server themselves.
Checkers to run before you submit, and companies that will submit for you, are in the overview.