CommunityHunt for developers

CommunityHunt exposes its community and event directory as a public JSON API, an OpenAPI specification, and a Model Context Protocol (MCP) server, so you can build integrations or let an AI agent query the directory directly.

Authentication

Read endpoints (listing and searching communities and events) require no authentication or API key. Write endpoints (submitting a community, claiming a listing, managing events) require a signed-in CommunityHunt session — sign in at /sign-in and call the API from the browser. There is currently no separate API-key system for server-to-server writes.

Quickstart: REST API

Search communities:

curl "https://communityhunt.in/api/communities?search=design&pricing=Free"

Fetch a single community:

curl "https://communityhunt.in/api/communities/<id>"

List upcoming events:

curl "https://communityhunt.in/api/events?search=meetup"

OpenAPI specification

The full API surface — including request/response schemas and the authenticated write endpoints — is described at /openapi.json. Import it directly into Postman, Swagger UI, or any codegen tool.

MCP server for AI agents

CommunityHunt runs a Model Context Protocol server at /mcp using the Streamable HTTP transport. Point an MCP-compatible client (Claude, ChatGPT, or any MCP host) at this URL to get three tools: search_communities, get_community, and list_upcoming_events. No authentication is required — these tools only expose the same public, read-only data as the REST API.

{
  "mcpServers": {
    "communityhunt": {
      "url": "https://communityhunt.in/mcp"
    }
  }
}

Agent guidance

For a plain-text summary of what CommunityHunt is and when an agent should use it, see /llms.txt. Homepage content is also available as Markdown via Accept: text/markdown content negotiation.

Questions

Email hello@communityhunt.in or see the contact page.