Page History

Specify the endpoint for the MCP server in the format of http(s)://host[:port]/path. This is required to create a new connection. After the initial connection is created, you can use the connection ID to control which connection you want to work with.

The tool splits the Endpoint into two parts by default:

• Base URL: http(s)://host[:port]
• SSE endpoint: /path

See the note below if your base URL is more than just a hostname and port.

Example:

• Endpoint: http://localhost:8080/sse

Result:

• Base URL: http://localhost:8080
• SSE endpoint: /sse

Note: The tool assumes that your endpoint's base URL is comprised of just a hostname and port and that everything else is the SSE endpoint. If that is not the case in your situation, use the system property described below to properly define the base URL so the endpoint is split correctly.

-J-Dcom.parasoft.soavirt.tool.mcpclient.baseurl=<BASE_URL> 

Specify either true or false to keep connection open or close connection after test execution. The default is false.

The MCP client allows multiple active connections to be used. If the connection ID matches the ID for a connection that is already open, that connection will be reused. If the connection ID matches an ID for a connection that has been closed or has never been used to open a connection previously, a new connection will be created.

If Keep Alive is true, SOAtest will not close the connection at the end of that test’s execution. If Keep Alive is false, SOAtest will close the connection at the end of that test’s execution. Unlike built-in transports, there is no final cleanup of open connections for this custom tool when execution is finished, so you should set Keep Alive to false for the last test of a given connection. If this is not done, the connection will stay open.

For example, in the following scenario, both connections will be kept open after the test run is over:

• Connection A (Keep Alive: true)
• Connection B (Keep Alive: true)
• Connection A (Keep Alive: true)
• Connection B (Keep Alive: true)

To fix this, you would set Keep Alive to false for the last test that uses a particular connection:

• Connection A (Keep Alive: true)
• Connection B (Keep Alive: true)
• Connection A (Keep Alive: false)
• Connection B (Keep Alive: false)

Specify a connection ID if you are testing multiple connections. Any string can be used for connection IDs.

If you specify a connection ID that references an already open connection, as well as an Endpoint, Request Timeout, Bearer Token, Basic Auth Username or Basic Auth Password, the Endpoint, Request Timeout, Bearer Token, Basic Auth Username or Basic Auth Password will be ignored because the connection will already be open.

You do not need to set the connection ID if you are working with a single connection within a test suite, SOAtest will use the default value (<default>) for the connection ID.

However, if you want to open and send/receive messages on multiple connections within the same scenario, you need to specify unique connection IDs for each of them.

The default is <default>.

Specify the OAuth 2.0 access token with which to authenticate to a MCP server that uses OAuth authentication. If no OAuth authentication is needed, leave this field blank. If this field is specified, the Basic Auth Username and Basic Auth Password fields will be ignored.

Specify the username with which to authenticate to a MCP server that uses Basic authentication. If no Basic authentication is needed, leave this field blank. If Bearer Token field is specified, this field will be ignored.

Specify the password with which to authenticate to a MCP server that uses Basic authentication. If no Basic authentication is needed, leave this field blank. If Bearer Token field is specified, this field will be ignored.

The name of the method to be invoked. The following methods are supported:

• tools/list
• tools/call
• resources/list
• resources/read
• prompts/list
• prompts/get

These fields configure arguments that should be sent as part of the request.

You can configure up to ten arguments. Arguments are configured using a name=value format. (The value can be a JSON structure.) For example, message="hello" and entities=[{"name":"John_Smith","entityType":"person","observations":["Speaks fluent Spanish"]}].