11.0+26.5 MCP Server

The Model Context Protocol (MCP) is an open standard for structured communication between AI clients and external tools or services. QF-Test implements this protocol as an MCP server, making its test automation engine available to any MCP-compatible AI client. Through this integration, AI clients can control browsers and desktop applications, interact with UI elements, and execute QF-Test test procedures using natural language. It is also possible to define additional MCP tools, making QF-Test a universal MCP server for any controllable application.

26.5.1 Set up QF-Test MCP Server

The QF-Test MCP server can be enabled in both interactive and batch mode.

In interactive mode, use the options dialog: navigate to »Artificial Intelligence« - »MCP & Agent Skills«, check »Enable MCP Server«, set the desired port (default: 5543, see "MCP Server Port"), and click »OK«. If QF-Test runs on the same machine as the QF-Test license server, an alternative port to 5543 must be used to avoid a conflict.

In batch mode start QF-Test from the command line with qftest -batch -mcp or -mcp=port to run it headlessly with the MCP server active.

The default MCP endpoint is then available at http://127.0.0.1:5543/mcp; the connection type is streamable HTTP.

To connect Claude Desktop, add the following entry to claude_desktop_config.json. The file can be found via »Edit config« in the section »Developer« in the Claude settings.

{
  "mcpServers": {
    "qftest": {
      "command": "npx",
      "args": ["mcp-remote", "http://localhost:5543/mcp"]
    }
  }
}

To connect Claude Code CLI, run the following command and restart Claude Code:

claude mcp add --transport http qftest http://localhost:5543/mcp

To connect Cursor, add the following entry to mcp.json. The file can be found via "New MCP Server" in the section "Tools & MCPs" in the Cursor settings.

{
  "mcpServers": {
    "qftest": {
      "url": "http://localhost:5543/mcp"
    }
  }
}

To connect AnythingLLM, navigate to »Settings«-»Agent Skills«, click on "Edit" icon next to "MCP Servers" and add the following entry to the mcpServers object:

{
  "mcpServers": {
    "qftest": {
      "type": "streamable",
      "url": "http://localhost:5543/mcp"
    }
  }
}

To connect OpenCode, add the following entry to opencode.json. The file is located at ~/.config/opencode/opencode.json for a global configuration, or place it in the project root directory for a project-specific configuration.

{
  "mcp": {
    "qftest": {
      "type": "remote",
      "url": "http://localhost:5543/mcp"
    }
  }
}

26.5.2 Built-in MCP Tools

The following tools are provided by the QF-Test MCP server out of the box.

26.5.3 Create Custom MCP Tools and Prompts

Any QF-Test procedure can be exposed as an MCP tool by adding doctags to its comment. The test suite file containing the procedure must be listed in the »MCP Suites« option found in the options dialog: navigate to »Artificial Intelligence« - »Agent Skills«.

The file qfs-ai.qft is included by default to provide the built-in MCP tools.

To create custom MCP tools suites, add @mcp/tool to the procedure comment to mark it as an MCP tool. MCP prompts can also be created by adding @mcp/prompt to the procedure comment. The tool or prompt name is derived automatically from the procedure name by lowercasing it and replacing spaces and special characters with underscores. Use @mcp/name followed by the desired name to override the automatically generated name.

The tool or prompt description is derived from procedure description created by available doctags. Use @param paramName description to document each parameter. Start the description with the keyword (Required) to mark a parameter as required. Use @return description to describe the return value. Even for purely action-based procedures, it is recommended to return a value describing the execution performed. Use @mcp/timeout millis to set a custom execution timeout in milliseconds. Add @mcp/exposedByDefault false to define a tool or prompt that is not active unless explicitly enabled via the AI security options.

Packages annotated with @mcp/name are prefixed to the tool or prompt name. To expose all procedures in a package as tools or prompts at once, annotate the package comment with @mcp/tools or @mcp/prompts accordingly. Nested packages are prefixed automatically to its tools and prompts. Annotate nested package with @mcp/name to override its prefix in tool or prompt name.

Example procedure comment:

My custom search tool

@param   query         Required. The search term to look up.
@param   maxResults    Maximum number of results to return.
@return  A list of matching product names.

@mcp/tool
@mcp/name search_product

26.5.4 Security considerations

26.5.4.1 Disclaimer

NoteProcedures called via MCP run with your system user's full permissions. They could modify, delete, or access any files your user account can access. Review and test all procedures before marking them as MCP prompt or tool.

26.5.4.2 Security best practices

Keep these practices in mind when writing procedures called via MCP:

• Validate and sanitize parameter input: never trust input data without checking
• Block path traversal: check for .. in file paths, and use absolute paths where possible