FAQs

How do I connect my AI assistant to the Loadster MCP server?

Loadster has a built-in Model Context Protocol (MCP) server at https://api.loadster.com/mcp. MCP is the open standard that AI assistants use to call external tools, and Loadster’s server exposes its script editor, scenarios, monitors, and test results.

Your client must support remote MCP servers over Streamable HTTP and authenticate with OAuth or an Authorization: Bearer header. If it does, connecting is mostly a matter of pointing it at that URL.

Connecting with OAuth or a Personal Access Token

There are two ways to authenticate, depending on the assistant:

  • OAuth — supported clients, including the Loadster plugin for ChatGPT and Codex, Claude Code, and Cursor, can send you to Loadster to approve the connection in your browser. There’s no token to copy, and you can see and revoke connected assistants on the API & Agents page in your Loadster settings.
  • Personal access token — clients that don’t use OAuth, along with CI jobs and scripted agents, can authenticate with a token you create in the dashboard under Settings → API & Agents → Personal Access Tokens and pass in an Authorization: Bearer header. Copy it when you create it, since it’s only shown once. The same token also works with the Loadster REST API.

However an assistant connects, it acts as you within the team where you set it up, so treat a token like a password and revoke any you no longer use.

Setup Steps for MCP Clients

The exact steps differ a little by client. In ChatGPT and Codex, the easiest route is the official Loadster plugin, which you install from the plugin directory without touching any configuration. The Codex IDE extension, and Codex setups that use a personal access token, go through Codex’s MCP configuration instead. The MCP manual page has current steps for those clients, along with Claude Code, the Claude desktop app, Cursor, and VS Code. The loadster/loadster-mcp repository on GitHub has the same snippets, plus a Claude Code plugin you can install with /plugin marketplace add loadster/loadster-mcp.

If your preferred assistant isn’t documented there and you don’t figure it out, please email help@loadster.com and we’ll be happy to take a look.

Testing the MCP Connection

Once connected, ask the assistant something simple like “List my Loadster projects” to confirm it can reach your account. An initial unauthenticated 401 in server logs can be normal during OAuth discovery. A 401 shown to the user, or repeated after OAuth completes, usually means the token is missing, mistyped, or revoked, or the OAuth connection was revoked.