Proa documentation MCP Server

What the code does

We read the source, 1 d ago · tools taken from the live server · 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(command, args, { cwd, env, stdio: ['pipe', 'pipe', 'pipe'], windowsHide: true });

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, { cwd, env, stdio: ['pipe', 'pipe', 'pipe'], windowsHide: true });

  const snapshotPath = path.join(repoRoot, snapshotRelativePath);

RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --default-toolchain stable

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.

    return subprocess.run(

      - "/var/run/docker.sock:/var/run/docker.sock:ro"

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

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

claude mcp add docs --transport http https://proa.so/mcp

https://proa.so/mcp

[mcp_servers.docs]
url = "https://proa.so/mcp"

{
  "mcpServers": {
    "docs": {
      "url": "https://proa.so/mcp"
    }
  }
}

{
  "servers": {
    "docs": {
      "type": "http",
      "url": "https://proa.so/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints