JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 9
  • Score
    100M100P100Q67891F

Model Context Protocol server for Hackle

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@hackle-io/hackle-mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    Hackle MCP Server

    smithery badge

    A Model Context Protocol server for Hackle API providing tools and resources for querying A/B Test data.

    Features

    Tools

    • list_experiments: List experiments(A/B Test) from your workspace

    Installation

    Option 1: Installing via Smithery

    To install hackle-mcp for Claude Desktop automatically via Smithery:

    npx -y @smithery/cli install @hackle-io/hackle-mcp --client claude

    Option 2: Add to claude_desktop_config by hand

    Add this entry to your claude_desktop_config.json:

    • On Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
    • On Windows: %APPDATA%\Claude\claude_desktop_config.json
    • On Linux: ~/.config/Claude/claude_desktop_config.json
    {
      "mcpServers": {
        "hackle-mcp": {
          "command": "npx",
          "args": [
            "-y",
            "@smithery/cli@latest",
            "run",
            "@hackle-io/hackle-mcp",
            "--config",
            "{\"apiKey\":\"YOUR_API_KEY\"}"
          ]
        }
      }
    }

    Restart Claude if running

    Getting Your API Key

    To use the Hackle MCP Server, you will need an API key. To obtain your API key:

    1. Contact the Hackle team directly through Hackle Slack Community
    2. Request an API key for MCP Server access
    3. The Hackle team will provide you with a unique API key

    Important: Never share your API key or commit it to public repositories. Treat your API key as a sensitive credential.