Claude Code
Claude Code can read your fivebar stats over MCP, and answer questions about them.
Ask it about your sites in your own words, such as why traffic jumped on Tuesday, and it answers from your figures, following fivebar’s rules about what they mean. Working in your site’s code, it can also add fivebar to it and check it’s working. Connecting is adding fivebar’s address, signing in and choosing Allow, with no key to copy.
Add fivebar
Run:
claude mcp add --transport http fivebar https://fiveb.ar/api/mcpThat adds it for you, in the project you’re in. To have it in every project, put --scope user
before fivebar. To share it with everyone working on the project, in its .mcp.json,
put --scope project there instead.
Sign in
In Claude Code, run /mcp, choose fivebar, then Authenticate. Or, from the shell, run
claude mcp login fivebar.
fivebar opens in your browser. Sign in if you need to, check that the page names Claude Code, and choose Allow. Claude Code can then read the stats of every site on your Sites page, and changes nothing of yours unless you also tick the box to let it change settings.
Try it
Type / to find fivebar’s ready-made questions, such
as /fivebar:weekly_report.
Ask Claude Code about your sites in your own words, such as:
- Which pages did best last week, and where did their visitors come from?
- How does this month compare with last month so far?
- How many people are on my site right now?
Removing it
claude mcp remove fivebarTo sign out and keep it, choose Clear authentication under /mcp, or run claude mcp
logout fivebar.
To stop Claude Code reading your stats from fivebar’s side, disconnect it in Settings.
Good to know
- Signed in to Claude Code with a Claude account that has fivebar as a connector, fivebar is there already, with nothing to add.
- If you allow fivebar’s tools without being asked, allow them by name, such as
mcp__fivebar__list_sites, and leave outsend_feedbackand any tool that changes settings, so you see each note and change before Claude Code makes it.
More in Claude Code’s own documentation.