DeepTap as an MCP server.

Install in Claude Desktop

Edit your claude_desktop_config.json:

{
  "mcpServers": {
    "deeptap": {
      "command": "npx",
      "args": ["-y", "{{TBD-mcp-package}}"],
      "env": {
        "DEEPTAP_API_KEY": "dt_live_..."
      }
    }
  }
}

Restart Claude Desktop. The DeepTap tools appear in the tool picker.

Install in Continue

Continue's config.json uses the same MCP server shape:

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "name": "deeptap",
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": ["-y", "{{TBD-mcp-package}}"]
        }
      }
    ]
  }
}

Tools exposed

• deeptap_search: depth-1 or depth-2 retrieve. Wraps POST /v1/search. Accepts query, depth (1 or 2), and an optional corpus_id.
• deeptap_research: depth-3 iterate plus synthesize. Wraps POST /v1/research. Streams progress.
• deeptap_cache_lookup: read-only fact cache lookup. Wraps the cache check layer in isolation. Useful when an agent wants to verify a fact without running full retrieval.

Worked example, depth 1

// MCP client invocation
{
  "tool": "deeptap_search",
  "args": {
    "query": "Top three vector databases by GitHub stars in 2026.",
    "depth": 1
  }
}

// Server response (depth 1)
{
  "depth": 1,
  "rounds_executed": 1,
  "facts": [
    { "claim": "...", "confidence": 0.93, "source_url": "..." }
  ],
  "credits_charged": "{{TBD-depth-1-credits}}"
}

Worked example, depth 2

{
  "tool": "deeptap_search",
  "args": {
    "query": "Compare data residency guarantees of the top five US-region cloud LLM providers.",
    "depth": 2
  }
}

// Server response carries the saturation reason
{
  "depth": 2,
  "rounds_executed": 2,
  "stop_reason": "facet_ledger_saturated",
  "facts": [ /* ... */ ]
}

Worked example, depth 3

{
  "tool": "deeptap_research",
  "args": {
    "query": "Build a competitive landscape for prompt-injection defenses.",
    "depth": 3,
    "stream": true
  }
}

// Streamed progress events
{ "event": "round_started", "round": 1 }
{ "event": "round_complete", "round": 1, "facets_filled": 3 }
{ "event": "round_started", "round": 2 }
// ... until ...
{ "event": "stopped", "stop_reason": "stopping_ai_satisfied" }
{ "event": "synthesis", "report_html": "..." }

MCP conformance notes

• Transport: stdio for local installs, SSE for hosted multi-tenant deployments.
• Resource exposure: cached facts are exposed as MCP resources scoped by tenant; the host can read them without running a query.
• Auth pass-through: API key, x402, MPP, and TrueCom modes all work through the MCP server. See Auth and payment.