Luciq, the mobile observability company formerly known as Instabug, published a guide to choosing between MCP, a CLI, a vendor’s own agent and your own agent for debugging. The rule of thumb is clean: “MCP is for conversation, the CLI is for automation.” Use MCP when the question is “why?” and takes follow-ups; use the CLI when the same answer has to come back in the same shape on a schedule, in a pipeline or over thousands of records. Underneath that sits the real claim, that the model is not the difference: “A model working from a stack trace alone is guessing. A model working from what happened on the device is debugging.”
Separate the figures by source. Luciq says its MCP server has handled 3.4 million agent queries since April 2026, with 158% month-over-month growth in invocations and 84% monthly retention. Those are Luciq’s own numbers, unaudited, and they are offered as proof that developers would rather bring context to the agent they already use. The other figure is borrowed: Scalekit’s 2026 benchmark found the same tasks cost 4 to 32 times more tokens through MCP than through a CLI, which Luciq uses to argue for pulling volume with scripts and handing the model only the slice that needs thinking. That advice survives without either number, as does the warning that user reports and reviews carry text a stranger wrote, which is exactly how prompt injection reaches an agent wired to an alert.
The Luciq record, still catalogued under Instabug, holds thirteen API pages, and the ones the post’s workflow runs through are the Crashes API and Occurrences API for the crash and its sessions, the Reviews API behind “which crashes are showing up in our 1-star reviews,” the Bugs API for user reports, and the Luciq Webhooks that would fire the alert-driven agent the post describes last. The agentic access profile counts 10 operations.
The Kin Score is 45.6, developing, with contract quality at 56.4 and operational transparency at 26.3. Agent Readiness is 29.6: agentic access, delegated identity, the event surface and a rate-limit signal are lit. mcp_server is unlit, on a record whose own description names the Luciq MCP Server at api.luciq.ai/api/mcp, for a company citing 3.4 million queries through it. The server is evidently real and used. What is missing is the signal an agent that has not been told about it would use to find it, and for a post whose thesis is that context decides the outcome, that is the context the catalog cannot yet see.