Wireboard

io.github.wireboardPublished by GitHub account wireboardv0.1.3Updated Oct 24, 2026

Official MCP server for WireBoard. Lets LLM agents query your analytics in conversation.

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Official WireBoard MCP server that lets an AI assistant query your website analytics — traffic totals, trends, breakdowns, events and live visitors — in natural

What you can do
List sites in the account and show the token owner's identity and abilities, plus the dimensions, metrics and limits the API supports. Retrieve period totals such as visitors, pageviews, bounce rate and visit duration. Get visitor or pageview counts bucketed by hour or day, and per-day history including returning visitors. Break down top rows by dimension (country, device, browser, referrer) and pull per-URL metrics with prefix, contains or exact filters. Query custom events with grouping and filtering, and fetch a real-time snapshot of live visitors, top pages and active sessions. Date ranges can be given in natural language such as last 7 days or this month, always in UTC.
When to use it
Useful when you want to ask about your WireBoard site traffic conversationally instead of opening a dashboard: weekly visitor counts, top referrers, worst-performing pages, event counts by campaign, or what is happening on the site right now.
Requirements
Runs as a local process over stdio, installed either as a Claude Desktop extension file or via the npm package @wireboard/mcp (Node 18+). Requires a WireBoard account and an API token supplied in the WIREBOARD_TOKEN environment variable, minted with the analytics:read and live:read abilities. Network access to the WireBoard API is needed.
Before you install
WIREBOARD_TOKEN is a credential with read scope over every site in the account; keep it out of committed client configs and rotate it if leaked. The server is read-only and cannot modify data. Requests are self-capped at 100 per minute, adjustable via WIREBOARD_MCP_RATE_PER_MINUTE. Analytics data is sent to the AI client you connect.

Installation

In SourceWeft

  1. Open Wireboard in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[WireBoard]

wireboard-mcp

Official Model Context Protocol server for WireBoard.

Lets LLM agents (Claude Desktop, Cursor, VS Code, etc.) query your real-time and historical analytics in conversation. Built on top of the official @wireboard/api JavaScript SDK.

Install

Two ways to install, pick whichever fits your setup.

Option A: Desktop Extension (recommended for Claude Desktop users)

Download wireboard-mcp-x.y.z.mcpb from the GitHub releases page and double-click it. One file works on Windows, macOS, and Linux — Claude Desktop ships its own Node runtime, so there are no system dependencies to install.

Claude Desktop will prompt for your WireBoard API token, store it securely in your OS keychain, and the WireBoard tools become available immediately.

If double-click doesn't open the file, install it via Claude Desktop → Settings → Extensions → Advanced Settings → Install Extension.

Option B: npm install (for Cursor, VS Code, headless / CI, automation)

sh
npm install -g @wireboard/mcp

Requires Node 18+. Then configure your MCP client of choice.

Claude Desktop config

Edit claude_desktop_config.json (Settings → Developer → Edit Config):

json
{  "mcpServers": {    "wireboard": {      "command": "wireboard-mcp",      "env": {        "WIREBOARD_TOKEN": "your_token_here"      }    }  }}

Restart Claude Desktop. The WireBoard tools will appear automatically.

Cursor / VS Code / other MCP clients

Use the same command + env-var pattern in your client's MCP config.

Mint a token

You need a WireBoard API token before either install path will work. Mint one at Settings → API with the analytics:read ability for REST tools and live:read for the live snapshot tool.

What you can ask

Once configured, ask Claude things like:

  • "How many visitors did my site get last week?"
  • "Show me the top 10 referrers for the past 30 days."
  • "What's happening on my site right now?"
  • "Which pages under /checkout have the worst bounce rate this month?"
  • "How many Purchase events fired from utm_source=newsletter yesterday?"
  • "Compare visitor counts day by day for the past two weeks."

Claude will pick the right tool, call it, and answer in natural language.

Available tools

ToolWhat
list_sitesEvery site in the account
get_accountToken-owner identity + abilities
get_aggregatePeriod totals: visitors, pageviews, bounce rate, duration
get_timeseriesOne metric (visitors or pageviews) bucketed by hour or day
get_historyPer-day visitors / returning / pageviews / bounce / duration
get_breakdownTop-N rows by dimension (country, device, browser, referrer, etc.)
get_top_urlsPer-URL metrics with prefix / contains / exact filters
query_eventsCustom event queries with grouping and filtering
get_live_stateReal-time snapshot (live visitor count, top pages, active sessions, etc.)
list_dimensionsMeta: every dimension, metric, and limit the API supports

All tools accept natural date ranges: "today", "yesterday", "last 7 days" (or "30d" shorthand), "this week", "last week", "this month", "last month", or explicit "YYYY-MM-DD..YYYY-MM-DD". Always UTC.

Rate limiting

The MCP proactively caps itself at 100 requests/minute (under the API's 120/minute limit) so LLM bursts space themselves out instead of hitting 429s. Override with the WIREBOARD_MCP_RATE_PER_MINUTE env var if you have a use case that needs different pacing.

The underlying SDK still auto-retries on 429 as a backstop.

Security

  • Treat your token like a credential. It has full analytics:read and live:read scope on every site in the account.
  • Don't commit your MCP client config to a public repo with the token in it. Use an env var or a secret manager and reference it from your config.
  • Revoke and rotate if a token leaks. Settings → API in your dashboard.

The MCP is read-only: it can fetch data, never modify it. The WireBoard public API itself is read-only in v1.

Logging

Logs go to stderr (so they don't interfere with the MCP protocol on stdout).

Source and contributing

Building locally

sh
npm installnpm test               # run vitestnpm run build          # bundle TS → dist/index.js (esbuild, ~600 KB)npm run build:mcpb     # also pack dist/wireboard-mcp-<version>.mcpb

The .mcpb is a zip of manifest.json, icon.png, and the single bundled dist/index.js. All runtime dependencies are inlined by esbuild.

License

MIT.

Source: README.md at commit 7b39a1f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts