Connect your external AI

Two choices to get right

Open MCP in Peaklab and wait for your personal connection details to load. Every client needs the same two things: the server address and your key.

First, the connection type. Peaklab runs on the internet, so always choose the remote or streamable HTTP option. Choosing STDIO, or filling in a command field, tells the client to start a program on your own computer: it cannot reach Peaklab, and you will see the connection listed as active with no tools available.

Second, how the key travels. Where the client lets you set a request header, send the key as a header, because an address is easier to leak through logs, history and screenshots. Where there is no header field, the key goes inside the address instead. The MCP page offers a copy button for each form.

Claude

1. Copy your MCP URL in Peaklab.
2. In Claude, open Settings and then Connectors.
3. Choose the option to add a custom connector.
4. Name it Peaklab, paste the URL and confirm.
5. Enable the connector in a new conversation and ask about your recent training.

ChatGPT

1. In ChatGPT, open Settings, then Security and login, and turn on developer mode. Accept the warning about third-party connectors.
2. Open the plugins or connectors page and choose the option to add one.
3. Set the type to streamable HTTP rather than STDIO. This is the most common mistake: STDIO expects a program running on your own computer, so the URL is ignored and no tools appear.
4. Paste the plain server address into the URL field.
5. Under headers, add Authorization with the value Bearer followed by your key.
6. Create the connection, review the tools ChatGPT lists, then enable Peaklab in a new conversation.

Codex

1. Codex uses its own configuration file at ~/.codex/config.toml, written in TOML, so a JSON configuration will not work.
2. Make your key available as an environment variable in your shell, and also to the desktop application, which does not read your shell profile.
3. Add the server with the Codex command line, choosing the remote server option and pointing it at the bearer token variable.
4. List the configured servers to confirm Peaklab appears as a remote server with bearer token authentication.
5. Restart Codex so it reads the new configuration.

Cursor and other editors

1. Use Copy Cursor config in Peaklab. It sends your key as an Authorization header.
2. Open the MCP configuration file for all projects at ~/.cursor/mcp.json, or for a single project at .cursor/mcp.json.
3. Paste the entry, merging it into an existing server block if one is present.
4. Save the file and confirm the server appears with its tools in the client's MCP settings.

Keep the URL private

Your personal URL includes a credential. Do not include it in screenshots, public documentation, shared chats or bug reports. The examples in these Docs intentionally do not contain a usable key.

Menus and plan requirements in external clients change often. If a label does not match, follow the equivalent control in your installed version.