For developers building AI agents that need external tools, Glama is an MCP metaregistry and gateway that indexes available MCP servers and provides a hosted way to discover, run, and connect them into agent workflows.
Presence & Market Position
Tracked · below panel floor — earned mentions are accruing toward the next scored window.
Measures earned, engagement-weighted share of voice across the GTM voices panel. Methodology →
Glama is positioning itself as an MCP discovery and gateway layer for developers who need to find, run, and connect external tools to agents. Its market footprint is early, but practitioner discussion already centers on the practical problem of navigating a rapidly expanding server ecosystem and identifying usable tools beyond code generation. The product’s role is to make that ecosystem more accessible through a directory and hosted connection path. As MCP moves from an engineering protocol into a broader agent-workflow pattern, Glama provides a practical starting point for tool discovery and integration.
Smithery
Arcade.dev
Anchor Browser
Blaxel
Browse AIShopify, Cloudflare, Databricks, Accenture, Square, Duolingo, Zillow, UiPath, Zomato, Neo4j
Work at Glama? Claim this profile to add customers and case studies.
Business Profile
Glama started as a solo build: Frank Fiegel launched it in November 2024, days after Anthropic introduced the MCP protocol, and has run it independently since with no outside funding disclosed. Under a year and a half later the registry has scaled to tens of thousands of indexed servers, tens of thousands more hosted connectors, and reported usage past a million tool calls a month across 50,000-plus developers, still operated as a one-person company. The business has grown from a simple directory listing into a hosting and gateway product, adding managed infrastructure on top of the original index rather than raising to fund the expansion.
Agent Readiness
Measures how easily your agents can build on it — API, MCP, CLI, SDK, docs depth. Methodology →
Glama's product centers on agent-facing infrastructure: an MCP inspector for testing servers in-browser before wiring them into an agent, one-click hosting that skips Docker and TLS setup, and a gateway adding JSON-RPC logging, per-tool access control, and managed OAuth credentials on top of any hosted server. The build has moved from indexing what exists toward operating the runtime agents actually call, with usage analytics extending visibility past discovery and into how those tool calls perform in production.
IS THIS YOUR BRAND?
Claim this profile
Fact-check your data, add context, and earn the verified badge — free, takes minutes, work email required.
Claim Glama →