Skip to main content
Lightsage MCP gives AI agents direct access to the Lightsage public API through the Model Context Protocol. Use it when you want an agent to list prompts, inspect API Performance configuration, create eval runs, retrieve results, or manage Lightsage resources without shelling out to the Lightsage CLI.

​
Install by client

Choose the client you want to configure. Each guide connects the client to https://mcp.lightsage.com/mcp. Lightsage MCP supports two authentication methods:
  • OAuth — hosted connector surfaces (ChatGPT, Claude web/Desktop) sign in with your Lightsage account and pick an organization. No API key required.
  • X-Lightsage-Api-Key header — coding agents and CLI-based clients send a Lightsage API key from the dashboard.

ChatGPT

Add Lightsage in developer mode with its public OAuth client.

Claude

Add Lightsage as a custom connector in Claude web or Desktop with OAuth.

Claude Code

Add Lightsage as a remote HTTP MCP server with a custom auth header.

Codex

Configure Lightsage MCP in ~/.codex/config.toml.

Cursor

Add Lightsage MCP to your global or project Cursor MCP config.

Gemini CLI

Add Lightsage MCP to Gemini CLI with a streamable HTTP server.

GitHub Copilot

Configure Lightsage MCP for GitHub Copilot in VS Code or Copilot CLI.

Kilo

Configure Lightsage MCP as a remote server in Kilo.

OpenCode

Configure Lightsage as a remote MCP server in opencode.json.

​
Run the local package

For clients that require a local stdio process, run the published MCP package:

​
Verify the connection

After configuring a client, start with a read-only prompt:
Then try a low-risk API Performance prompt:
If the client cannot list tools, confirm the endpoint is reachable:
OAuth-enabled clients receive a 401 Unauthorized challenge before sign-in. The response must include:

​
Troubleshooting