Small, careful software for people who run AI agents — built in the open, shipped from day one.
A triage for broken MCP setups. One command scans the config files of the eight agent clients on your machine, explains what is broken in plain English — and repairs the mechanical class (comments, trailing commas) with a parse-gated write and a backup.
# every MCP client on this machine $ npx mcp-triage MCP Triage v0.1.0 — scanned 3 config file(s) Findings (4): [ERROR] Claude Desktop: trailing comma in JSON → remove the comma; restart the client [ERROR] Codex "notes-mcp": command not on PATH [WARN ] Codex "notes-mcp": relative path ./notes [INFO ] "filesystem" drifts across 2 clients Summary: 2 errors, 1 warning, 1 info # fix the mechanical class — with a backup $ npx mcp-triage --fix [FIXED] Claude Desktop — removed trailing comma
A read-only health check for your DeepSeek Harness session library. It spots the two things that quietly kill long agent sessions — runaway size (OOM risk) and crash-torn logs (unclosed turns that resume silently repairs).
# install the plugin $ dsh plugin --profile web add \ github:neufagents/dsh-healthcheck # then ask your agent > run a health check on my dsh sessions
We work on self-hosted AI agent setups — Claude Code, OpenClaw, DeepSeek Harness, n8n and similar stacks, MCP configs included: if a client still refuses to start after a clean mcp-triage scan, send us the report — that is the kind of case we take. New servers deployed and hardened, broken ones repaired, healthy ones looked after. Fully async, everything in writing — and we take on a small number of projects at a time, so each one gets done properly.
Your agent stack, freshly set up on a clean server — and proven to boot.
Something stopped working — we find the root cause and fix it.
Monitoring, backups and updates for a stack that has to stay up.
Write to us. A few lines: what you run (or want to run), where it lives, and what you need. Plain email — no forms, no calls.
Scope and price, in writing. We reply with exactly what we'll do, what it costs, and how access works — before anything is paid or touched.
Approve, then we work. You approve in writing; we do the work and hand over the proof — tests, logs, runbook.
Tell us what you're running — we'll tell you how we can help.
Usually answered within a business day.