PacketStream integration

Add PacketStream web search to Cline

Add PacketStream's remote MCP server to Cline with the Streamable HTTP transport and your API key, then check the tools and approvals.

Give Cline live Google results and readable web pages through PacketStream’s remote MCP server. Cline sends your API key in a header that you set in its MCP settings. The MCP server is in early beta.

Configure

Create an API key on the MCP page of the dashboard, then open Cline’s MCP settings:

  • In an IDE: in the Cline panel, select the MCP Servers icon, open the Configure tab, and select Configure MCP Servers.
  • Cline CLI: edit ~/.cline/data/settings/cline_mcp_settings.json.

Add the packetstream entry under mcpServers and replace YOUR_API_KEY with your key:

{
  "mcpServers": {
    "packetstream": {
      "type": "streamableHttp",
      "url": "https://api.packetstream.io/v1/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" },
      "disabled": false,
      "autoApprove": []
    }
  }
}
  • Keep "type": "streamableHttp". Without type, Cline uses the legacy SSE transport, which the server does not support.
  • Cline’s documentation does not describe environment-variable references in headers, so this entry holds the key itself. Keep the settings file private, and never commit or share it.

Check it works

  1. In the MCP Servers view, packetstream should be enabled and list packetstream_search and packetstream_fetch. In Cline CLI, run cline config mcp to list your servers.
  2. Check the key on its own with the free key check. Listing the tools works without a key, so a connected server does not prove the key works:
export PACKETSTREAM_API_KEY="YOUR_API_KEY"
curl -sS https://api.packetstream.io/v1/account \
  -H "Authorization: Bearer $PACKETSTREAM_API_KEY"

A working key returns your balance as JSON. A missing or wrong key returns HTTP 401 with the code unauthorized.

Then ask Cline something that needs current information. It should call packetstream_search.

Tool approvals

With an empty autoApprove list, Cline asks you before each PacketStream call. Every successful call is billed, and the server asks agents to use these tools for every web search and page fetch, so add a tool to autoApprove only when you are happy for it to run without asking.

Troubleshooting

  • The server does not connect, or reports HTTP 405. The entry has no "type": "streamableHttp", so Cline tried SSE. Add it and restart the server from the MCP Servers view.
  • The tool result says missing_api_key. The MCP server does not answer a missing key with HTTP 401. The tool call returns an error result that Cline reads and passes on, and the call is not billed. Add the headers entry shown above.
  • invalid_api_key. The header does not hold a PacketStream key, often because it still has the YOUR_API_KEY placeholder. It should read Bearer followed by a key that starts with ps_.
  • unauthorized. The key was revoked or replaced on the dashboard. Create a new key and update the entry.
  • Auto-approval stopped working after an update. Version 1.3.0 renamed web_search and web_fetch to packetstream_search and packetstream_fetch. Replace the old names in autoApprove.

See MCP client troubleshooting for the other error results.

Ready to give Cline live web results? Create an account, add funds, and create the API key on the MCP page of the dashboard.
Create account