Connecting a client¶

The Suitest MCP server is hosted by Suitest. To use it you only need to point your MCP client at the right address and give it a token.

What you need¶

Three values are all it takes:

Value	Where it comes from
Address	`https://the.suite.st/api/public/v4/mcp`
Transport	`http`
Authorization header	Built from your Suitest token, see below

Step 1: create a token¶

Open your account preferences and create a Personal or Service token. Suitest shows the token password only once, so copy it before you close the dialog.

Pick the token type to match the job:

A Personal token acts as you. This is the usual choice when you work with an assistant yourself.
A Service token is not tied to a person. Use it for a shared or automated setup.

Both token types can call every tool. Each sees the same data: everything in the organization that owns the token.

Step 2: build the authorization header¶

The server uses HTTP Basic authentication, the same as the Network API. Join your token ID and token password with a colon, then encode the result as base64.

On macOS or Linux:

printf '%s' 'yourTokenID:yourTokenPassword' | base64

On Windows, in PowerShell:

[Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes('yourTokenID:yourTokenPassword'))

The header value is the word Basic, a space, and the encoded string.

Keep the header secret

The encoded string is not encrypted. Anyone who reads it can recover your token password and reach your Suitest organization. Treat the client configuration file as a secret, and keep it out of version control.

Step 3: add the server to your client¶

Most MCP clients read a JSON configuration file. The entry looks like this:

{
    "mcpServers": {
        "suitest": {
            "type": "http",
            "url": "https://the.suite.st/api/public/v4/mcp",
            "headers": {
                "Authorization": "Basic eW91clRva2VuSUQ6eW91clRva2VuUGFzc3dvcmQ="
            }
        }
    }
}

Replace the encoded string with the one you built in step 2.

Claude Code¶

Run this command, either in your project or with --scope user to make the server available everywhere:

claude mcp add --transport http suitest https://the.suite.st/api/public/v4/mcp \
    --header "Authorization: Basic eW91clRva2VuSUQ6eW91clRva2VuUGFzc3dvcmQ="

Check that it worked with claude mcp list. You can also write the JSON entry above into a .mcp.json file in your project root. Claude Code picks it up the next time it starts.

Other clients¶

Cursor, Visual Studio Code and other MCP clients use the same three values. Look for a remote or HTTP MCP server in the client settings, then supply the address and the authorization header. The key names differ between clients, but the values do not.

Step 4: try it out¶

Ask your assistant something simple that only reads data, for example:

List the devices in my Suitest organization.

The assistant should call the device_list tool and come back with your devices. If it does, you are set up.

To get to know the other tools, try these questions in order. Each one builds on the answer before it:

Ask	Tools the assistant calls
Which apps and versions do I have?	`apps_list`
List the configurations of my app, and show me the first one in full.	`app_configs_list`, `app_config_get`
List the test packs of my app, and show me the details of one.	`test_packs_list`, `test_pack_get`
Show the latest results of that test pack.	`test_pack_executions_list`, `test_pack_execution_iterations`, `test_pack_execution_iteration`
Open the result of the first failing test.	`test_run_device_result`

See the Tools reference for the inputs and outputs of every tool.

If it does not work¶

What you see	What to check
The client reports 401 or unauthorized	The header is wrong. Rebuild it, and make sure you encoded `tokenID:tokenPassword` with a colon and no trailing newline.
The client reports 403 or forbidden	The token is valid but lacks access. Check that the token belongs to the organization you expect.
The server does not appear at all	The client did not load the configuration. Restart it, then confirm the file is the one that client reads.
A tool reports that an app or device was not found	The token is scoped to another organization. Create a token in the right one.

If calls reach Suitest but fail on the network, check whether your organization uses IP whitelisting.

Previous:
Overview Next:
Tools reference