
HeyClaude — Claude & AI workflow directory
Search the HeyClaude directory of Claude Code agents, MCP servers, skills, and tools.
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Search the HeyClaude directory of Claude Code agents, MCP servers, skills, and tools.
How to connect
How to connect HeyClaude — Claude & AI workflow directory to Claude
The server address to paste into Claude settings:
https://heyclau.de/api/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect HeyClaude — Claude & AI workflow directory to ChatGPT
The server address to paste into ChatGPT settings:
https://heyclau.de/api/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect HeyClaude — Claude & AI workflow directory to Cursor
The server address to paste into Cursor settings:
https://heyclau.de/api/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (28)
Raw names from tools/list. Only developers need these.
| registry.search | Search read-only HeyClaude registry entries by query, category, exact tag, and skill platform compatibility. |
| 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.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.updates | List recently added or upstream-updated HeyClaude entries from generated registry metadata. |
| entry.related | Fetch read-only related HeyClaude entries based on category, tags, platforms, keywords, and source metadata. |
| 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.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. |
| registry.stats | Fetch aggregate read-only registry stats, freshness, category counts, and real source-signal coverage. |
| install.setup | Fetch read-only MCP client setup snippets for Codex, Claude Desktop, Cursor, Windsurf, or remote HTTP clients. |
| 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.adapter | Fetch generated read-only platform adapter content, currently Cursor rule adapters for skill packages. |
| registry.feeds | List read-only HeyClaude registry feeds, category feeds, platform feeds, and artifact locations. |
| submission.schema | Fetch read-only HeyClaude submission schemas for PR-first intake by category. |
| submission.validate | Validate a HeyClaude content submission draft locally without creating GitHub issues, pull requests, or publishing content. |
| submission.duplicates | Search generated registry artifacts for likely duplicate entries before a user opens a submission PR. |
| submission.urls | Build prefilled HeyClaude submit and review URLs for a validated PR-first submission draft without making write calls. |
| submission.guidance | Fetch category-specific HeyClaude contribution guidance, required fields, and review expectations. |
| submission.prepare | Build a read-only maintainer-reviewed HeyClaude submission draft with canonical PR text and URLs. |
| submission.examples | Fetch read-only category examples and templates for faster, more accurate HeyClaude submissions. |
| submission.review | Review a HeyClaude submission draft locally for schema errors, duplicate risk, and maintainer checklist items without writing to GitHub. |
| submission.policy | Fetch HeyClaude's read-only submission, artifact, import, and maintainer-review policy for contributors and agents. |
| 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. |
| 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.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. |