Schema | testing-mcp

testing-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TESTING_MCP`	No	When set to true, enables the WebSocket bridge to the MCP server. Leave unset to disable.
`TESTING_MCP_PORT`	No	Overrides the WebSocket port for test clients.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}
`logging`	{}

Functions exposed to the LLM to take actions

Name	Description
get_current_test_stateA	Get the current state of a connected test, including DOM, snapshot, console logs, and available context APIs. The response includes 'availableContext' field which lists all APIs/variables that can be used in execute_test_step.
finalize_testB	Finalize the test by removing connect() call and optionally cleaning up markers
list_active_testsA	List all currently connected test processes
get_generated_codeB	Get all generated code blocks from a test file
execute_test_stepA	Execute code directly in the connected test client and get back the updated DOM state and console logs. IMPORTANT: Before using this tool, call get_current_test_state first to check the 'availableContext' field, which lists all available APIs/variables you can use in your code.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcpland/testing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server