mcpbeat Sign in

HeyClaude — Claude & AI workflow directory MCP Server

answering

HeyClaude — Claude & AI workflow directory is answering right now. Last checked 12 min ago. 66 installs a week from npm. It exposes 28 tools. Last commit 17 Aug 2026.

Search the HeyClaude directory of Claude Code agents, MCP servers, skills, and tools.

Installs per day peak 19 · avg 6 · +230% w/w
a month agotoday
Uptime history 91 days of history · worst day 89%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
28
Tools
read from the server
243 ms
Response time
average over 24h
66
Installs / week
npm and PyPI

What the code does

We read the source, 4 d ago · tools taken from the live server · rules 995398eba69f

In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

  "d09GRgABAAAAAEJcAA8AAAAAfmwAAQABAAAAAAAAAAAAAAAAAAAAAAAAAABHREVGAAABWAAAAMIAAAEoI4Eb6EdQT1MAAAIcAAAMCgAAJDLdCzCtR1NVQgAADigAAAJpAAAEzo13izJPUy8yAAAQlAAAAE4AAABgE78V51NUQVQAABDkAAAAJgAAACp5kmqBY21hcAAAEQwAAAGdAAACWoztc+FnYXNwAAASrAAAAAgAAAAIAAAAEGdseWYAABK0AAAmpgAAQWwIW5GVaGVhZ…
  "d09GRgABAAAAAEJcAA8AAAAAfmwAAQABAAAAAAAAAAAAAAAAAAAAAAAAAABHREVGAAABWAAAAMIAAAEoI4Eb6EdQT1MAAAIcAAAMCgAAJDLdCzCtR1NVQgAADigAAAJpAAAEzo13izJPUy8yAAAQlAAAAE4AAABgE78V51NUQVQAABDkAAAAJgAAACp5kmqBY21hcAAAEQwAAAGdAAACWoztc+FnYXNwAAASrAAAAAgAAAAIAAAAEGdseWYAABK0AAAmpgAAQWwIW5GVaGVhZ…
Run aws configure to set credentials. Ensure AWS_REGION, AWS_ACCESS_KEY_ID, and AWS_SECRET_ACCESS_KEY are in environment or ~/.aws/credentials file.
- kubeval (optional, for schema validation)
    Docker daemon accessible (via Unix socket /var/run/docker.sock or TCP

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Nothing serious here today

Today is the operative word: we check HeyClaude — Claude & AI workflow directory every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add heyclaude --transport http https://heyclau.de/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://heyclau.de/api/mcp
~/.codex/config.toml
[mcp_servers.heyclaude]
url = "https://heyclau.de/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "heyclaude": {
      "url": "https://heyclau.de/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "heyclaude": {
      "type": "http",
      "url": "https://heyclau.de/api/mcp"
    }
  }
}

Available tools 28

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

submission
submission.duplicates
Search generated registry artifacts for likely duplicate entries before a user opens a submission PR.
submission.examples
Fetch read-only category examples and templates for faster, more accurate HeyClaude submissions.
submission.guidance
Fetch category-specific HeyClaude contribution guidance, required fields, and review expectations.
submission.policy
Fetch HeyClaude's read-only submission, artifact, import, and maintainer-review policy for contributors and agents.
submission.prepare
Build a read-only maintainer-reviewed HeyClaude submission draft with canonical PR text and URLs.
submission.review
Review a HeyClaude submission draft locally for schema errors, duplicate risk, and maintainer checklist items without writing to GitHub.
submission.schema
Fetch read-only HeyClaude submission schemas for PR-first intake by category.
submission.urls
Build prefilled HeyClaude submit and review URLs for a validated PR-first submission draft without making write calls.
submission.validate
Validate a HeyClaude content submission draft locally without creating GitHub issues, pull requests, or publishing content.
registry
registry.feeds
List read-only HeyClaude registry feeds, category feeds, platform feeds, and artifact locations.
registry.info
Fetch read-only HeyClaude MCP package, registry, tool, and public rate-limit metadata.
registry.list
List read-only HeyClaude entries with bounded pagination and optional category, platform, tag, and query filters.
registry.plan
Plan a read-only Claude or Codex workflow toolbox from ranked HeyClaude registry entries. Each entry includes an inline install block (install command, config snippet, download URL) and the recommended stack is summarized as a copy-pasteable installPlan, alongside trust and follow-up guidance.
registry.recommend
Answer 'what should I use to do X' in one call. Given a plain-language task (and optional platform/category), returns the best-match HeyClaude entries ranked by fit — each with why it fits, trust summary, disclosed safety/privacy notes, and an inline install block — plus a topPick and a consolidated installPlan. Unlike workflow.plan it does not force category diversity; it returns the genuinely best matches. Collapses the search → compare → detail → asset loop into a single answer-shaped response.
registry.search
Search read-only HeyClaude registry entries by query, category, exact tag, and skill platform compatibility.
registry.stats
Fetch aggregate read-only registry stats, freshness, category counts, and real source-signal coverage.
registry.updates
List recently added or upstream-updated HeyClaude entries from generated registry metadata.
entry
entry.asset
Fetch the category-aware copy/install asset for a HeyClaude entry without writing local files. Pass assetType (e.g. 'install_command', 'config_snippet') to return only that asset and avoid the full_content/script payloads when you do not need them.
entry.compare
Compare 2-5 read-only HeyClaude entries by fit, category, platforms, source metadata, and install complexity.
entry.coverage
Compare 2-5 HeyClaude entries side by side by how much trust metadata they disclose (source, package, safety, privacy, and review provenance) and rank them by deterministic signal coverage. This measures disclosed-metadata completeness only; it is not a malware scan, a safety verdict, or installation approval, and a higher score does not mean an entry is safe.
entry.detail
Fetch a read-only HeyClaude registry entry detail payload by category and slug. By default (bodyMode='excerpt') the body markdown is trimmed to a short lead and large copyable fields are omitted to conserve context, with bodyChars/bodyTruncated/omittedFields describing what was dropped; pass bodyMode='full' for the complete content or 'none' to drop the body entirely. Use entry.asset to retrieve omitted install/script content.
entry.related
Fetch read-only related HeyClaude entries based on category, tags, platforms, keywords, and source metadata.
entry.safety
Review 1-5 HeyClaude entries for source, package, safety, and privacy metadata fit before install or recommendation. This is a metadata review only and does not provide malware scanning, automatic safety guarantees, or installation approval.
entry.trust
Explain deterministic trust, source, package, safety, privacy, and review metadata signals for one HeyClaude entry. This is a metadata review only and does not provide malware scanning, automatic safety guarantees, or installation approval.
install
install.adapter
Fetch generated read-only platform adapter content, currently Cursor rule adapters for skill packages.
install.compatibility
Fetch platform compatibility metadata for a HeyClaude skill entry.
install.guidance
Fetch read-only install, config, usage, and package guidance for a HeyClaude entry.
install.setup
Fetch read-only MCP client setup snippets for Codex, Claude Desktop, Cursor, Windsurf, or remote HTTP clients.

Endpoints

URLTransportStateLatencyChecked
https://heyclau.de/api/mcp streamable-http answering 3457 ms 12 min ago

Alternatives to HeyClaude — Claude & AI workflow directory

same job, measured the same way
Swarmnest
by swarmnest

Search AI agent tools, MCP servers and Skills. Verified agents post Field Reports and on The Hive.

21 tools answering
Toolfactory
by goatinahat

Build an agent tool once; ship it as Agent Skills, MCP servers, Agent Plugins / Claude / Codex

180 installs/wk local only
A2asearch MCP
by tadas-github

Search 10,000+ AI agents, MCP servers, and CLI tools via A2ASearch from any MCP client.

51 installs/wk local only
Claude Code Organizer
by mcpware

Organize Claude Code memories, skills, MCP servers, commands, agents, rules via drag-and-drop.

267 installs/wk local only
Marketing Skills Directory
by sandeepkelvadi

Search, browse & read 340+ Claude Code marketing & SEO skills from any MCP client.

9 tools answering
ContextStream MCP Server
by contextstreamio

ContextStream MCP server for code context, memory, search, and AI tools.

3 749 installs/wk local only
CodeTrendy
by codetrendy

Search the CodeTrendy directory of websites and tools. Read-only, no API key.

7 tools answering
Ailist MCP
by hifriendbot

MCP server for AiList — search and discover Ai projects from Claude Code

42 installs/wk local only

HeyClaude — Claude & AI workflow directory — questions

Answers built from our own checks of this server.

What can HeyClaude — Claude & AI workflow directory do?
It exposes 28 tools, read directly from the server on our last check. Among them: entry.asset, entry.compare, entry.coverage, entry.detail, entry.related, entry.safety and 22 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is HeyClaude — Claude & AI workflow directory mostly used for?
Its tools cluster around submission, registry and entry. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is HeyClaude — Claude & AI workflow directory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 243 ms. The bar chart above shows every period we have measured.
How do I connect HeyClaude — Claude & AI workflow directory?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does HeyClaude — Claude & AI workflow directory need an API key?
No. HeyClaude — Claude & AI workflow directory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 28 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is HeyClaude — Claude & AI workflow directory?
It answers our handshake in 243 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use HeyClaude — Claude & AI workflow directory?
The npm package @heyclaude/mcp was installed 66 times in the last week. Week over week that is +230%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is HeyClaude — Claude & AI workflow directory open source?
The code is open source: it is published under the MIT licence, written in MDX, 305 stars on GitHub and 2 open issues. The licence covers the code in the repository, not the hosted service at heyclau.de, which runs on its operator's own terms.