Vectr MCP Server

What the code does

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

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.

        subprocess.Popen(

    abs_path = os.path.normpath(os.path.join(root, path))

    cp.spawn(launcher.command, [...launcher.args, 'start', '--path', workspaceRoot, '--port', String(preferredPort)], {

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 vectr -- uvx vectr

{
  "mcpServers": {
    "vectr": {
      "args": [
        "vectr"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.vectr]
command = "uvx"
args = ["vectr"]

{
  "mcpServers": {
    "vectr": {
      "args": [
        "vectr"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "vectr": {
      "args": [
        "vectr"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: VECTR_PORT (Port the local vectr daemon serves MCP on. Start the daemon with `vectr start` before connecting.). The author declared them in the registry entry; get the values from the project itself.