MCP Test MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_URL | No | LLM API endpoint URL (required for execute_prompt_with_llm) | |
| LLM_API_KEY | No | API key for authentication | |
| LLM_MODEL_NAME | No | Model name to use | |
| MCP_TEST_LOG_LEVEL | No | Set logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL) | INFO |
| MCP_TEST_CONNECT_TIMEOUT | No | Connection timeout in seconds | 30.0 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_to_serverA | Connect to an MCP server for testing. Establishes a connection to a target MCP server using the appropriate transport protocol (stdio for file paths, streamable-http for URLs, or explicit stdio via command parameter). Only one connection can be active at a time. |
| disconnectA | Close the current MCP server connection. Safely disconnects from the active MCP server and clears all connection state and statistics. This method is safe to call even if no connection exists. Returns: Dictionary with disconnection details including: - success: Always True - message: Human-readable status message - was_connected: Whether a connection existed before disconnect - metadata: Request timing information and previous connection info |
| get_connection_statusA | Check the current MCP server connection state. Returns detailed information about the active connection including server information, transport type, connection duration, and usage statistics. Returns: Dictionary with connection status including: - success: Always True - connected: Boolean indicating if currently connected - connection: Full ConnectionState if connected, None otherwise - message: Human-readable status message - metadata: Request timing and connection duration info |
| list_toolsA | List all tools available on the connected MCP server. Retrieves comprehensive information about all tools exposed by the target server, including full input schemas to enable accurate tool invocation. Returns: Dictionary with tool listing including: - success: True on successful retrieval - tools: List of tool objects with name, description, and full input_schema - metadata: Total count, server info, timing information Raises: Returns error dict if not connected or retrieval fails |
| call_toolA | Execute a tool on the connected MCP server. Calls a tool by name with the provided arguments and returns the result along with execution timing and metadata. Returns: Dictionary with tool execution results including: - success: True if tool executed successfully - tool_call: Object with tool_name, arguments, result, and execution metadata - metadata: Request timing and server information Raises: Returns error dict for various failure scenarios: - not_connected: No active connection - tool_not_found: Tool doesn't exist on server - invalid_arguments: Arguments don't match tool schema - execution_error: Tool execution failed |
| list_resourcesA | List all resources available on the connected MCP server. Retrieves comprehensive information about all resources exposed by the target server, including URIs, names, descriptions, and MIME types to enable accurate resource access. Returns: Dictionary with resource listing including: - success: True on successful retrieval - resources: List of resource objects with uri, name, description, mimeType - metadata: Total count, server info, timing information Raises: Returns error dict if not connected or retrieval fails |
| read_resourceA | Read a specific resource from the connected MCP server. Reads a resource by URI and returns its content along with metadata. Returns: Dictionary with resource content including: - success: True if resource was read successfully - resource: Object with uri, mimeType, and content - metadata: Content size and request timing Raises: Returns error dict for various failure scenarios: - not_connected: No active connection - resource_not_found: Resource doesn't exist on server - execution_error: Resource read failed |
| list_promptsA | List all prompts available on the connected MCP server. Retrieves comprehensive information about all prompts exposed by the target server, including names, descriptions, and complete argument schemas to enable accurate prompt invocation. Returns: Dictionary with prompt listing including: - success: True on successful retrieval - prompts: List of prompt objects with name, description, and arguments schema - metadata: Total count, server info, timing information Raises: Returns error dict if not connected or retrieval fails |
| get_promptA | Get a rendered prompt from the connected MCP server. Retrieves a prompt by name with the provided arguments and returns the rendered prompt messages. Returns: Dictionary with rendered prompt including: - success: True if prompt was retrieved successfully - prompt: Object with name, description, and rendered messages - metadata: Request timing and server information Raises: Returns error dict for various failure scenarios: - not_connected: No active connection - prompt_not_found: Prompt doesn't exist on server - invalid_arguments: Arguments don't match prompt schema - execution_error: Prompt retrieval failed |
| execute_prompt_with_llmA | Execute a prompt with an LLM and return the response. This tool performs the complete workflow:
Supports two prompt patterns:
|
| health_checkB | Health check endpoint that verifies the server is running. Returns: Dictionary with status and server information |
| pingA | Simple ping tool that responds with 'pong'. Useful for testing basic connectivity and server responsiveness. Returns: The string 'pong' |
| echoA | Echo back a message. |
| addA | Add two numbers together. |
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 14 tools
Each tool has a clear, distinct purpose: connection lifecycle (connect, disconnect, status), introspection (list tools/resources/prompts), execution (call_tool, read_resource, get_prompt), and a few trivial test utilities (ping, echo, add). No two tools appear to do the same thing, and the descriptions reinforce their uniqueness.
The majority of tools follow a verb_noun pattern (e.g., list_tools, read_resource, connect_to_server), but there are exceptions like 'disconnect', 'ping', 'echo', and 'add' which are bare verbs or single nouns. This mix is noticeable, though the exceptions are trivial and arguably acceptable for test utilities.
At 14 tools, the server provides a comprehensive but focused surface for testing MCP interactions. The count includes both essential operations (connect, list, call, read) and a few trivial tools (ping, echo, add) that serve diagnostic purposes. It is not excessive for the stated goal of an MCP test server.
The tool set covers the full lifecycle of interacting with an MCP server: connection management, introspection of all primitives (tools, resources, prompts), execution of each type, and a high-level workflow (execute_prompt_with_llm). Missing operations like resource update/delete are not typically required for a test harness, so the surface is sufficiently complete.