Martin Loop MCP Server

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

    return spawn(plan.command, plan.args, options ?? {});

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(command, args, {

    if (await isFile(path.join(stagingRoot, forbidden))) throw new Error(`Forbidden file included in staging: ${forbidden}`);

    const entries = await readdir(dir);

  const pathKey = Object.keys(process.env).find((key) => key.toLowerCase() === "path");

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 martin-loop -- npx -y @martinloop/mcp

{
  "mcpServers": {
    "martin-loop": {
      "args": [
        "-y",
        "@martinloop/mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.martin-loop]
command = "npx"
args = ["-y", "@martinloop/mcp"]

{
  "mcpServers": {
    "martin-loop": {
      "args": [
        "-y",
        "@martinloop/mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "martin-loop": {
      "args": [
        "-y",
        "@martinloop/mcp"
      ],
      "command": "npx"
    }
  }
}