Awareness Days MCP

Give a compatible AI assistant four read-only tools for awareness-day dates, context and recorded coverage. Both hosted and local connections use your private Data API key.

Hosted connection

Use a client that supports authenticated Streamable HTTP with an explicit request header. This service has no OAuth flow. A URL field alone does not establish compatibility with a particular assistant or plan.

Hosted MCP endpoint
https://www.awarenessdays.com/wp-json/ad-data/v1/mcp
Transport
Stateless JSON Streamable HTTP, POST only. No sessions or SSE stream.
Authentication header
Authorization: Bearer YOUR_AD_API_KEY, or X-API-Key: YOUR_AD_API_KEY.
Content negotiation
Content-Type: application/json; Accept includes application/json and text/event-stream.

Initialize the connection with a supported protocol version, then include the negotiated MCP-Protocol-Version header. Supported versions are 2026-07-28, 2025-11-25 and 2025-06-18; a documented legacy missing-header compatibility case also exists.

Local connection

For an assistant that supports local stdio MCP servers, open Data Tools, create a key and download the reviewed CLI/MCP package. Node.js 20 or later is required.

Install the downloaded package
npm install -g ./awarenessdays-data-0.1.0.tgz
Local MCP configuration
{
    "mcpServers": {
        "awarenessdays": {
            "command": "awarenessdays-mcp",
            "env": {
                "AD_API_KEY": "YOUR_AD_API_KEY"
            }
        }
    }
}

Use your client’s private environment or secret settings. The value above is a placeholder; do not share a completed configuration. If global commands are unavailable to the client, use its supported absolute-path command setting. This package is downloaded from your account; no npm registry or npx installation is claimed.

The four tools

ToolInputsPurpose
awarenessdays_get_status{}Available years, source timestamps and account allowance.
awarenessdays_get_facets{"year":"2027"} (year optional)Exact filter labels for the requested coverage.
awarenessdays_search_events{"year":"2027","q":"community","page":1,"per_page":25}One page of matching occurrences. Read every page before claiming completeness.
awarenessdays_get_event{"key":"KEY_FROM_SEARCH"}One occurrence’s dates, context, links and available metadata.

Responses include structured JSON and equivalent text. Tools cannot change events, favourites, views or subscriptions. They use the same records and account allowance as the REST API.

Prompts to try

  • “Check the available years and categories, then find community events for my planning period. Link each result to its guide.”
  • “Find relevant health awareness dates for a wellbeing content calendar. Tell me which region each event applies to.”
  • “Show the recorded context for this occurrence and flag missing information before we draft a campaign.”

Ask the assistant to preserve source links, unknown values and pagination. The tools look up records; they do not independently verify every organiser’s schedule.

Using the data in your own chatbot

Your application can call the REST API directly from its backend and expose only the read operations it needs. Use the public OpenAPI contract and API guide to define tool parameters. Keep the key in your server environment and retain available guide links in the assistant’s answer.