driftnet MCP Server

What the code does

We read the source, 1 h ago · rules 995398eba69f

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 p = spawn(cmd, args, { stdio: ["ignore", "pipe", "pipe"] });

    fetch(`https://api.telegram.org/bot${token}/${method}`, {

    $("add-btn").innerHTML = ic("plus"); $("add-btn").title = $("add-btn").ariaLabel = `${T().addTitle} (a)`;

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.

        `EXISTS (SELECT 1 FROM shares s WHERE s.item_id = items.id AND ${like("s.note")})`,

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 driftnet -- npx -y driftnet

{
  "mcpServers": {
    "driftnet": {
      "command": "npx",
      "args": [
        "-y",
        "driftnet"
      ]
    }
  }
}

[mcp_servers.driftnet]
command = "npx"
args = ["-y", "driftnet"]

{
  "mcpServers": {
    "driftnet": {
      "command": "npx",
      "args": [
        "-y",
        "driftnet"
      ]
    }
  }
}

{
  "servers": {
    "driftnet": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "driftnet"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: DRIFTNET_HOME (Where settings and the catalogue live (default ~/.driftnet)), DRIFTNET_LLM_PROVIDER (anthropic, openai, gemini, bedrock, vertex, claude-cli or gemini-cli; empty for no summaries), DRIFTNET_LLM_MODEL (Model name for that provider), DRIFTNET_LLM_API_KEY (API key for that provider (gemini also reads GEMINI_API_KEY; for vertex it may be a raw access token)), DRIFTNET_LLM_BASE_URL (OpenAI-compatible endpoint for the openai provider (Ollama, OpenRouter, Gemini…)), DRIFTNET_LLM_REGION (Region for the bedrock provider (or AWS_REGION) and the vertex provider (default us-central1)), AWS_ACCESS_KEY_ID (bedrock provider: AWS access key ID (with AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN for temporary credentials)), AWS_SECRET_ACCESS_KEY (bedrock provider: AWS secret access key), AWS_BEARER_TOKEN_BEDROCK (bedrock provider: a Bedrock API key, used instead of the AWS keys), GOOGLE_APPLICATION_CREDENTIALS (vertex provider: path to a service-account JSON key file (or DRIFTNET_VERTEX_CREDENTIALS)), GOOGLE_CLOUD_PROJECT (vertex provider: Google Cloud project id (optional when the key file names one)), DRIFTNET_JUDGE (Who files each link before the model: jev, rules (free, no model), llm, heuristic, off, or a plugin's judge name), DRIFTNET_JUDGE_RULES (Path to a rules file for the rules judge, one 'pattern -> folder' per line), DRIFTNET_LANGUAGE (Language summaries are written in (default English)), DRIFTNET_AGENT (Name recorded for this agent's saves and votes (default local)).