The GTM MCP Directory
Directory / MCP Layer / Glama (MCP directory)

Glama (MCP directory)

MCP not applicable Gate unknown MCP Layer RESEARCHED Checked 2026-08-24 CLI: glama-submit (community)
RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: glama.ai · entry id 07-glama · source 07-mcp-infrastructure.md line 122

What it does
A large searchable registry/catalog of open-source MCP servers (77,000+ listed as of this check), filterable by language, hosting type (remote/local/hybrid), capability, and category; also offers separate hosting services.
AI features, separated from automation with an AI label on it
none - a catalog/search layer, not an AI product.
RevOps role
Useful as a discovery/search tool for finding a self-hosted or community MCP server for a niche need; mainstream GTM/CRM platforms (Salesforce, HubSpot, Slack, Gmail) were not prominently featured in what was surfaced - the catalog skews toward databases, dev tools, and self-hosted/local-first servers.
MCP server
Status bucket
MCP not applicable
Auth
Varies per listed server; Glama promotes several "no API key required" servers but does not itself broker auth for the catalog as a whole the way Smithery's agent.pw does.
Parsed URLs
1 found in the mcp_url field

An MCP server is not a meaningful question for this entry. The status was established on 2026-08-24.

mcp_status, verbatim from the file:

n/a (Glama is the directory itself)

mcp_url, verbatim from the file:

https://glama.ai/mcp/servers

Command line

This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing.

Binary
glama-submit
Status
community CLI, third party
Strongest evidence
npm
Harvested
2026-09-27

Install, as the source shows it:

npm install -g glama-submit

quoted from https://www.npmjs.com/package/glama-submit on 2026-09-27, via npm, a third party source

Packages seen, with the version on 2026-09-27:

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

Access gate
Gate bucket
Gate unknown
Can a solo operator reach it
Not established

api_gate, verbatim from the file:

unknown (pricing page referenced but not disclosed in the fetched content)

949 of 1252 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess.

API documentation

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

On GitHub

github.com/glama-ai tied to the vendor by rule 3, account website https://glama.ai/ has the vendor's domain, confidence strong

Public repositories
3, forks excluded, as read on 2026-09-08
Mention MCP
1 of them
Look like CLIs
0 of them
Latest push
2026-09-04

The five most recently pushed, on 2026-09-08:

RepositoryKindDescriptionStarsPushedLatest release
tool-definition-quality-scoreotherAn open framework for scoring how well an MCP tool definition communicates to an AI agent – the Tool Definition Quality...322026-09-04
lightportotherA lightweight AI gateway that makes LLM providers OpenAI-compatible.172026-08-16v2.11.0
rjsf-validator-cfworkerotherThe @cfworker/json-schema based validator for @rjsf/core52026-01-13v1.0.2

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

Jobs it can do

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

Sources

2 source URLs. Raw sources field, verbatim:

https://glama.ai/mcp/servers, https://glama.ai/api/mcp/openapi.json

Notes, verbatim from the file
Glama's emphasis on local-first/self-hosted servers makes it a better fit for privacy-conscious infra teams than for someone looking for one-click hosted GTM connectors. [api_gate 2026-08-25] Re-checked and left unknown, honestly: plans are cheap and self-serve (free for open-source MCP servers, then $9/mo Starter, $26/mo Pro, $80/mo Business) and a REST directory API exists whose OpenAPI spec requires bearerAuth on every endpoint, but no loadable Glama page states which plan issues that token; the API reference page is client-rendered and returns nothing to a plain fetch. Checked against https://glama.ai/api/mcp/openapi.json.
Provenance
Entry id
07-glama
Source file
07-mcp-infrastructure.md
Source line
122
Tier
RESEARCHED
last_checked
2026-08-24
Data baked
2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.