# PacketStream MCP server

> Run live web searches and fetch web pages as Markdown through PacketStream's residential network.

- Listing: https://mcp.tc/i/packetstream
- Connect: use the server's own URL `https://api.packetstream.io/v1/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Search & Web Data](https://mcp.tc/c/search-web)
- Vendor: PacketStream
- Homepage: <https://packetstream.io/docs/mcp/>
- Docs: <https://packetstream.io/docs/mcp/>
- Repository: <https://github.com/packetstream/packetstream-mcp>

## About

PacketStream gives an assistant two read-only web tools. One runs live searches with country, language and location targeting across search, news, shopping, places, autocomplete, scholar and AI mode result types. The other fetches a public page and returns its main content as Markdown, routed through a residential network that can help with blocks and CAPTCHAs.

It runs as a hosted Streamable HTTP server, so nothing is installed locally. Users connect with a PacketStream API key sent as a Bearer token, or sign in with their PacketStream account through a separate OAuth URL. Calls are billed to a prepaid balance at $0.0025 each, and failed calls are free.

## What it can do

- Run live web searches with country, language and location targeting
- Search news, shopping, places, scholar and autocomplete results
- Fetch a public web page as Markdown
- Page through long documents with a start index
- Read pages that block direct datacenter requests

## Tools (2)

- `packetstream_search`: Run a live web search and return Markdown and JSON results with country, language and location… (read-only)
- `packetstream_fetch`: Fetch one public http(s) URL and return its main content as Markdown with status and title. (read-only)

## Example prompts

- "Search the web for the latest news on solid-state batteries in Germany."
- "Fetch https://example.com/blog/post and give me the Markdown content."
- "Find scholar results about retrieval augmented generation."
- "Look up coffee shops near Milan as a local user would see them."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http packetstream https://api.packetstream.io/v1/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
```

2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Use the `mcp-remote` bridge, which keeps the key on this computer (a connector added on claude.ai with the key under **Request headers** also shows up here). Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "packetstream": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.packetstream.io/v1/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=PacketStream&connectorUrl=https%3A%2F%2Fapi.packetstream.io%2Fv1%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://api.packetstream.io/v1/mcp`. Under **Request headers**, add `Authorization: Bearer <YOUR_API_KEY>` with your key from PacketStream, then click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=packetstream&config=eyJ1cmwiOiJodHRwczovL2FwaS5wYWNrZXRzdHJlYW0uaW8vdjEvbWNwIiwiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyIDxZT1VSX0FQSV9LRVk%2BIn19>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "packetstream": {
      "url": "https://api.packetstream.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "packetstream": {
      "type": "http",
      "url": "https://api.packetstream.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${input:api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "api-key",
      "description": "API key",
      "password": true
    }
  ]
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "packetstream": {
      "serverUrl": "https://api.packetstream.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add packetstream --url https://api.packetstream.io/v1/mcp --bearer-token-env-var PACKETSTREAM_API_KEY
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.packetstream]
url = "https://api.packetstream.io/v1/mcp"
bearer_token_env_var = "PACKETSTREAM_API_KEY"
```

Set `PACKETSTREAM_API_KEY` to your key in the shell that runs Codex.

### Gemini CLI

```bash
gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" packetstream https://api.packetstream.io/v1/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "packetstream": {
      "type": "http",
      "url": "https://api.packetstream.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.packetstream.io/v1/mcp`.

## Recent changes

- 2026-11-04 20:28 UTC: Tracking started: 2 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/packetstream#history (Atom feed: https://mcp.tc/i/packetstream/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.5.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-04
- Updated: 2026-11-04

---
Source: https://mcp.tc/i/packetstream (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
