Skip to main content
Connect your AI client directly to LightShip’s hosted MCP endpoint. This is the standard setup for searching and inspecting authorized traces.

​
Create an API key

Sign in to LightShip, open Connect, and create a personal API key. The key begins with lsk_... and is shown only once. Use the MCP URL shown on the same page. It normally ends in /mcp.

​
Codex

Restart Codex after adding the connection, then ask it to search or inspect your traces.

​
Claude Code

Do not commit the API key to a repository or client configuration file.

​
Optional: export larger investigations

The remote endpoint returns bounded search results and trace details. To let an agent write a larger authorized export directly into its workspace, install the local LightShip companion:
Then configure an stdio MCP connection that runs lightship mcp with these environment variables:
The companion adds lightship_export_traces, which writes JSONL under .lightship/exports/ and returns only file paths and counts to the conversation. Keep .lightship/ private. Administrator setup uses the separate /mcp/setup endpoint and an administrator API key. Most users should connect only /mcp. See the MCP API reference for the protocol and complete tool list.