Submit
MCP Servers2025-11-25

HeyClaude MCP Server - Access Claude Pro Directory via MCP

Access the complete Claude Pro Directory through HeyClaude's official MCP server. Search prompts, agents, MCP servers, rules, commands, and more directly from Claude Desktop, Cursor, or any MCP client.

mcpdirectoryapitoolscommunityheyclaudeclaude-pro-directorysearchdiscovery

Author

HeyClaude Team

Added

2025-11-25

Setup time

2 minutes

Difficulty

intermediate

Quick use

Install command

1 lines
claude mcp add --transport http heyclaude-mcp https://mcp.heyclau.de/mcp && claude mcp list

Claude config

.claude/settings.json

14 lines
{
  "heyclaude-mcp": {
    "url": "https://mcp.heyclau.de/mcp",
    "oauth": {
      "scopes": [
        "mcp:tools"
      ],
      "resource": "https://mcp.heyclau.de/mcp",
      "tokenEndpoint": "https://hgtjdifxfapoltfflowc.supabase.co/auth/v1/token",
      "authorizationEndpoint": "https://mcp.heyclau.de/oauth/authorize"
    },
    "transport": "http"
  }
}

Source asset

json

14 lines
{
  "heyclaude-mcp": {
    "url": "https://mcp.heyclau.de/mcp",
    "oauth": {
      "scopes": [
        "mcp:tools"
      ],
      "resource": "https://mcp.heyclau.de/mcp",
      "tokenEndpoint": "https://hgtjdifxfapoltfflowc.supabase.co/auth/v1/token",
      "authorizationEndpoint": "https://mcp.heyclau.de/oauth/authorize"
    },
    "transport": "http"
  }
}

Section

Content

Expand

Access the complete Claude Pro Directory through HeyClaude's official MCP server. Search prompts, agents, MCP servers, rules, commands, and more directly from Claude Desktop, Cursor, or any MCP client. Real-time access to our community-driven directory with 11 powerful tools for discovery, search, and content exploration. Supports OAuth 2.1 authentication with resource parameter (RFC 8707), JWT token audience validation, Row-Level Security enforcement, and comprehensive directory access across all categories.

Section

Features

Expand
  • 11 powerful tools for directory exploration (search, trending, popular, recent, related)
  • Real-time access to Claude Pro Directory (live data via authenticated queries)
  • Search with filters, tags, and pagination (max 50 items per request)
  • Trending and popular content discovery (engagement-based sorting)
  • Related content recommendations (semantic similarity and tag matching)
  • One-click .mcpb installation (MCP bundle format support)
  • OAuth 2.1 authentication with resource parameter (RFC 8707 compliance)
  • JWT token audience validation (prevents token passthrough attacks)
  • Row-Level Security (RLS) enforcement (per-user data access control)
  • Streamable HTTP transport (MCP Protocol 2025-06-18)
  • Advanced HeyClaude platform integration with content management, user analytics, and community engagement features
  • Batch operations support for efficient bulk content operations, user management, and analytics processing with automatic rate limit handling and retry logic
  • Real-time platform synchronization capabilities with webhook integration support for monitoring platform events and triggering automated workflows

Section

Use Cases

Expand
  • Search for prompts, agents, and MCP servers (comprehensive directory search)
  • Discover trending content across categories (popularity-based discovery)
  • Get detailed information about specific items (complete metadata retrieval)
  • Find related content based on tags and similarity (semantic recommendations)
  • Browse recently added content (latest directory additions)
  • Access directory from Claude Desktop or Cursor IDE (MCP client integration)
  • Secure token-based directory access (OAuth 2.1 compliant authentication)
  • Row-Level Security compliant queries (per-user data access enforcement)
  • Build automated platform management workflows that sync external systems with HeyClaude for real-time content management and community engagement

Section

Installation

Expand

Claude Code

  1. Run: claude mcp add --transport http heyclaude-mcp https://mcp.heyclau.de/mcp
  2. Verify installation: claude mcp list
  3. Test connection: claude mcp status heyclaude-mcp
  4. Authenticate with OAuth 2.1 flow (authorization code with PKCE)
  5. Grant required permissions (mcp:tools scope)
  6. Verify token audience includes MCP server URL
Claude CodeDetails
  1. Run: claude mcp add --transport http heyclaude-mcp https://mcp.heyclau.de/mcp
  2. Verify installation: claude mcp list
  3. Test connection: claude mcp status heyclaude-mcp
  4. Authenticate with OAuth 2.1 flow (authorization code with PKCE)
  5. Grant required permissions (mcp:tools scope)
  6. Verify token audience includes MCP server URL
Claude DesktopDetails
  1. Open Claude Desktop settings
  2. Navigate to Developer > MCP Settings
  3. Add the following configuration to your claude_desktop_config.json
  4. Save the file and restart Claude Desktop
  5. Authenticate with OAuth 2.1 flow (authorization code with PKCE)
  6. Grant required permissions (mcp:tools scope)
  7. Verify token audience includes MCP server URL
  8. Verify connection in Claude Desktop

Section

Requirements

Expand
  • HeyClaude account (Supabase Auth account required)
  • OAuth 2.1 authentication (authorization code flow with PKCE)
  • Network access to mcp.heyclau.de (HTTPS required, HTTP transport)
  • Understanding of MCP protocol (Model Context Protocol 2025-06-18)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of OAuth 2.1 flow (authorization code with PKCE, resource parameter)
  • Understanding of JWT token audience validation (RFC 8707)
  • Understanding of Row-Level Security (RLS) policies
  • Understanding of tool pagination limits (max 50 items per request, some tools max 20)
  • Optional: Supabase account (for OAuth authentication)

Section

Examples

Expand

Search for MCP servers

Use searchContent tool to find MCP servers matching a query

Search for MCP serversDetails

Use searchContent tool to find MCP servers matching a query

Ask Claude: "Search for MCP servers related to GitHub"
Get trending contentDetails

Use getTrending tool to discover popular agents

Ask Claude: "Get trending agents from the directory"
Get content detailsDetails

Use getContentDetail tool to retrieve full metadata for a specific item

Ask Claude: "Show me details for the github-mcp-server"
Find related contentDetails

Use getRelatedContent tool to discover similar items

Ask Claude: "Find content related to the stripe-mcp-server"
Get Content ItemDetails

Retrieve a content item from HeyClaude with metadata

// Get HeyClaude content item
const content = await heyclaude.content.get({
  content_id: "content-id",
  include_metadata: true
});

Section

Security

Expand
  • OAuth 2.1 authentication with resource parameter (RFC 8707) required
  • JWT token audience validation (prevents token passthrough attacks)
  • Row-Level Security (RLS) enforcement via authenticated Supabase client
  • HTTPS required for all connections (secure transport)
  • Bearer token authentication (Authorization: Bearer header)
  • HeyClaude API keys and access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • HeyClaude OAuth access tokens should be used for third-party integrations to ensure proper access control, token lifecycle management, and automatic token refresh
  • HeyClaude content IDs and user identifiers may expose platform structure and user information - ensure HeyClaude resource identifiers are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for HeyClaude MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • HeyClaude webhook configurations and payloads may contain sensitive content and user data - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Section

Troubleshooting

Expand

OAuth authentication failed or token audience mismatch

Verify OAuth 2.1 flow completed correctly (authorization code with PKCE). Check token audience claim includes MCP server URL (https://mcp.heyclau.de/mcp). Ensure resource parameter (RFC 8707) was included in authorization request. Verify redirect URI matches registered URI in Supabase Auth. Check token not expired (refresh if needed). Review OAuth metadata endpoints: /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server. Ensure JWT token includes correct audience in 'aud' claim. Re-authenticate if token was issued without resource parameter.

OAuth authentication failed or token audience mismatchDetails

Verify OAuth 2.1 flow completed correctly (authorization code with PKCE). Check token audience claim includes MCP server URL (https://mcp.heyclau.de/mcp). Ensure resource parameter (RFC 8707) was included in authorization request. Verify redirect URI matches registered URI in Supabase Auth. Check token not expired (refresh if needed). Review OAuth metadata endpoints: /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server. Ensure JWT token includes correct audience in 'aud' claim. Re-authenticate if token was issued without resource parameter.

JWT token validation errors or missing audience claimDetails

OAuth 2.1 requires resource parameter (RFC 8707) to include MCP server URL in token audience. Verify token was issued with resource parameter in authorization request. Check token 'aud' claim includes https://mcp.heyclau.de/mcp. Re-authenticate if token was issued without resource parameter. Review authorization endpoint: /oauth/authorize (proxies to Supabase Auth with resource parameter). Ensure client uses OAuth 2.1 flow, not OAuth 2.0. Check token expiration and refresh if needed. Verify client ID and redirect URI are correct in Supabase Auth configuration.

Tool execution errors or database query failuresDetails

Check Row-Level Security (RLS) policies allow access for authenticated user. Verify Supabase client authenticated correctly (token in Authorization header). Review tool pagination limits (max 50 items per request, some tools max 20). Check database connection and RPC availability. Review error messages in tool responses for specific issues. Verify category and slug parameters are correct (valid categories: agents, rules, commands, skills, collections, mcp). Check content exists in directory for specified category/slug. Review tool input schema requirements (required vs optional parameters).

Connection errors or endpoint unreachableDetails

Verify network access to mcp.heyclau.de (HTTPS required). Check endpoint URL correct: https://mcp.heyclau.de/mcp (primary), https://mcp.claudepro.directory/mcp (legacy), or direct Supabase endpoint. Test health endpoint: https://mcp.heyclau.de/ (should return server info with version 1.0.0, protocol 2025-06-18). Verify CORS headers allow requests from your client. Check MCP Protocol Version header matches 2025-06-18. Review Mcp-Session-Id header if using session management. Verify HTTP transport (not STDIO) for remote server. Check firewall or network restrictions blocking HTTPS connections.

HeyClaude MCP server authentication errors with API keysDetails

Verify API key is valid and not expired. Check API key permissions match required operations. Ensure API key format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

HeyClaude rate limit errors when processing multiple requestsDetails

Implement exponential backoff retry logic with jitter. Use HeyClaude API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed content data. Check HeyClaude documentation for specific rate limits.

HeyClaude content or user access denied errorsDetails

Verify API key has access to the content or user. Check content permissions and account membership. Ensure API key has required permissions for target operations.

HeyClaude MCP server connection timeouts or network errorsDetails

Check network connectivity and firewall settings. Verify HeyClaude API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

0% complete