Llmkit MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const child = spawn(cmd, opts.command.slice(1), {

    await fetch(`https://api.telegram.org/bot${TG_TOKEN}/sendMessage`, {

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

          curl -s -X POST "https://api.telegram.org/bot${{ secrets.TELEGRAM_BOT_TOKEN }}/sendMessage" \

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add llmkit -- npx -y @f3d1/llmkit-mcp-server

{
  "mcpServers": {
    "llmkit": {
      "command": "npx",
      "args": [
        "-y",
        "@f3d1/llmkit-mcp-server"
      ]
    }
  }
}

[mcp_servers.llmkit]
command = "npx"
args = ["-y", "@f3d1/llmkit-mcp-server"]

{
  "mcpServers": {
    "llmkit": {
      "command": "npx",
      "args": [
        "-y",
        "@f3d1/llmkit-mcp-server"
      ]
    }
  }
}

{
  "servers": {
    "llmkit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@f3d1/llmkit-mcp-server"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: LLMKIT_API_KEY (LLMKit API key. Optional: local tools work without it), LLMKIT_PROXY_URL (LLMKit proxy URL (defaults to hosted service)).