QUICKSTART

Start Inspecting MCP Traffic in 5 Minutes

Route MCP traffic through DigitalPipe for governance, cost control, and hosted execution.

Sign up and get your proxy endpoint

Create an account at app.digitalpipe.net. Your proxy endpoint and API key are available immediately in your dashboard.

Your proxy endpoint:

https://[your-account].proxy.digitalpipe.net

Your API key:

dp_live_[your-api-key-here]

Swap your base URL

Update your MCP client config to point to the DigitalPipe proxy instead of the direct server URL. Everything else stays the same.

BEFORE (direct connection)

{
  "mcpServers": {
    "my-server": {
      "url": "https://example.com/mcp"
    }
  }
}

AFTER (through DigitalPipe)

{
  "mcpServers": {
    "my-server": {
      "url": "https://[your-account].proxy.digitalpipe.net?server=https://example.com/mcp"
    }
  }
}

The original server URL is passed as a query parameter. DigitalPipe routes the traffic and inspects it in real-time.

Watch your traffic in the dashboard

Return to app.digitalpipe.net. Your first proxied call appears instantly in the dashboard — request, response, latency, and tool names all visible.

What you'll see: Real-time call log with request/response payloads, latency per call, tool names invoked, and one-click kill switch for each connection.

Turn on Valve for traffic shaping

Valve adds per-key rate limits, concurrency caps, and circuit breakers so one noisy agent or failing provider cannot overwhelm your workloads.

Open Valve to watch traffic in real time, then tune limits from Settings → Valve.

Enable Manifold to cut token costs

Manifold exposes a small set of meta-tools instead of every tool schema. Agents still get the same results, but context-window usage drops sharply — especially for large catalogs.

Enable Manifold on any hosted MCP, then open the Manifold to see token savings, deduplicated calls, and queued bursts.

Configuration Examples

Claude Desktop (config.json)

{
  "mcpServers": {
    "filesystem": {
      "command": "node",
      "args": ["/path/to/claude-desktop-mcp/dist/index.js"]
    },
    "postgres": {
      "url": "https://your-account.proxy.digitalpipe.net?server=https://github.com/modelcontextprotocol/servers/tree/main/src/postgres"
    }
  }
}

TypeScript MCP Client

import { Client } from "@modelcontextprotocol/sdk/client";

const client = new Client({
  name: "my-app",
  version: "1.0.0"
}, {
  baseUrl: "https://your-account.proxy.digitalpipe.net?server=https://example.com/mcp",
  headers: {
    "Authorization": "Bearer dp_live_your-api-key"
  }
});

await client.connect();

Limits & Behavior

Local stdio servers

The hosted proxy cannot front local stdio servers (servers that run on localhost and communicate via stdin/stdout). It only works with HTTP-based MCP servers.

For stdio servers, the desktop agent on your machine needs to run DigitalPipe locally. See availability docs for more.

Ready for more?

Explore the API reference or jump straight to examples.

Dashboard Help See Examples