nowfound

Dev tools · alternatives · 2026

24 alternatives to MCP-tidy – How many MCPs in your Claude Code are you actually using?

Hi HN, I built mcp-tidy to solve a problem I kept running into with Claude Code. As I tried different MCP servers over the past few months, my ~/.claude.json accumulated servers I'd forgotten about. Claude Code loads all tool descriptions (built-in + MCP) into context, so unused servers add overhead you don't need. The tool is simple: three commands. - `mcp-tidy list` - see what's configured (global + per-project) - `mcp-tidy stats` - check actual usage from transcript logs - `mcp-tidy remove --unused` - clean up with automatic backup It parses the JSONL transcript logs in…

MCP-tidy is a utility for Claude Code users that identifies and removes unused Model Context Protocol servers from their configuration. It analyzes transcript logs to show which MCP servers are actually being used… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 2 we have checked on their own sites, 2 of them free or with a free tier.

  1. 1

    Store, review, and share your Claude Code sessions

    Mar 2026 · bench.silverstream.ai · its alternatives →

  2. 2

    Every MCP tool call dumps raw data into Claude Code's 200K context window. A Playwright snapshot costs 56 KB, 20 GitHub issues cost 59 KB. After 30 minutes, 40% of your context is gone. I built an MCP server that sits between Claude Code and these outputs. It processes them in sandboxes and only returns summaries. 315 KB becomes 5.4 KB. It supports 10 language runtimes, SQLite FTS5 with BM25 ranking for search, and batch execution. Session time before slowdown goes from ~30 min to ~3 hours. MIT licensed, single command install: /plugin marketplace add mksglu/claude-context-mode…

    Feb 2026 · github.com · its alternatives →

  3. 3

    I kept slamming into Claude Code limits mid-session and couldn’t find a quick way to see how close I was getting, so I hacked together a tiny local tracker. Streams your prompt + completion usage in real time Predicts whether you’ll hit the cap before the session ends Runs 100 % locally (no auth, no server) Presets for Pro, Max × 5, Max × 20 — tweak a JSON if your plan’s different GitHub: https://github.com/Maciek-roboblog/Claude-Code-Usage-Monitor It’s already spared me a few “why did my run just stop?” moments, but it’s still rough around the edges. Feedback, bug…

    2025 · github.com · its alternatives →

  4. 4
    Claudebin▲258

    Hi HN, We use Claude Code a lot, and after a long session there isn't a simple way to share exactly what happened with someone else. Prompts, responses, file edits, and tool calls all stay inside the terminal. We built Claudebin to make that easier. It's a plugin that lets you export the current session as a URL containing: - the full message thread - file reads and writes - bash commands - web and MCP calls You can send the link to someone, attach it to a PR, embed part of it, or resume the session locally. It's open source. GitHub:…

    Feb 2026 · claudebin.com · its alternatives →

  5. 5

    Hi all! I normally work on the PyTorch project but I've been on baby leave for the past month, so I've been playing around with AI as a user rather than a framework implementor. I really liked the agent experience with Claude Code, but I couldn't really justify spending so many dollars on API costs for random side projects. I already pay for a Claude Pro subscription though, and it turns out you can simulate many of Claude Code's features with an MCP. If you have a Pro subscription, check this out! I think it really captures the Claude Code experience quite well, without forcing you to pay…

    2025 · github.com · its alternatives →

  6. 6

    Continuous Claude is a CLI wrapper I made that runs Claude Code in an iterative loop with persistent context, automatically driving a PR-based workflow. Each iteration creates a branch, applies a focused code change, generates a commit, opens a PR via GitHub's CLI, waits for required checks and reviews, merges if green, and records state into a shared notes file. This avoids the typical stateless one-shot pattern of current coding agents and enables multi-step changes without losing intermediate reasoning, test failures, or partial progress. The tool is useful for tasks that require many…

    Nov 2025 · github.com · its alternatives →

  7. 7
    Claudy▲163

    A proper home for Claude Code — multi-session, multi-account

    May 2026 · claudy.markg.app · its alternatives →

  8. 8

    Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens. Tools like ccusage give a cost breakdown per model and per day, but I wanted to understand usage at the task level. CodeBurn reads the JSONL session transcripts that Claude Code stores locally (~/.claude/projects/) and classifies each turn into 13 categories based on tool usage patterns (no LLM calls involved). One surprising result: about 56% of my spend was on conversation turns with no tool usage. Actual coding (edits/writes) was…

    Apr 2026 · github.com · its alternatives →

  9. 9

    I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…

    Dec 2025 · github.com · its alternatives →

  10. 10

    I’ve been impressed with Claude Code but one thing that sometimes gets in the way in my workflows is the messy, mangled text that is shown when pasting text from the Claude Code terminal sessions. So I built an open-source utility that cleans extraneous white space, pipes, and other characters from your CC/Codex pastes. For example, you can turn this: `How can I create a Claude Code script that │ │ cleans up extraneous characters and cleans up │ │ extra spaces, new lines, and other messiness │ when I copy from Claude Code terminal │ │ prompts or copy code from Claude Responses in │ │…

    Mar 2026 · cleanclode.com · its alternatives →

  11. 11

    I use Claude Code across multiple projects with different conventions and some shared repos just as it so happens to be the real world. Managing the config files (.claude/rules/, mcps.json, settings.json) by hand got tedious, so I built a local web UI for it. This one started out as claude-config but migrated to coder-config as I'm adding others (Gemini, AG, Codex, etc). Main features: - Visual editor for rules, permissions, and MCP servers - Project registry to switch between codebases - "Workstreams" to group related repos (frontend + API + shared libs) with shared context -…

    Jan 2026 · github.com · its alternatives →

  12. 12

    I got tired of playwright-mcp eating through Claude's 200K token limit, so I built this using the new Claude Skills system. Built it with Claude Code itself. Instead of sending accessibility tree snapshots on every action, Claude just writes Playwright code and runs it. You get back screenshots and console output. That's it. 314 lines of instructions vs a persistent MCP server. Full API docs only load if Claude needs them. Same browser automation, way less overhead. Works as a Claude Code plugin or manual install. Token limit issue:…

    2025 · github.com · its alternatives →

  13. 13

    I built a lightweight project management workflow to keep AI-driven development organized. The problem was that context kept disappearing between tasks. With multiple Claude agents running in parallel, I’d lose track of specs, dependencies, and history. External PM tools didn’t help because syncing them with repos always created friction. The solution was to treat GitHub Issues as the database. The "system" is ~50 bash scripts and markdown configs that: - Brainstorm with you to create a markdown PRD, spins up an epic, and decomposes it into tasks and syncs them with GitHub issues - Track…

    2025 · github.com · its alternatives →

  14. 14RG

    Hey HN! I'm José, and I built Recall to solve a problem that was driving me crazy. The Problem: I use Claude for coding daily, but every conversation starts from scratch. I'd explain my architecture, coding standards, past decisions... then hit the context limit and lose everything. Next session? Start over. The Solution: Recall is an MCP (Model Context Protocol) server that gives Claude persistent memory using Redis + semantic search. Think of it as long-term memory that survives context limits and session restarts. How it works: - Claude stores important context as "memories" during…

    2025 · npmjs.com · its alternatives →

  15. 15

    We needed something like --dangerously-skip-permissions that doesn’t nuke your untracked files, exfiltrate your keys, or install malware. Claude Code's permission system is allow-or-deny per tool, but that doesn’t really scale. Deleting some files is fine sometimes. And git checkout is sometimes not fine. Even when you curate permissions, 200 IQ Opus can find a way around it. Maintaining a deny list is a fool's errand. nah is a PreToolUse hook that classifies every tool call by what it actually does, using a deterministic classifier that runs in milliseconds. It maps commands to action types…

    Mar 2026 · github.com · its alternatives →

  16. 16

    Resume Claude Code sessions for a fraction of the tokens

    Jul 2026 · github.com · its alternatives →

  17. 17

    Claude Code deleted my research and plan markdown files and informed me: “I accidentally rm -rf'd real directories in my Obsidian vault through a symlink it didn't realize was there: I made a mistake. “ Unfortunately the backup of my documentation accidentally hadn’t run for a month. So I built claude-file-recovery, a CLI-tool and TUI that is able to extract your files from your ~/.claude session history and thankfully I was able to recover my files. It's able to extract any file that Claude Code ever read, edited or wrote. I hope you will never need it, but you can find it on my GitHub…

    Feb 2026 · github.com · its alternatives →

  18. 18

    I built a tool that stores your full Claude Code history to let you easily find and resume sessions. It has TUI, CLI and MCP interfaces. It's a single Go binary, and the session history is synced to SQLite each time you use it. Default mode is the TUI with a session browser and full-text search. Once a session is selected you can browse and search within it, resume it or export to markdown. The MCP server provides tools to let Claude search back through the session for pre-compact context or pull from prior sessions. I use this constantly. I've seen elaborate continuity systems to give…

    Jan 2026 · github.com · its alternatives →

  19. 19

    Ask Claude Code where your usage went. Token audit, limit diagnosis and usage forensics — built from the session logs already on your machine, nothing leaves it. - kelviq/tare

    Aug 2026 · github.com · its alternatives →

  20. 20

    Hey HN! I built Retain as the evolution of claude-reflect (github.com/BayramAnnakov/claude-reflect). The original problem: I use Claude Code/Codex daily for coding, plus claude.ai and ChatGPT occasionally. Every conversation contains decisions, corrections, and patterns I forget existed weeks later. I kept re-explaining the same preferences. claude-reflect was a CLI tool that extracted learnings from Claude Code sessions. Retain takes this further with a native macOS app that: - Aggregates conversations from Claude Code, claude.ai, ChatGPT, and Codex CLI - Instant full-text…

    Jan 2026 · github.com · its alternatives →

  21. 21

    Did you know Claude Code deletes your session data after 30 days? I found out the hard way when I tried to check my spending history. My session files hit 3GB (2000+ files) and existing tools took 40+ seconds. Rewrote it in Rust with simd-json + rayon. - First run: ~1s (vs 40s+) - Daily use: ~0.04s (1000x faster, cached) - TUI dashboard with daily/weekly/monthly breakdown - Supports Claude Code, Codex CLI, Gemini CLI - Persistent cache — history survives even after CLI deletes files GitHub: https://github.com/mag123c/toktrack Feedback welcome!

    Feb 2026 · github.com · its alternatives →

  22. 22

    Hi HN, I built this because I got tired of the Claude Code CLI hiding details from me. Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts. I wanted a middle ground: *Full observability without the noise.* `claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time. *Unlike wrappers, it solves the visibility gap in your native…

    Feb 2026 · github.com · its alternatives →

  23. 23
    Scapefree tier, from $9.99/mo▲59

    Hey HN, we've been using Claude Code daily for months, and built Scape to fix our biggest pain point: managing multiple worktrees quickly & reducing the mental load of switching between them quickly. What we built: Scape is a macOS menu bar app that sits on top of Claude Code and gives you: - One-click worktrees: click a button, get a new git worktree with a Claude session already working on it. Develop in parallel without leaving your current branch. - Toolkit: per-session actions like "Create PR", "Commit & Push", "Run & Fix Tests." Add your own with bash scripts or prompts. -…

    24d ago · scape.work · its alternatives →

  24. 24

Also compare

Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →