Cyanheads Mcp Server
Discover cyanheads MCP servers with semantic search and copy-ready install snippets instead of hand-maintaining a local MCP config spreadsheet.
Overview
cyanheads MCP is a Build-phase MCP server for fleet discovery across the cyanheads ecosystem via semantic search and install snippets.
What is this MCP server?
- Semantic search across the cyanheads MCP fleet using baked embeddings in fleet.json
- Returns install snippets for stdio and remote transports
- stdio @cyanheads/cyanheads-mcp-server and remote https://cyanheads.caseyjhand.com/mcp
- CATALOG_URL default https://caseyjhand.com/fleet.json with CATALOG_REFRESH_SECONDS default 3600
- Server version 0.3.2 with MCP_LOG_LEVEL control
- Package version 0.3.2
- Default catalog refresh interval 3600 seconds
- Fleet catalog schema v2 with baked embeddings per README
What problem does it solve?
Solo builders accumulate dozens of MCP URLs and npm packages without a single agent-queryable index to find and install the right cyanheads server.
Who is it for?
Builders standardizing on cyanheads MCP packages who want one discovery entry point before adding CourtListener, Crossref, CPSC, and siblings.
Skip if: Finding arbitrary non-cyanheads MCPs on the open registry or executing domain API calls without installing the chosen downstream server.
What do I get? / Deliverables
You search the fleet in natural language, get matching servers, and paste generated install blocks into your client config.
- Ranked cyanheads MCP matches from semantic fleet search
- Copy-ready client install configuration for chosen servers
Recommended MCP Servers
Journey fit
Installing and composing MCP tooling is central to the Build phase, but fleet discovery also helps when you first scout which integrations to scope. Semantic catalog search plus install snippets directly supports agent-tooling setup in Claude Code and Cursor.
How it compares
Publisher fleet catalog MCP with semantic search, not a single-domain API integration.
Common Questions / FAQ
Who is cyanheads MCP for?
Solo builders using Claude Code or Cursor who deploy multiple cyanheads MCP servers and want semantic discovery instead of reading each README manually.
When should I use cyanheads MCP?
Use it when scoping agent integrations or refreshing your MCP stack after the fleet catalog updates.
How do I add cyanheads MCP to my agent?
Install @cyanheads/cyanheads-mcp-server with stdio or add https://cyanheads.caseyjhand.com/mcp; optionally override CATALOG_URL and CATALOG_REFRESH_SECONDS.