MCP

Ask your logs a question from Claude or any MCP-compatible AI tool. Paid plans only.

MCP ships on every paid plan (Starter and up) — see Plans & limits. This is a new capability that's rolling out shortly; if it isn't live on your plan yet, check back soon.

helloLOG exposes a Model Context Protocol server so you can ask an AI tool about your own activity log instead of digging through the dashboard by hand — "did anyone touch checkout settings this week", "who published that page", "show me failed logins from the last 24 hours".

Connect with a site key and the server is scoped to one site — the same as the read API, it can only ever see that site's events and stats. Connect with an account key instead and you also get tools for managing sites and querying events across your whole account — see Connect with an account key below.

Connect

URL

https://api.hellolog.io/v1/wordpress-activity-audit-log/mcp

Header

Authorization: Bearer <your site key>

Claude Code

Terminal

claude mcp add --transport http hellolog \
  https://api.hellolog.io/v1/wordpress-activity-audit-log/mcp \
  --header "Authorization: Bearer <your site key>"

Claude Desktop

Add a remote HTTP server with the same URL and header from Claude Desktop's connector settings.

What it can see

With a site key, the server answers questions grounded in that site's own event stream — recent activity, counts and breakdowns, and lookups by user, object, or event type. It's read-only: nothing an AI tool does through MCP with a site key can change your site or your logs.

An account key adds tools that do change things — creating, renaming, reactivating and deleting sites, and minting or revoking their keys. See below.

Connect with an account key

Same server, same URL — connect an account key instead of a site key and you get seven extra tools: managing sites across your account, plus event queries that aren't limited to one site.

URL

https://api.hellolog.io/v1/wordpress-activity-audit-log/mcp

Header

Authorization: Bearer <your account key>

Tool	What it does
`list_sites`	List every site on your account, with status, retention, and its `group_id`/`group_name` (`null` if ungrouped).
`create_site`	Register a new site and mint its first site key, returned once.
`rename_site`	Set or clear a site's display name.
`activate_site`	Reactivate a paused site.
`delete_site`	Permanently delete a site, its keys, and its events — requires explicit confirmation.
`mint_site_token`	Issue an additional site key for an existing site.
`query_events`	Read events for one site, one group, or across every site on the account.

Site keys still connect and still work — they get the same three read-only tools as before, scoped to that one site. The account key is the one that can manage sites.

Only a site key or an unscoped account key connects here. Group-scoped keys (goal_grp_...) aren't supported over MCP yet — connecting one is rejected rather than silently narrowed to its group. Use a group key against the Account API directly instead.

Groups themselves — creating, renaming, deleting, or moving a site into one — aren't exposed as MCP tools yet; use the Account API or the dashboard's Sites page for that. query_events' optional group_id argument and list_sites' group fields are the only group-aware surface here so far.

Example prompts

Create a site for shop.example.com and give me its token

Show yesterday's critical events across all my sites

Show this week's events for everything in my "Agency clients — Acme" group

Revoking access

MCP access is tied to whichever key you connected with, so it follows the same rules as the read API and the Account API: rotate or revoke the key from the dashboard and the connection stops working within seconds — no separate step needed.

Reseller accounts

Grant an account unlimited plan limits with the operator-only reseller flag.

AI & your data

What AI access does and doesn't mean for your logs.