Announced Oct 22, Claude users can now add Qlik from the Claude Directory to search Qlik Cloud apps and datasets, ask questions over governed data, trace lineage, and build sheets and charts by prompt, all under existing Qlik permissions via OAuth. Access needs the Qlik MCP: Allowed role permission (setup docs).
Add one URL ( https://agentic testnet mcp.hedera.com/mcp ) and sign in with a HashPack or Kabila wallet over OAuth, and your agent can transfer HBAR, mint tokens, deploy contracts, and post consensus messages, but the server holds no keys and every transaction waits for your wallet approval. It's testnet only, with no spend caps, so the wallet prompt is your only guardrail (CryptoCompass)…
Released Oct 22, it reuses cached local MCP tool snapshots across registered Git worktrees in one repo, makes ACP sessions honor saved sandbox settings and sandbox / no sandbox on resume, and swaps the legacy remote / no remote startup flags for clearer hosting and connection options. It also fixes Gemini tool calls failing schema validation on nullable and enum fields and keeps cloud replies intact after a dropped connection…
Generally available Oct 22, the MCP gives any compatible agent 46 tools to query digital experience data, summarize user sessions, build funnels, and run monitoring agents, each returning structured data plus how the answer was produced. Teams are wiring it into coding and design agents so UX friction can be detected, fixed, and measured in a loop, and into incident triage ranked by customer impact…
Shipped Oct 22, amp orb provider ./dispatch.sh connects out to Amp and hands spawn, pause, and delete jobs to your own script, so the checkout, builds, and orb disks stay on your infrastructure while Amp still runs the agent loop and models; a Helm chart covers GKE, EKS, and AKS. It's free for individuals and teams, and Amp never connects into your network (docs)…
Launched Oct 22, it reads your published app's production logs and metrics when an alert fires, finds the cause, validates a fix, and emails you a summary of what happened. Autofix alerting is turned on in the app's Publishing settings, and fixes only ship to production automatically if you also enable auto publish…
Spotted something we missed? Start a thread.
