# How to connect your AI to Livebib

Claude, ChatGPT, Gemini, Le Chat, your code editor or an AI you build yourself can work with your Livebib account. You log in, choose what it may do, and can disconnect it at any time.

https://livebib.com/help/connect-your-ai

## What does a connection do?

A connection lets the AI service you already use read and do things in your Livebib account. Depending on what you allow, it can read your broadcasts and splits, compare your races, plan a route and save a planned broadcast for you to check, and follow people.

You need no server, no app and no API key. You approve the connection on a Livebib page, and Livebib checks what it may do on every request.

## Get your connection address

1. Open livebib.com/ai and tap “Log in or create an account”. No account yet? Logging in with your email creates one. There is no password.
2. You land on “Connected AI services”. You also find it under “Settings”.
3. Tap “Copy address”. The address is the same for every AI service.

## Connect in Claude

1. On claude.ai or in the Claude desktop app, open “Customize”, then “Connectors”.
2. Choose “Add custom connector”, name it Livebib and paste the address.
3. If Claude asks how to sign in, choose “Register automatically”. Then add it.
4. Claude opens Livebib. Log in, check the access it asks for and choose “Connect account”.

> On the Free plan you can add one custom connector. On Team and Enterprise an owner adds it under “Organization settings”, then “Connectors”, and members connect it. A connector added on the web also works in the Claude phone app. In Claude Code, run claude mcp add --transport http livebib followed by the address, then type /mcp to log in.

## Connect in ChatGPT

1. In a browser, open chatgpt.com/plugins.
2. Choose the plus button, then “Add custom MCP server”. Name it Livebib and paste the address as the server URL.
3. Under authentication choose OAuth, confirm with “I understand and want to continue” and choose “Create as a plugin”.
4. Install it, log in to Livebib when asked and choose “Connect account”. In a chat, type @ and pick Livebib.

> OpenAI decides which plans can add their own servers, and a workspace admin may have to allow it. It is done on the web, not in the ChatGPT app.

## Connect in Gemini

In the Gemini web app, open “Settings”, then “Connected Apps”, choose “Add a custom app” and paste the address. Gemini opens Livebib for you to log in and approve. Once connected it works in the Gemini phone app too.

For now Google offers custom apps only to people over 18 in the US, with a personal Google account and Gemini in English. From anywhere else, the Gemini CLI connects: add Livebib under mcpServers in its settings.json with the address as httpUrl, then run /mcp auth livebib.

## Connect in Le Chat by Mistral

1. In Le Chat, open “Connectors” in the sidebar.
2. Choose “Add Connector” and the “Custom MCP Connector” tab.
3. Name it livebib, paste the address as the server URL and choose “Connect”.
4. Log in to Livebib and choose “Connect account”.

> Only the account's administrator can add a connector. On a personal plan that is you.

## Connect in Google Antigravity

1. Open the MCP settings. In the Antigravity editor, click “…” at the top of the agent side panel, choose “MCP Servers”, then “Manage MCP Servers” and “View raw config”. In the agy command line, type /mcp.
2. Under mcpServers, add livebib with the address as serverUrl and save. The editor, the Antigravity app and agy share this one file, mcp_config.json in the folder .gemini/config in your home folder.
3. Open “Agent settings” with Cmd and comma on a Mac or Ctrl and comma on Windows and Linux. Go to “Customizations” and choose “Authenticate” next to livebib.
4. Log in to Livebib in your browser and choose “Connect account”. Copy the code your browser then shows, paste it into the settings and choose “Submit”.

> Write serverUrl, not httpUrl as in the Gemini CLI, because Antigravity does not read httpUrl. An older Antigravity kept the file in .gemini/antigravity instead, and the menu opens the right one either way. To use a personal token instead of logging in, add headers with Authorization set to Bearer followed by the token.

## Connect in a code editor

Most code editors take the address as a remote MCP server and open Livebib in your browser for you to log in and approve. Where to add it:

- Cursor: add Livebib to mcp.json with the address as url.
- VS Code: run “MCP: Add Server” from the command palette, choose HTTP and paste the address.
- Windsurf, now Devin Desktop: in the Cascade panel choose “...” and “Open MCP config file”, then add Livebib with the address as serverUrl.
- Zed: open “Settings”, then “AI”, “MCP Servers”, “Add Server” and “Add Remote Server”.
- JetBrains: in Junie, add Livebib to mcp.json with the address as url and choose “Authorize”. AI Assistant takes the address under “Model Context Protocol (MCP)” in its settings, but JetBrains does not say yet how it logs in.
- Visual Studio: in Agent mode, choose “Tools”, then “+” and “Add custom MCP server”.
- Kiro: add Livebib to mcp.json in .kiro/settings with the address as url. In Amazon Q Developer, choose the tools icon in the chat, then “+” and http.
- Cline: open “MCP Servers”, the “Remote Servers” tab, paste the address and choose Streamable HTTP.
- Continue and Augment Code: these take a personal token in their headers instead of a login.

> Menus are quoted in English, as each company names them, and they change often. The full list, with what to paste for each one, is on livebib.com/ai/docs.

## Connect a coding agent in the terminal

Claude Code and the Gemini CLI are above. The others take the address with one command or one line in their settings, then open Livebib in your browser for you to log in.

- OpenAI Codex: add a section mcp_servers.livebib with the address as url to config.toml in the .codex folder, then run codex mcp login livebib. The Codex app and editor extension read the same file.
- GitHub Copilot CLI: run copilot mcp add --transport http livebib followed by the address, then /mcp auth.
- Kiro CLI, which replaced the Amazon Q Developer CLI: the same mcp.json as Kiro, then /mcp auth.
- Mistral Vibe CLI: run vibe mcp add livebib --url followed by the address.
- Goose: choose “Add custom extension”, then “Remote Extension (Streamable HTTP)”, and paste the address as the endpoint URL.
- opencode and Amp: add Livebib as a remote server with the address, then run opencode mcp auth livebib, or start Amp.
- Warp: its login cannot return to Livebib yet. Add Livebib under “Settings”, then “Agents” and “MCP servers”, with a personal token in its headers.
- GitHub Copilot cloud agent: it takes only a personal token, in a repository secret whose name starts with COPILOT_MCP_. Give that token read access only, since the agent does not ask before it acts.

## Connect in other AI apps

- Perplexity: open “Plugins” in the sidebar, or “Customize” and “Connectors”. Choose “Add custom”, “Add MCP connector” and “Remote”, paste the address, choose Streamable HTTP and log in from the connector's card.
- Grok: open grok.com/connectors, choose “New Connector” and “Custom”, and paste the address. xAI does not say yet how it logs in.
- Microsoft Copilot Studio: choose “Tools”, “Add a tool”, “New tool” and “Model Context Protocol”, paste the address and choose an API key in the header Authorization. The key is Bearer followed by a personal token.
- Raycast: run “Install MCP Server”, choose HTTP, paste the address, choose the OAuth type Dynamic and then “Sign In”. If the login does not finish, use a personal token under “HTTP Headers”.
- LM Studio: in the “Program” tab choose “Install”, then “Edit mcp.json”, and add Livebib with the address as url.
- Jan: open “Settings”, then “MCP Servers” and “Add MCP Server”, choose HTTP, paste the address and choose “Sign in”.
- Msty Studio: choose “Add New Tool” and HTTP, paste the address and put a personal token under “Headers”.
- Open WebUI and LibreChat: an administrator adds the address as an MCP server with Streamable HTTP. The login works only when the installation runs on https or on your own computer. Otherwise use a personal token.

## AI services that cannot connect yet

Microsoft 365 Copilot needs a kind of login Livebib does not offer, and it takes no personal token. Does your organisation want Livebib in Microsoft 365 Copilot? Write to hello@livebib.com and we will set it up with you. Ollama has no way to connect to a server like Livebib.

The Microsoft Copilot app, Meta AI, DeepSeek, Siri, Poe and Character.ai have no way to add a server of your own yet. When one of them does, it goes into this guide.

## Your own AI engine or script

An agent you build with the Anthropic API, the OpenAI API or an MCP library sends a fixed key instead of logging in. For that, make a personal token.

1. On “Connected AI services”, go to “Your own AI engine or script”.
2. Name the token, tick what it may do and choose “Create token”.
3. Copy the token right away. Livebib shows it only once.
4. Send it with every request to the address, in the header Authorization: Bearer followed by the token. In the Anthropic API it goes in authorization_token, and in the OpenAI API in headers.

> Anyone with the token can act as you, with the access you chose. Never paste it into a chat. If it leaks, disconnect it and make a new one.

## Disconnect

On “Connected AI services”, choose “Disconnect” next to a connection or a token, or “Disconnect all”. It stops working on its next request. Each connection also shows the date it is valid until. What the AI service has already saved stays with that service.

## Can it read my heart rate?

Only if you choose to. A new connection never includes heart rate, and no AI service can ask for it. On “Connected AI services”, choose “Share my heart rate” on the one connection you want. It can then read your own heart rate on your own runs, for as long as you have agreed to heart rate in Livebib. Choose “Stop sharing heart rate” to end it.

## What is shared, and what is not

Exact GPS tracks and private messages are never shared through a connection, and heart rate only as described above. What your AI reads goes to that AI service under its own terms. Livebib runs in the EU, but that does not mean the data stays in the EU at the AI service.

