TrackJS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRACKJS_API_KEY | Yes | Your TrackJS API key | |
| TRACKJS_BASE_URL | No | Custom API base URL (defaults to https://api.trackjs.com) | https://api.trackjs.com |
| TRACKJS_CUSTOMER_ID | Yes | Your TrackJS Customer ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_errorsC | Retrieve errors from TrackJS with optional filtering |
| get_error_detailsB | Get detailed information about a specific error |
| get_error_messagesC | Get most common error messages |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_errors lists errors with filtering, get_error_details retrieves specifics for a single error, and get_error_messages aggregates common messages. There is no overlap or ambiguity between them.
All tools follow the same verb_noun pattern (get_errors, get_error_details, get_error_messages) using snake_case consistently. The naming convention is uniform and predictable.
With only 3 tools, the set is well-scoped for a focused error-monitoring server. Each tool serves a necessary function and none feel redundant or excessive.
The server covers the core read-only workflow: listing/filtering errors, viewing details, and aggregating messages. It lacks write/update operations, but that appears outside its intended scope as a retrieval-focused tool.