How to submit an MCP server to Glama
By Jonah EasePublished Last checked
Glama is two directories under one roof: one for servers whose code you run yourself, and one for connectors, which are servers somebody else hosts at a URL. Which one you belong in decides the rest of the route[1][2]. Both start with an account, and the awesome-mcp-servers list runs a check for a Glama score badge on every pull request.
Servers or connectors
| List | What it holds | Size on |
|---|---|---|
| Servers | Source code you install and run | 94,520 |
| Connectors | A running endpoint a client connects to, tagged Healthy, Unhealthy or Untested | 25,727 |
Counts shown on each list's page, updated 1 Oct 2026 at 07:00[1][2]. Each page has its own Add Server button.
Glama says its directory comes from community submissions, automated discovery with manual curation, the official MCP Registry and the awesome list[3]. A published registry entry may therefore reach Glama without a submission.
Add Server asks you to sign in first
Signed out, clicking Add Server opens a sign-up dialog instead of a form: Google, GitHub or Discord buttons, or an email address, and an "I'm not a robot" box[1]. You click through that yourself. The form behind the dialog is not on a public page, so this page does not describe its fields.
The Docker check
Glama has to start your server to read its tools. The awesome list's own bot tells authors that the Dockerfile goes directly into Glama, and that the check only needs the server to start and answer introspection requests[6]. A server that cannot start in a container has nothing for the check to read.
Claim the listing with glama.json
A claimed listing lets you edit the name and description, set the Docker image, see usage reports and get review notifications[4]. Put this file in the repository root:
{
"$schema": "https://glama.ai/mcp/schemas/server.json",
"maintainers": ["your-github-username"]
}After you add or change it, run the Claim ownership flow again so Glama re-reads the file. A repository under your personal account can also be claimed by signing in with GitHub, but one under an organisation needs the file[4].
When the claim or the check fails
- You still cannot claim after adding glama.json. Glama's two checks: your GitHub username is in
maintainers, and the JSON has no syntax error[4]. - The listing has no score yet. The awesome list's bot asks authors to wait until Glama has evaluated the server and shows a quality score[6]. Glama's TDQS grades each tool in six areas, from Purpose Clarity to Contextual Completeness[5].
- The awesome list labels your pull request missing-glama. Its entry must carry the score badge, in this form[6]:
[](https://glama.ai/mcp/servers/OWNER/REPO)By hand
Sign in, press Add Server on the right list, and fill in the form that opens. If you list a server you run from source, add the Dockerfile on Glama and the glama.json to the repository. The awesome-mcp-servers list depends on the result, so do this first.
Current status,
Both lists showed an Add Server button on 1 Oct 2026. Neither page states a price or a review time[1][2].
Sources
- Glama: MCP servers directory · checked
- Glama: MCP connectors directory · checked
- Glama: MCP directory API reference (data sources) · checked
- Glama blog: What is glama.json? · checked
- Glama blog: Tool Definition Quality Score (TDQS) · checked
- awesome-mcp-servers: the Glama check workflow · checked
ManyCP is not affiliated with, endorsed by or sponsored by any directory, Docker, OpenAI, Anthropic or GitHub named here. Names are used to say which service a fact is about.
Or skip all of that
Or let ManyCP fill it in for you
ManyCP fills in every field and links straight to the form. You click send. On Pro, ManyCP files it by hand for you.
ManyCP prepares
- The name, description and URL Glama's form asks for
- A glama.json for your repo root, so you can claim the listing
You do
- Sign in and pass the robot check
- Add the Dockerfile on Glama if you run from source