Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

A Model Context Protocol server for TrackJS error monitoring that allows you to query and analyze your JavaScript errors.

README.md

TrackJS MCP Server

A Model Context Protocol server for TrackJS error monitoring that allows you to query and analyze your JavaScript errors.

Setup

1. Install Dependencies

npm install

2. Get Your TrackJS API Credentials

  1. Log into your TrackJS account at https://my.trackjs.com
  2. Go to AccountAPI Keys (only visible to Account Owners)
  3. Copy both your Customer ID and API Key

3. Configure Environment Variables

Copy the example environment file and add your API key:

cp env.example .env

Then edit .env with your actual TrackJS API key:

# Required: Your TrackJS API key  
TRACKJS_API_KEY=your_actual_api_key_here

# Required: Your TrackJS Customer ID
TRACKJS_CUSTOMER_ID=your_actual_customer_id_here

# Optional: Custom API base URL (defaults to https://api.trackjs.com)
TRACKJS_BASE_URL=https://api.trackjs.com

4. Build the Project

npm run build

5. Run the Server

npm start

Available Tools

This MCP server provides the following tools:

  • get_errors - Retrieve recent errors with optional filtering (application, environment, date range, etc.)
  • get_error_details - Get detailed information about a specific error by ID
  • get_error_messages - Get most common error messages with counts and sorting options

Usage Examples

Once connected via MCP, you can ask questions like:

  • "Show me recent errors from the last 24 hours"
  • "What are the most common error messages?"
  • "Show me errors sorted by user impact"
  • "Get details for error ID abc123"

MCP Client Configuration

Claude Desktop Configuration

To use this server with Claude Desktop, add the following to your Claude Desktop MCP configuration file:

Location: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)

{
  "mcpServers": {
    "trackjs": {
      "command": "node",
      "args": ["/absolute/path/to/trackjs-mcp/dist/index.js"],
      "env": {
        "TRACKJS_API_KEY": "your_trackjs_api_key_here",
        "TRACKJS_BASE_URL": "https://api.trackjs.com/v1"
      }
    }
  }
}

Important: Replace /absolute/path/to/trackjs-mcp/ with the actual path to this project directory.

Alternative: Using .env file

If you prefer to use the .env file approach (recommended), configure like this:

{
  "mcpServers": {
    "trackjs": {
      "command": "node",
      "args": ["/absolute/path/to/trackjs-mcp/dist/index.js"],
      "cwd": "/absolute/path/to/trackjs-mcp"
    }
  }
}

This way, the server will automatically load environment variables from your .env file.

After adding the configuration:

  1. Restart Claude Desktop
  2. The TrackJS tools should be available in your Claude conversations

Development

# Development mode with hot reload
npm run dev

# Build TypeScript
npm run build

# Clean build artifacts  
npm run clean

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Observability servers.