mcp s

MCP server from fillegar/mcp-servers

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio fillegar-mcp-servers node path/to/server.js \
  --env PORT="56874 (open port required for Tosca/NeoLoad integration)" \
  --env QTEST_TOKEN="<your-qTest-API-token> (for qTest MCP integration)"

How to use

This MCP server provides ready-to-use configurations to connect Tricentis Tosca Cloud, qTest, and NeoLoad with AI-powered IDEs such as VS Code, Cursor, and Visual Studio. The server acts as a bridge, translating IDE prompts into actions against your Tricentis tenants and returning results like test cases, defects, and NeoLoad scenarios. Use the included MCP JSON files to define which tool you’re connecting, then load the corresponding file into your IDE as described in the repository's setup guide. Once running, you can trigger prompts such as listing Tosca test cases, fetching defects from qTest, or showing NeoLoad scenarios, and receive AI-assisted responses in your IDE.

How to install

Prerequisites:

Node.js (latest LTS) installed
Access to your Tricentis tenant (Tosca Cloud, qTest, or NeoLoad)
For qTest: API Token with MCP permissions
Ensure port 56874 is available

Installation steps:

Install Node.js from https://nodejs.org
Clone this MCP server repository or create your mcp.json files in your project

Install dependencies (if applicable) and run the Node server:

# example if there is a package.json at project root
npm install
npm start

Verify the server is listening on port 56874 (or the port you configured)
In your IDE, place the appropriate MCP JSON file (e.g., tosca.vscode.mcp.json, qtest.cursor.mcp.json, or neoload.vscode.mcp.json) in your workspace root and load it as described in the IDE setup section. You can test connectivity with prompts like “List all Tosca test cases” or “Fetch defects from qTest.”

tips:

You can test commands manually using: npx mcp-remote@latest (as suggested in troubleshooting)
If you change the port, update the PORT environment variable accordingly
Keep your qTest token secure and only provide it in the MCP file or secure env vars

Additional notes

Tips and common issues:

Ensure your Tricentis tenant URL is correct (e.g., yourtenant.my.tricentis.com).
Open port 56874 to allow IDEs to connect.
For qTest, ensure the API token has MCP permissions.
If you encounter connectivity issues, test with npx mcp-remote@latest to validate commands.
The MCP JSON files are tool-specific; place the correct file in your workspace root or IDE settings directory as shown in the README.
When sharing configurations, avoid exposing tokens in public repositories; use environment variables or secure secret management when possible.