mcp

Clarity MCP Bootleg Market turns browser traffic captured in HAR files into actionable MCP tools that an AI agent can call. The server ingests HAR-derived endpoints, builds a catalog of tools, and exposes them to MCP clients (like Claude). Clients connect via the standard MCP protocol, request the list of available tools, and then issue tool calls that the server forwards to the Clarity backend, which executes the underlying web API requests and returns structured results ready for the AI to consume.

To use it, install and run the MCP server, then connect your MCP client and use ListTools to inspect what tools are available. When you call a tool, the server transforms the call, forwards it to the backend, and returns the API response in MCP-friendly format. Tools correspond to individual endpoints captured from HAR files and are designed to abstract away raw HTTP details while providing useful, real-time data to your AI agent.

Prerequisites:

• Node.js and npm installed on your machine
• Access to the internet to fetch the MCP package
• Optional: a Clarity API key if you plan to forward requests to the Clarity backend

Step-by-step:

1. Install the MCP package globally (or use npx): npm install -g @lekt9/clarity-mcp

2. Set environment variables (example): export CLARITY_API_KEY=your_api_key export CLARITY_MCP_ID=your_mcp_id # optional if you have multiple MCPs export NEXTJS_APP_URL=https://clarity.org/ # optional default

3. Run the server (the CLI provided by the package): clarity-mcp

4. Verify the server is running by requesting the tool list through your MCP client or by checking logs.

Note: The server relies on a valid Clarity backend API key and accessible endpoints to fetch and execute tools.

Environment variables:

• CLARITY_API_KEY: Required for authenticated requests to the Clarity backend
• CLARITY_MCP_ID: Optional if you manage multiple MCPs
• NEXTJS_APP_URL: URL of the Clarity backend (defaults to https://clarity.org/)

Common issues:

• If tools fail to load, ensure the API key is valid and that the backend URL is reachable.
• Tool execution depends on Clarity backend availability; the MCP server does not cache tool definitions or results.
• When sharing HAR-derived tools, handle HAR contents securely as they may contain sensitive data.