HeyClaude MCP Server

Overview

The official HeyClaude MCP server exposes the public HeyClaude registry to MCP clients. It is designed for read-only discovery: search registry entries, fetch details, inspect platform compatibility, copy install guidance, discover feeds, and prepare reviewable content submissions.

The server does not publish content, create GitHub issues, open pull requests, manage accounts, write local project files, or mutate editor configuration. Submission helpers validate drafts and generate prefilled HeyClaude submit URLs for a human-reviewed PR-first workflow.

Tools

• search_registry: search public registry entries by query, category, and platform.
• get_entry_detail: fetch an entry detail payload by category and slug.
• get_compatibility: inspect skill platform compatibility metadata.
• get_install_guidance: fetch install commands, config snippets, package links, and usage notes.
• get_platform_adapter: fetch generated platform adapter content such as Cursor rule adapters for skills.
• list_distribution_feeds: discover registry JSON, RSS, Atom, category, platform, and artifact feeds.
• get_submission_schema: inspect category-specific submission fields.
• validate_submission_draft: validate a content submission draft without making write calls.
• search_duplicate_entries: check for likely duplicate registry entries before submitting.
• build_submission_urls: build prefilled HeyClaude submit and review URLs.
• get_category_submission_guidance: fetch category-specific contribution guidance and review expectations.

Install

Remote endpoint through mcp-remote

Use this when your MCP client expects a stdio command but you want to connect to the hosted HeyClaude endpoint.

{
  "mcpServers": {
    "heyclaude": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://heyclau.de/api/mcp"]
    }
  }
}

Streamable HTTP endpoint

Use the hosted endpoint directly if your MCP client supports remote Streamable HTTP servers.

https://heyclau.de/api/mcp

Local stdio from the repository

Use this when developing HeyClaude locally or testing generated registry artifacts before deploy.

pnpm --filter @heyclaude/mcp start

Set HEYCLAUDE_DATA_DIR=/absolute/path/to/apps/web/public/data if you need to point the server at a specific generated artifact directory.

Example prompts

Search HeyClaude for MCP servers related to GitHub.

Show install guidance for mcp/github-mcp-server.

Validate this HeyClaude content submission draft and build a PR-first submit URL.

Find possible duplicate entries before I submit this new Claude skill.

Security model

• Read-only registry artifacts are the source of truth.
• Hosted MCP requests are schema validated and rate limited.
• Submission tools return validation reports and URLs only.
• No GitHub tokens, OAuth grants, API keys, PR creation, or issue creation are exposed through MCP.
• No local project files, .cursor, .claude, or MCP client config files are written by the server.
• Accepted submissions remain maintainer reviewed before content is imported.

Troubleshooting

The client cannot connect to the hosted endpoint

Confirm the client supports Streamable HTTP MCP servers. If it only supports stdio, use mcp-remote with https://heyclau.de/api/mcp.

Search returns no results

Try a broader query or pass only one filter at a time. Categories use HeyClaude slugs such as agents, mcp, tools, skills, rules, commands, hooks, guides, collections, and statuslines.

A submission draft is invalid

Call get_submission_schema for the target category, then pass the required fields into validate_submission_draft. The MCP server will report missing fields, unsafe URLs, likely duplicates, and the next review step.

I need to publish content automatically

That is intentionally outside the MCP v1 boundary. Use the generated submit URL or PR draft, then let the maintainer-reviewed import workflow handle accepted submissions.