EveryMCP
← All marketplace guides
Glama logoGlama
Longtail ecosystem•Path checked

Glama MCP registry and gateway

Glama is a community directory and gateway that indexes GitHub servers and public remote connectors, with tool-level discovery and optional hosted access.

The brand reference above links to an official platform source. EveryMCP is an independent directory and is not endorsed by this platform.

Destination type

Community directory

Integration mode

Hosted and local

Eligibility and connection boundary

The checked FAQ describes GitHub repository submissions and HTTPS Streamable HTTP connectors. Optional test credentials or OAuth details can help Glama verify a private connector path.

Review or publication path

Glama describes automated license, security, and health checks for indexing. Unhealthy connectors remain pending; healthy submissions are public by default and discoverable.

Cost and terms

Glama's public homepage says listing a server is free. Hosting, gateway, managed credentials, and usage features have separate terms that should be checked before enabling them.

Preparation checklist

  1. 1.Use a public GitHub repository for a local server or an HTTPS Streamable HTTP endpoint for a remote connector.
  2. 2.Prepare a concise name, description, tool metadata, and the minimum test credential or OAuth flow needed for health checks.
  3. 3.Review the public-by-default behavior and sensitive-data logging implications before enabling a hosted gateway.
  4. 4.Retain the listing, health result, claim or challenge receipt, and deprecation path as separate evidence.

Open questions

  • • Current indexing, claim, and connector verification behavior for a particular server.
  • • Whether a local package or remote endpoint should be listed first for the intended audience.
Receipt boundary: A connection, a submitted PR, or a registry record does not prove marketplace approval. Keep the platform response, version, review state, and rollback plan with the release evidence.