# How do I connect my agent to the Loadster MCP server?

> Point your AI agent at the Loadster MCP server at api.loadster.com/mcp and connect with OAuth or a token. Setup steps for Claude, ChatGPT, and more.

Source: https://loadster.com/faqs/connect-to-loadster-mcp-server/

Loadster has a built-in [Model Context Protocol](https://modelcontextprotocol.io/) (MCP) server at
`https://api.loadster.com/mcp`. MCP is the open standard that AI agents 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 an MCP Token

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

- **OAuth** — supported clients, including ChatGPT web connections created in Developer Mode and local Codex clients,
  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 agents on the **AI Agents** page in your Loadster settings.
- **MCP 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 → AI Agents → MCP Tokens** and pass in an `Authorization: Bearer`
  header. Copy it when you create it, since it's only shown once.

However an agent 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. ChatGPT web uses a plugin connection and does not read local Codex
configuration, while Codex in the ChatGPT desktop app, the Codex CLI, and the Codex IDE extension share the MCP
configuration on the same Codex host. The [AI agents manual](https://loadster.com/manual/ai-agents/) has current steps for those clients,
along with Claude Code, the Claude desktop app, Cursor, and VS Code.

If your preferred agent isn't documented there and you don't figure it out, please
email [help@loadster.com](mailto: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.