Exeris AI Bridge MCP Server

What the code does

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

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  const child = spawn(spec.command, [...spec.args], { stdio: ["pipe", "pipe", "inherit"] });

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(spec.command, [...spec.args], { stdio: ["pipe", "pipe", "inherit"] });

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 ai-bridge -- npx -y @exeris/ai-bridge

{
  "mcpServers": {
    "ai-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@exeris/ai-bridge"
      ]
    }
  }
}

[mcp_servers.ai-bridge]
command = "npx"
args = ["-y", "@exeris/ai-bridge"]

{
  "mcpServers": {
    "ai-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@exeris/ai-bridge"
      ]
    }
  }
}

{
  "servers": {
    "ai-bridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@exeris/ai-bridge"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: EXERIS_PROJECT_ROOT (Root of your own project, for build-* and caps-*. Defaults to the nearest pom.xml at or above the working directory), EXERIS_DOCS_ROOT (An exeris-docs checkout. Without one, docs-* answers from the registry snapshot bundled in the package).