One AI endpoint to search and call 22k+ MCP servers; 50+ hosted tools work instantly, no key.
通过网关代理调用某个远程 MCP 服务的具体工具，并把结果原样返回。
【这是调用平台 MCP 的第三步】在 search_servers 找到服务、list_server_tools 拿到工具名与
入参 schema 后，调用本工具实际执行。网关会向目标 MCP 发起 initialize + tools/call（超时 30 秒），
兼容 Streamable HTTP 与 SSE。
参数：
endpoint: 目标远程 MCP 端点 URL（必须是平台库中已登记的地址，否则拒绝，防 SSRF）。
tool_name: 要调用的工具名（来自 list_server_tools）。
arguments: 工具入参字典，按该工具 inputSchema 填写。例如 {"city": "青岛", "days": 3}。
返回：目标工具的执行结果（content 文本/结构化内容原样透传，isError 标识是否业务错误）。
| Name | Required | Description | Default |
|---|---|---|---|
| endpoint | Yes | ||
| arguments | No | ||
| tool_name | Yes |
列出某个远程 MCP 服务提供的全部工具（工具名、描述、入参 schema）。
【这是调用平台 MCP 的第二步】在 search_servers 找到目标服务后，传入它的 server_id
（或直接传 endpoint_url），网关会以 MCP 客户端身份向目标服务发起 initialize + tools/list，
兼容 Streamable HTTP 与旧版 SSE 两种传输（超时 15 秒）。
参数：
server_id: 平台目录中的服务 ID（来自 search_servers 返回的 id）。
endpoint: 也可直接给远程 MCP 端点 URL；但该 endpoint 必须已在平台库中登记（否则拒绝，防 SSRF）。
二选一，优先使用 server_id。
返回：目标服务的工具清单 [{name, description, inputSchema}] 与使用的传输类型。
拿到工具名后，用 call_server_tool(endpoint=..., tool_name=..., arguments=...) 调用。
| Name | Required | Description | Default |
|---|---|---|---|
| endpoint | No | ||
| server_id | No |
搜索 MCP Marketplace 平台目录中已收录的 MCP 服务（只读，共约 2.2 万个）。
【这是调用平台 MCP 的第一步】当你需要某个能力（如"查天气""查汇率""查热搜""查IP"）时，
先用本工具按关键词检索，拿到 server_id 与 endpoint_url，然后：
- 用 list_server_tools(server_id=...) 查看该服务提供哪些工具；
- 再用 call_server_tool(endpoint=..., tool_name=..., arguments={...}) 实际调用。
参数：
query: 搜索关键词，中英文均可。支持多个关键词（空格分隔，AND 匹配），
对名称(name)和描述(description)做模糊匹配。例如 "天气"、"weather"、"热搜 微博"。
limit: 返回条数上限，默认 10，最大 30。
返回：匹配的 MCP 列表，每条含：
- id / name / slug / description（描述摘要）
- endpoint_url: 远程 MCP 端点（若有；以 http/https 开头则 remote_direct=true，可直接远程调用）
- remote_direct: 是否远程可直连
- alive / tools_count / checked_at: 平台能力验证状态（alive=1 表示最近验证存活，排在前面）
排序：验证存活(alive=1)且有远程端点的优先，其次按名称相关度。
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes |
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
call_server_toollist_server_toolssearch_serversClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
One connector for 15,000+ MCP servers plus your team's private MCPs, from any AI client.
The OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call.
Search and install 4,000+ security-scanned MCP servers from inside any MCP-aware AI client.
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
Add one secure layer between your agents and this server.
Score is being calculated.
