mgx-thinking-log-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MGX_TOKEN | No | Auth token (appended as ?token= to skip Bearer auth) | |
| MGX_BASE_URL | No | Base URL for the MGX API | http://test-tool.deepwisdomai.com |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_thinking_logsA | Fetch MGX thinking logs for a given chat. Returns the log content as text, suitable for agent analysis. |
| download_thinking_logsA | Download MGX thinking logs to a local file. Useful for saving large log files for later analysis. |
| get_mgx_envA | Fetch the mgxenv.json configuration for a specific MGX chat version. Returns environment config as JSON. |
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 targets a distinct operation: fetching log content as text, downloading logs to a file, and retrieving environment config. The difference between get and download is clear—one returns content for analysis, the other persists to disk.
All tool names follow a consistent verb_noun snake_case pattern (get_, download_). The nouns are descriptive and aligned with the tool's function, with no mixed naming conventions.
Three tools is a well-scoped count for a focused logging/configuration server. Each tool serves a distinct purpose and none are redundant or bloat.
Core retrieval operations are covered: getting logs, downloading logs, and fetching environment config. A minor gap is the lack of listing or searching available logs, but the tool set likely expects chat IDs as inputs, making the surface adequate.