Glama

Glama

Glama is an MCP server registry and gateway for teams connecting AI agents to external tools. Glama indexes the Model Context Protocol ecosystem, lets you browse servers by category and search across the tools they expose, and test any server in an in-browser MCP Inspector before you install it. Beyond discovery, Glama runs a gateway that sits in front of MCP servers with request logging, per-tool access control, managed OAuth, and usage analytics. Servers are maintainer-verified, rebuilt continuously, and scored for quality and safety.

Production credibility: Built by Frank Fiegel and launched as an MCP directory on 25 November 2024, days after Anthropic introduced the protocol; bootstrapped with no disclosed outside funding. Self-reported scale in 2026 includes roughly 37,800 indexed servers, about 6,000 hosted connectors, and over a million tool calls per month across 50,000+ developers.

Key Features

• Registry of ~37,800 MCP servers, browsable by category (vendor-reported)
• Full-text search across the tools each server exposes
• In-browser MCP Inspector to test servers without installing them
• One-click hosted connectors run on Glama infrastructure
• Gateway/reverse proxy with logging, per-tool access control, and managed OAuth
• Quality and safety scoring with maintainer verification

Ideal Use Case

Developers and teams who want to vet an MCP server before trusting it — testing it in the browser, checking its quality score, then running it through a gateway that logs calls and enforces access control, rather than installing unreviewed servers straight into a production agent.

How Glama differentiates

Smithery leads with hosting and a router; PulseMCP is directory-and-news. Glama's emphasis is trust and control: the MCP Inspector lets you exercise a server in the browser first, safety scoring flags risky ones, and the gateway adds logging, access control, and managed OAuth in front of whatever you run. For a team whose binding concern is governing what its agents can reach, that inspect-then-proxy path is the differentiator.

FAQ

Q: What is Glama? A: Glama is a registry, in-browser inspector, and gateway for Model Context Protocol (MCP) servers. You discover servers, test them in the browser, and run them behind a gateway with logging, access control, and managed OAuth.

Q: Can I test an MCP server before installing it? A: Yes — Glama's in-browser MCP Inspector lets you connect to and exercise a server's tools without installing anything locally, so you can vet it first.

Q: What does the Glama gateway do? A: The gateway is a reverse proxy in front of MCP servers that adds request logging, per-tool access control, managed OAuth credentials, and usage analytics.

Q: How many MCP servers does Glama index? A: Glama self-reports roughly 37,800 indexed servers and about 6,000 hosted connectors as of 2026; the figure grows continuously as the ecosystem expands.

Q: Is Glama free? A: Glama is free to browse, search, and inspect, with paid tiers for hosted connectors and gateway usage. Check the pricing page for current limits.

tl;dr

Glama is an MCP registry, inspector, and gateway — browse ~37,800 servers, test them in the browser, and run them behind a proxy with logging, access control, and managed OAuth. Bootstrapped, launched November 2024, maintainer-verified with safety scoring. The trust-and-governance pick among MCP directories.