HeyClaude MCP Server
Website •
GitHub •
npm •
MCP endpoint •
v0.4.0 release
Read-only Model Context Protocol server for the HeyClaude registry.
It exposes the same public registry surface used by the website and Raycast:
search, entry details, platform compatibility, install guidance, generated
adapters, feed discovery, and safe submission-draft helpers. It does not create
GitHub issues, open pull requests, write local files, publish content, host
packages, or manage accounts.
No API key is required for the public endpoint. Abuse controls are handled with
strict request validation, a 64 KiB body limit, and a dedicated Cloudflare
API_MCP_RATE_LIMIT binding capped at 60 requests/minute/IP in production.
Tools
registry.search - search public registry entries by query, category, and
platform.
registry.recommend - answer "what should I use to do X" in one call: returns
the best-match entries for a plain-language task, each with why it fits, a
trust summary, safety/privacy notes, and an inline install block, plus a
topPick and consolidated installPlan.
server.info - fetch package version, registry generation, tool list,
public access policy, and rate-limit metadata.
registry.list - browse entries with bounded pagination and optional
category, platform, tag, and query filters.
registry.updates - list recently added or upstream-updated entries from
generated registry metadata, optionally filtered with since.
entry.related - find related entries based on category, tags,
platforms, keywords, and source metadata.
entry.detail - fetch an entry detail payload by category and slug.
Defaults to a token-efficient body excerpt (reporting bodyChars,
bodyTruncated, and any omittedFields); pass bodyMode: "full" for the
complete content or "none" to drop the body. Omitted copyable fields are
available via entry.asset.
entry.asset - fetch the category-aware copy/install asset for an
entry, such as full prompt text, config snippets, commands, scripts, or
collection items. Pass assetType (e.g. install_command) to return only
that asset and skip the large full_content/script payloads.
entry.compare - compare 2-5 entries by fit, category, platform support,
install complexity, and source metadata.
registry.stats - fetch aggregate counts, freshness metadata, and real
source-signal coverage without implying popularity when stats are absent.
install.setup - fetch tested setup snippets for Codex, Claude Desktop,
Cursor, Windsurf, and raw Streamable HTTP clients.
install.compatibility - fetch skill platform compatibility metadata.
install.guidance - fetch install commands, config, package, and platform
guidance.
install.adapter - fetch generated adapter content, currently Cursor
rule adapters for skill packages.
feeds.list - discover public JSON, RSS, Atom, and platform
feeds.
submission.schema - fetch category submission fields for PR-first
intake.
submission.validate - validate a content submission draft locally.
submission.duplicates - check generated registry artifacts for likely
duplicates before opening a submission.
submission.urls - build prefilled HeyClaude submit and review URLs for human
review.
submission.guidance - fetch category-specific contribution
guidance and required fields.
submission.prepare - normalize and validate fields, then return a
canonical PR draft plus prefilled submit URL.
submission.examples - fetch category-specific example fields and
templates for more complete submissions.
submission.review - review schema errors, duplicate risk, and
maintainer checklist items before a submission PR is opened.
submission.policy - fetch the read-only submission, artifact, import,
and maintainer-review policy.
entry.trust - explain source, package, safety, privacy, and review
metadata signals for one entry. This is a metadata review only and does not
provide malware scanning, automatic safety guarantees, or installation approval.
entry.safety - compare 1-5 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.
Resources and Prompts
The server also exposes read-only MCP resources:
heyclaude://feeds/directory
heyclaude://category/{category}
heyclaude://entry/{category}/{slug}
Workflow prompts are available for common client flows:
asset.find
submission.prepare
submission.review
install.asset
Local Stdio
The published package defaults to the live HeyClaude MCP endpoint. In this
remote-bridge mode, draft-content helpers that accept private submission fields
(submission.validate, submission.urls, submission.prepare,
and submission.review) are intentionally not exposed or forwarded; use
local artifact mode for those helpers before entering private draft content.
{
"mcpServers": {
"heyclaude": {
"command": "npx",
"args": ["-y", "@heyclaude/mcp"]
}
}
}
Use a custom endpoint when testing a preview/dev deployment:
{
"mcpServers": {
"heyclaude": {
"command": "npx",
"args": [
"-y",
"@heyclaude/mcp",
"--url",
"https://heyclaude-dev.zeronode.workers.dev/api/mcp"
]
}
}
}
Local artifact mode is explicit and intended for development:
pnpm --filter @heyclaude/mcp start:local
Set HEYCLAUDE_DATA_DIR=/absolute/path/to/data, or pass
--local --data-dir /absolute/path/to/data, to point at a generated data
directory.
Example local MCP client config:
{
"mcpServers": {
"heyclaude": {
"command": "pnpm",
"args": ["--filter", "@heyclaude/mcp", "start:local"]
}
}
}
Remote HTTP
The web app also exposes a Streamable HTTP endpoint:
- production:
https://heyclau.de/api/mcp
- dev:
https://heyclaude-dev.zeronode.workers.dev/api/mcp
Validate a deployed endpoint with the SDK-level contract check:
MCP_ENDPOINT_URL=https://heyclaude-dev.zeronode.workers.dev/api/mcp pnpm validate:mcp-endpoint
This check connects with an MCP client, lists tools, calls representative
registry and submission-helper tools, verifies strict argument validation, and
checks the HTTP guards used by the remote route.
Security Boundary
- Read-only registry artifacts only.
- Submission helpers generate URLs and validation reports only.
- No GitHub OAuth, tokens, issue creation, PR creation, or repo writes.
- No local project-file writes or config mutations.
- Remote endpoint requires JSON POST bodies, rejects payloads above 64 KiB, and
uses the dedicated
API_MCP_RATE_LIMIT Cloudflare binding at
60 requests/minute/IP in production.
- Submission tools prepare review drafts only; the MCP server does not perform
GitHub writes or publish submitted content.
- The npm stdio remote bridge does not forward local draft-helper calls that
carry submission fields; run local artifact mode before entering private draft
content.
- Source-backed, content-only PRs may be merged automatically after content
validation, Superagent, and private maintainer-agent review pass. Platform,
workflow, package, and generated-artifact changes are never auto-merged by
this path.
- Community ZIP/MCPB artifacts are review/quarantine material only. Public
HeyClaude-hosted downloads are maintainer-built package artifacts.
npm Release Prep
MCP releases are package-scoped. Website/catalog changes do not create repo-wide
semver releases. The initial public package version is 0.1.0, and GitHub
release tags use mcp-vX.Y.Z.
The npm package artifact is hosted on npmjs.com. GitHub Releases track the
matching package-scoped source tag and release notes, such as mcp-v0.1.2.
Do not publish until the web branch has shipped, the production endpoint has
been verified, and the package smoke test passes. The release checklist is:
MCP_ENDPOINT_REQUIRE_SAFETY_METADATA=1 pnpm validate:mcp-endpoint -- --url https://heyclau.de/api/mcp --strict-tools
pnpm --filter @heyclaude/mcp test
pnpm --filter @heyclaude/mcp pack --dry-run
MCP_PACKAGE_REQUIRE_SAFETY_METADATA=1 MCP_PACKAGE_REMOTE_SMOKE_URL=https://heyclau.de/api/mcp pnpm validate:mcp-package
Publishing should happen through the manual Publish MCP Package GitHub
workflow with npm trusted publishing/provenance enabled for @heyclaude/mcp.