Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

TrackJS (BYOK) — connector documentation

  • MCP endpoint: https://byok-trackjs.connectorbay.com/mcp
  • REST API: POST https://byok-trackjs.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-trackjs.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own TrackJS TrackJS API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-trackjs.connectorbay.com/health · Tool schemas: https://byok-trackjs.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-trackjs · agent@connectorbay.com

What TrackJS (BYOK) is for

TrackJS (BYOK) lets an AI assistant read your own TrackJS data through the TrackJS API with a key you supply (TrackJS API key). Read-only: 8 tools (list_errors, errors_by_message, errors_by_url, errors_by_day, errors_by_hour, page_views_by_day, page_views_by_hour, usage_by_hour). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.trackjs.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by TrackJS. TrackJS and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What JavaScript errors did TrackJS record yesterday?"
  • "Which JavaScript errors happen most often in TrackJS?"
  • "Which pages produce the most JavaScript errors?"
  • "How many JavaScript errors per day did we have this month?"
  • "When during the day did JavaScript errors spike in TrackJS?"
  • "How many page views did TrackJS record per day last week?"

What it does

  • list_errors: List individual JavaScript errors, newest first, with message, time, page URL, browser, file and line, status and a link to the TrackJS dashboard. User ids, session ids and custom metadata are not returned.
  • errors_by_message: Count errors grouped by error message, most frequent first, with affected user count, last seen time and status.
  • errors_by_url: Count errors grouped by the page URL where they happened, most frequent first.
  • errors_by_day: Count errors and affected users per day, newest first by default.
  • errors_by_hour: Count errors and affected users per hour, newest first by default.
  • page_views_by_day: Count page views recorded by the TrackJS agent per day, newest first.
  • page_views_by_hour: Count page views recorded by the TrackJS agent per hour, newest first.
  • usage_by_hour: Get account usage per hour: page views, total, processed, ignored and dropped errors, and errors per page view.

BYOK key

You bring your own TrackJS TrackJS API key (https://docs.trackjs.com/data-api/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.trackjs.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the TrackJS API (api.trackjs.com) with a BYOK key; documentation: https://docs.trackjs.com/data-api/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by TrackJS. TrackJS and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your TrackJS account.

Built for: Worldwide. Languages: English.