test-intel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port for the HTTP transport when enabled | 3000 |
| TRANSPORT | No | The transport mode, e.g., 'http' or 'stdio' | stdio |
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 |
|---|---|
| analyze_test_coverageA | Parse a coverage report (lcov, istanbul JSON, or cobertura XML) and return uncovered files, functions, lines, and branch gaps. |
| find_untested_functionsA | Scan source files for function/method declarations and identify those with no corresponding test file. |
| get_function_complexityA | Analyze a file's functions for cyclomatic complexity to prioritize which functions need tests most urgently. |
| suggest_test_casesA | Analyze a specific function and generate structured test case suggestions based on its logic, branches, and type signatures. |
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 4 tools
Each tool has a distinct focus: generating test cases, parsing coverage reports, finding untested functions, and analyzing complexity. However, find_untested_functions and get_function_complexity both aim at identifying functions that need testing, which could cause some initial confusion.
All tool names follow a consistent snake_case verb_noun pattern, e.g., suggest_test_cases, analyze_test_coverage, find_untested_functions, get_function_complexity. This makes the toolset predictable and easy for an agent to navigate.
Four tools is well-scoped for a testing intelligence server, with each tool serving a clear and non-redundant purpose. There is no bloat, and the count feels sufficient for the stated domain.
The set covers a natural workflow of testing intelligence: generating tests, assessing coverage, identifying untested functions, and prioritizing via complexity. This is a solid read-only surface, though additional tools like listing existing test files or summarizing coverage trends could round it out further.