Server Quality Checklist

A "release" on Glama is not the same as a GitHub release. To create a Glama release:

1. Claim the server if you haven't already.
2. Go to the Dockerfile admin page, configure the build spec, and click Deploy.
3. Once the build test succeeds, click Make Release, enter a version, and publish.

This process allows Glama to run security checks on your server and enables users to deploy it.

Read the detailed guide

Create a release to enable server coherence scoring.

Create a release to enable tool definition quality scoring.

• No issues in the last 6 months
• No commit activity data available
• No stable releases found
• No critical vulnerability alerts
• No high-severity vulnerability alerts
• No code scanning findings
• CI status not available

Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

MCP servers without a LICENSE cannot be installed.

This repository includes a README.md file.

No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

Tip: use the "Try in Browser" feature on the server page to seed initial usage.

Add a glama.json file to provide metadata about your server.

If you are the author, simply authenticate using GitHub.

If the server belongs to an organization, first add glama.json to the root of your repository:

{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

Then authenticate using GitHub. Browse examples.

Add related servers to improve discoverability.