1. Sign in
Glama signs you in with a one-time code sent to your email, so there's no password to manage. Use an address on your product's domain so ownership is clear.
2. Submit each server
Add each remote server separately with its exact name, endpoint and docs link. One listing per server gives each its own page, which can rank on its own.
Open-source servers are listed from their GitHub repository; remote servers appear under connectors with their endpoint.
3. Pass the health check
After approval Glama tests your endpoint and shows the result on the listing. A public server just needs to answer the MCP handshake.
If your server requires OAuth, Glama can't test it until it has a profile to sign in with. Authorize Glama's test profile from your listing's admin area; otherwise the listing can show as unhealthy even when the server works.
- Check your endpoint first with the free MCP server checker.
- Keep a test account with read-only access for directory health checks.
- Watch for unhealthy notices by email and fix them quickly; they're shown publicly.
4. Get into the awesome lists
Some GitHub lists, such as awesome-remote-mcp-servers, expect a Glama connector listing and a working handshake before they accept your pull request, so Glama is worth doing early.
Keep going
Listed is step one. Found is what brings installs.
Get your MCP server's pages indexed by Google and Bing for free, then get backlinks on autopilot from real sites in your niche.
Create a free account