cyanheads-mcp-server
Server Details
Fleet discovery for the cyanheads MCP ecosystem — semantic search + install snippets.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cyanheads/cyanheads-mcp-server
- GitHub Stars
- 1
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 2 of 2 tools scored.
Each tool has a clear, distinct purpose: one searches the catalog, the other retrieves detailed entries. There is no overlap or ambiguity.
Both tools follow a consistent snake_case pattern with the server prefix 'cyanheads_' and a verb_noun structure (search_catalog, describe_entry).
With only two tools, the set is minimal but well-suited for a read-only catalog server. A third tool for listing all entries might be beneficial, but the count is otherwise appropriate.
The tools cover the essential operations for a catalog: searching and retrieving detailed info. However, missing listing or updating capabilities suggests minor gaps if the catalog is expected to be dynamic.
Available Tools
2 toolscyanheads_describe_entryDescribe Fleet Tool or ServerRead-onlyInspect
Return the description and install snippets for a named tool or server. For tools: the description and the server it belongs to. For servers: local (stdio, via npx) install snippets for every published server, plus remote (HTTP) connection snippets when a hosted endpoint exists — for every supported client, or one client via the client parameter. Call cyanheads_search_catalog first to find valid names.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Whether name refers to a tool or server. Omit to auto-detect: names containing underscores are treated as tools; names containing hyphens are treated as servers. | |
| name | Yes | Tool name (snake_case, e.g. "earthquake_search") or server name (kebab-case, e.g. "earthquake-mcp-server"). 1-64 characters. Use cyanheads_search_catalog to discover valid names. | |
| client | No | Return install snippets for this client only (both local and remote transports when available). Omit to return snippets for all supported clients. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The resolved entry — either a tool detail or a server detail depending on the resolved kind. |
cyanheads_search_catalogSearch Fleet Tools and ServersRead-onlyInspect
Search fleet tools and servers by natural-language description. Returns ranked matches with brief summaries and the server each tool belongs to. Use scope "servers" to find which server handles a workflow; use the default scope "tools" to find specific tools. Call cyanheads_describe_entry on a result name to get install snippets and the connection URL.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (1-20). Default 5. | |
| query | Yes | Natural language search query. Describe what you want to accomplish, a workflow, or a capability area. 1-500 characters. | |
| scope | No | What to search. "tools" returns individual tool matches; "servers" returns server-level matches. | tools |
| category | No | Filter by catalog category. Omit to search all categories. |
Output Schema
| Name | Required | Description |
|---|---|---|
| scope | Yes | Scope that was searched. |
| notice | No | Guidance when no results matched — e.g. how to broaden the query or try a different scope. Absent on successful result pages. |
| results | Yes | Ranked matches, best first. |
| servers | No | Roll-up of distinct servers across the full match set, before the limit slice. Present only for scope "tools". Ordered by topScore desc (name-tiebroken); capped at 10. Use serversTotal to see how many distinct servers matched in total. |
| totalCount | Yes | Total relevant matches before the limit was applied. |
| serversTotal | No | Total distinct servers in the full match set (before the cap of 10 is applied). Present only when servers is present. |
| effectiveQuery | Yes | The query that was searched. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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.
Discussions
No comments yet. Be the first to start the discussion!