Skip to main content
LightShip exposes a hosted MCP endpoint for bounded trace investigation. An optional local companion adds workspace exports for larger analyses. Both use the caller’s personal API key and the same server-side access policy.

​
Hosted MCP

Connect an MCP client to the /mcp endpoint shown on the LightShip Connect page. For example:
The hosted connection lets the authenticated user inspect filter capabilities, search traces, retrieve one authorized trace, and manage their own API keys.

​
Local companion

Run lightship mcp over stdio when an investigation needs to write a larger authorized export directly into the agent’s workspace:
The companion provides the hosted trace tools plus lightship_export_traces. It requires the lightship binary and these environment variables: See MCP clients for installation and client-specific setup.

​
Setup MCP

Setup is an optional second connection for administrators only:
This endpoint requires the admin role. Its tools connect trace data, define roles, manage users, and review source optimizations. It contains no trace-query tools. Setup accepts MCP initialize, ping, tools/list, and tools/call. Authenticate with an admin’s personal API key.

​
Context limits

lightship_search_traces defaults to 10 summaries and accepts at most 20. Hosted trace-tool results larger than 32 KiB return an error. Use the local companion’s export tool for larger investigations. For the underlying row API used by exports, see Query Traces.