ghostinspector-mcp-server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ghostinspector-mcp-serverList all my tests"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ghost Inspector MCP Server
An MCP (Model Context Protocol) server for interacting with Ghost Inspector, an automated browser testing platform.
Features
This MCP server provides tools to:
Hierarchy & Modules: View complete folder/suite structure, list reusable modules, and analyze module usage
Tests: List, view, execute, create, duplicate, and manage test results
Suites: List, view, execute suites, import tests, and manage suite results
Folders: Browse folder structure and list suites within folders
Organizations: Monitor currently running tests
Related MCP server: Testomat.io MCP Server
Installation
Using pip
pip install -e /path/to/ghostinspector-mcp-serverUsing uv (recommended)
uv pip install -e /path/to/ghostinspector-mcp-serverConfiguration
API Key
Set your Ghost Inspector API key as an environment variable:
export GHOST_INSPECTOR_API_KEY=your_api_key_hereYou can find your API key at: https://app.ghostinspector.com/account
Claude Code Configuration
Add the server to your Claude Code MCP settings. Edit your ~/.claude/claude_desktop_config.json (or the appropriate config file):
{
"mcpServers": {
"ghostinspector": {
"command": "ghostinspector-mcp",
"env": {
"GHOST_INSPECTOR_API_KEY": "your_api_key_here"
}
}
}
}Or if using uv:
{
"mcpServers": {
"ghostinspector": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ghostinspector-mcp-server", "ghostinspector-mcp"],
"env": {
"GHOST_INSPECTOR_API_KEY": "your_api_key_here"
}
}
}
}Available Tools
Hierarchy & Module Tools
Tool | Description |
| Get complete folder/suite structure in a single call |
| List all reusable modules (tests with |
| Find all tests that import a specific module |
Test Tools
Tool | Description |
| List all tests in your account (includes |
| Get detailed information about a specific test |
| Execute a test with optional parameters (browser, region, viewport, start URL) |
| Create a copy of an existing test |
| Run a test from JSON definition without saving it permanently |
| List execution history for a test |
| Get detailed result information |
| Cancel a running test |
Suite Tools
Tool | Description |
| List all test suites (includes resolved folder names) |
| Get suite details |
| Execute all tests in a suite |
| Create a new test in a suite from JSON definition |
| List tests within a suite (includes |
| List execution history for a suite |
| Get detailed suite result |
| List individual test results from a suite run |
| Cancel a running suite |
Folder Tools
Tool | Description |
| List all folders |
| Get folder details |
| List suites in a folder |
Organization Tools
Tool | Description |
| Get currently running tests for an organization |
Usage Examples
Once configured, you can use natural language to interact with Ghost Inspector:
"List all my Ghost Inspector tests"
"Run the test with ID abc123"
"Show me the results for suite xyz789"
"What tests are currently running?"
"Execute the login test suite on Firefox"
"Create a test that clicks the login button and verifies the dashboard loads"
"Show me the folder and suite hierarchy"
"List all reusable modules"
"What tests use the login module?"
Understanding Modules
Ghost Inspector supports reusable test modules - tests that are designed to be imported into other tests rather than run independently. Common examples include login flows, navigation sequences, and setup/teardown procedures.
Identifying Modules
Tests marked with importOnly=true are modules. They:
Won't execute when running a suite (they're skipped)
Are meant to be imported into other tests using the "Import steps from test" step
Allow you to maintain common flows in one place
Module Tools
Tool | Use Case |
| See all reusable modules grouped by suite |
| Impact analysis before modifying a module |
| Check |
Creating Tests
You can create tests programmatically using either import_test (saves permanently) or execute_on_demand_test (runs without saving).
Test Step Format
Steps are defined as a JSON array. Each step has:
command: The action to performtarget: CSS selector or element identifiervalue: (optional) Value for the action
Available Commands
Command | Description | Example |
| Click an element |
|
| Type text into an input |
|
| Navigate to a URL |
|
| Verify text exists |
|
| Verify element exists |
|
| Verify element is visible |
|
| Extract text to a variable |
|
| Execute JavaScript |
|
| Wait for milliseconds |
|
| Take a screenshot |
|
| Hover over element |
|
| Press keyboard key |
|
Example: Create a Login Test
Create a test in suite abc123 called "Login Test" that:
1. Goes to https://example.com/login
2. Types "user@example.com" into #email
3. Types "password123" into #password
4. Clicks the .login-button
5. Verifies "Dashboard" appears on the pageDevelopment
Setup
# Clone the repository
cd ghostinspector-mcp-server
# Install dependencies
uv pip install -e ".[dev]"Running Tests
pytestCode Formatting
black src/
ruff check src/License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tempestim/ghostinspector-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server