← zephex.dev

INDIVIDUAL MCP TOOL

keep_thinking

Structure multi-step debugging and planning across tool calls — not a one-shot think.

zephex.devnone authenticationAvailability not checked

Input schema

{}

Risk classification

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

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent endpoint

zephex.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.zephex]
url = "https://zephex.dev/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "zephex": {
      "type": "http",
      "url": "https://zephex.dev/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: zephex
Remote MCP URL: https://zephex.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": {
    "zephex": {
      "url": "https://zephex.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "zephex": {
      "type": "http",
      "url": "https://zephex.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "zephex",
  "transport": "streamable-http",
  "url": "https://zephex.dev/mcp"
}
MCP Inspector

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

Related tools

  • get_project_context — Scans manifests and config — one topic slice per call.
  • explain_architecture — Maps how files connect across a subsystem — roles and import edges, not file bodies.
  • read_code — Extracts code surgically via tree-sitter AST — not repo-wide search.
  • find_code — PREFER over native Grep when location is unknown.
  • audit_headers — Audit a public HTTPS URL the user deployed — security grade A–F, SSL, headers, cookies, health (ALIVE/DEGRADED/BROKEN), exposed secrets, tech stack.
  • check_package — Check a public registry package before install or version bump — frameworks (next, react, vite), payments (stripe), auth (next-auth, clerk), ORMs (prisma, drizzle).
  • check_test — Run tests and return structured health — fix_first, broken_areas, failure_clusters, coverage_by_area, blind_spots, deploy probes.
  • Zephex_dev_info — Expert developer playbooks — not your repo.