Close an AI client without leaving its MCP processes behind.
Windows developers using local MCP servers across several coding clients.
This is an early product concept currently being validated. The product is not yet available.
The problem
Client restarts can leave orphan server processes, duplicate instances and occupied ports.
What happens today
Inspect Task Manager, kill known processes and restart the client.
What I’m exploring
I’m exploring a tool that would offer: a local companion that associates supported MCP processes with their launching client and makes stale instances visible.
- Find the process owner
- Spot duplicate server instances
- Clean up only confirmed stale instances
These are proposed outcomes. There is no launch date yet.
Proposed early-access price
Would this save you enough time to be worth paying for? That’s what I’m testing.
$19 / month
No payment is collected. No subscription starts.
Would you use this?
If this is a problem you deal with, tell me a little about your workflow. Joining is an expression of interest. It does not start a subscription.
Please keep client details, credentials and confidential information out of your answers.
If your current tools already handle this, say so.
I want to understand what’s missing before I build anything. Your answers help me decide whether this deserves a next step. — Kai
Optional click and scroll mapping. No form contents, recordings or mouse trails. Basic page and signup funnel events are recorded separately.