Tedix MCP Server

What the code does

We read the source, 3 h 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.

            `rm -f ${quote(tokenPath)}; rm -rf ${quote(stage)}`,

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 [, namespace, tool] = PORTABLE_CALLABLE.exec(input.callable)!;

            const requested = Bun.file(path.join(assets, url.pathname));

                                Select <strong>+ Add</strong>, then{" "}

export const WORKSTATION_GIT_CREDENTIALS_PATH = `${WORKSTATION_HOME}/.git-credentials`;

            const res = await fetch(`https://api.telegram.org/bot${token}/getMe`);

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 7 min ago.

claude mcp add tedix --transport http https://connect.mcp.tedix.dev/mcp

https://connect.mcp.tedix.dev/mcp

[mcp_servers.tedix]
url = "https://connect.mcp.tedix.dev/mcp"

{
  "mcpServers": {
    "tedix": {
      "url": "https://connect.mcp.tedix.dev/mcp"
    }
  }
}

{
  "servers": {
    "tedix": {
      "type": "http",
      "url": "https://connect.mcp.tedix.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints