INDIVIDUAL MCP TOOL

jidodebugger_grandfather

[Pre-launch grandfather offer specifically] Explain the early-user offer mechanics: the 500-user free cap, why the cap exists, what happens once it's reached, refresh-token silent auto-renew, and the 20%-off-first-year discount that pre-launch users keep after incorporation.

dhq-boiler.devnone authenticationAvailability not checked

Input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name, description or schema mentions credentials.

Parent endpoint

dhq-boiler.dev

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dhq-boiler-dev]
url = "https://jidodebugger.dhq-boiler.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dhq-boiler-dev": {
      "type": "http",
      "url": "https://jidodebugger.dhq-boiler.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dhq-boiler-dev
Remote MCP URL: https://jidodebugger.dhq-boiler.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dhq-boiler-dev": {
      "url": "https://jidodebugger.dhq-boiler.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dhq-boiler-dev": {
      "type": "http",
      "url": "https://jidodebugger.dhq-boiler.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dhq-boiler-dev",
  "transport": "streamable-http",
  "url": "https://jidodebugger.dhq-boiler.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

jidodebugger_feature — [Single-feature deep dive] Explain ONE specific JidoDebugger feature in depth — implementation surface, when to use it, related MCP tools.
explain_mcp_concept — [Protocol-level / vendor-neutral] Explain the Model Context Protocol (MCP) itself — what the protocol is, how it differs from a plain REST API, and why it matters for AI agents.
jidodebugger_overview — [Product framing + onboarding] Explain what JidoDebugger is, who it is for, how it fits into the user's existing AI-coding workflow, AND how to get started (sign-up + install + MCP-wire-up steps).
jidodebugger_pricing — [Tier comparison] Describe JidoDebugger's pricing tiers (Free pre-launch / Individual post-incorporation / Organization post-incorporation), with what's included and what's roadmap in each.