Model Context Protocol (MCP)

What is the Livestorm MCP?

The Livestorm MCP server is a developer-friendly integration layer that makes your Livestorm data accessible to AI assistants and automated workflows. It exposes the Livestorm Public API V1 as a set of tools covering events, sessions, people and more, that any MCP-compatible client can call.

Available Tools

A set of tools covering events, sessions, people and more.

Installation

Server URL

https://mcp.livestorm.co/mcp

This is a remote MCP server over Streamable HTTP, with OAuth 2.1 and dynamic client registration. Because it is remote and transport-standard, it is client-agnostic: any MCP client that can connect to a remote HTTP server will work. The sections below cover the most common clients, for anything else, see Other clients.

For instructions for specific clients, read on…

Claude

Claude.ai (Team / Enterprise) — Go to the Connectors page, add a custom connector with the server URL above, and complete the OAuth flow.

Claude Desktop (Free / Pro) — Open Settings → Connectors → Add custom connector, paste the server URL, and complete the OAuth flow.

Claude Code — Run:

claude mcp add --transport http Livestorm https://mcp.livestorm.co/mcp

Then run /mcp inside Claude Code and complete the OAuth flow.

ChatGPT

In Settings → Connectors, add a custom connector with the server URL above and complete the OAuth flow.

Cursor

Add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

{
  "mcpServers": {
    "livestorm": {
      "url": "https://mcp.livestorm.co/mcp"
    }
  }
}

Reload Cursor, open Settings → MCP, and complete the OAuth flow when prompted.

GitHub Copilot (VS Code)

Add the server to .vscode/mcp.json in your workspace:

{
  "servers": {
    "livestorm": {
      "type": "http",
      "url": "https://mcp.livestorm.co/mcp"
    }
  }
}

Open the MCP: List Servers command, start the Livestorm server, and complete the OAuth flow. Copilot must be in Agent mode to use MCP tools.

Dust

In your Dust workspace, go to Admin → Tools (MCP), add a new remote MCP server with the server URL above, and complete the OAuth flow. The Livestorm tools then become available to your Dust agents.

Gemini

Remote MCP servers are supported by the Gemini CLI (the consumer Gemini app/web does not currently connect to third-party remote MCP servers). Add the server to ~/.gemini/settings.json:

{
  "mcpServers": {
    "livestorm": {
      "httpUrl": "https://mcp.livestorm.co/mcp"
    }
  }
}

The Gemini CLI supports OAuth discovery for remote servers and will prompt you to authenticate on first use.

Microsoft 365 Copilot

Microsoft 365 Copilot connects to remote MCP servers through Copilot Studio. Open your agent in Copilot Studio, then go to Tools → Add a tool → Model Context Protocol and run the "Add an MCP server" wizard:

• Server URL — https://mcp.livestorm.co/mcp
• Authentication — select OAuth 2.0 → Dynamic discovery. Our server supports OAuth 2.0 dynamic client registration, so Copilot Studio registers itself and discovers the endpoints automatically (no manual client ID/secret needed).

Publish the agent, then complete the OAuth flow when prompted on first use. The Livestorm tools then become available to the agent inside Microsoft 365 Copilot.

Other clients

Hundreds of other tools now support MCP servers. For any client that can only talk to local/stdio servers, or that doesn't yet support remote OAuth, use the mcp-remote bridge, which proxies a local stdio connection to our remote server and handles OAuth in your browser:

{
  "mcpServers": {
    "livestorm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.livestorm.co/mcp"]
    }
  }
}