automate-glama-submit

mcp
Security Audit
Warn
Health Warn
  • No license — Repository has no license file
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 14 GitHub stars
Code Warn
  • process.env — Environment variable access in index.js
  • network request — Outbound network request in index.js
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Bulk-submit all your MCP server repos to glama.ai in one command.

README.md

glama-submit

Bulk-submit all your MCP server repos to glama.ai in one command.

Glama indexes MCP servers via a glama.json file in each repo root. This tool automatically finds every MCP repo in your GitHub account and commits that file to each one.

How it works

  1. Fetches all your public GitHub repos
  2. Filters for MCP repos (by name, description, or topic containing mcp / model-context-protocol)
  3. Commits a glama.json to each repo's default branch
  4. Glama crawls GitHub and your repos appear at glama.ai/mcp/servers within ~24h

Usage

GITHUB_TOKEN=ghp_... GITHUB_USERNAME=yourname npx glama-submit

Dry run (preview only, no changes):

GITHUB_TOKEN=ghp_... GITHUB_USERNAME=yourname npx glama-submit --dry-run

Requirements

Token setup

  1. Go to github.com/settings/tokens/new
  2. Check public_repo scope
  3. Generate and copy the token

What gets committed

A glama.json is added to each MCP repo root:

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

Repos that already have a valid glama.json are skipped automatically.

MCP detection

A repo is considered an MCP server if its name, description, or GitHub topics contain any of:

  • mcp
  • model-context-protocol
  • modelcontextprotocol
  • model context protocol

License

MIT

Reviews (0)

No results found