Kitden
Related Servers
Alternatives to Kitden
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceShows what is consuming your agent context window before a session starts: always-loaded skill descriptions ranked by token cost, skills installed more than once under different names, CLAUDE.md/AGENTS.md sizes including what their @import lines pull in, and MCP servers configured across clients. Read-only: no child processes, no network.591 npmMIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that enables inspecting and auditing markdown agent steering files such as CLAUDE.md, AGENTS.md, GEMINI.md, SKILL.md, rules, commands and memory files. It reads files byte-exactly, outlines headings, lints frontmatter, invisible characters and broken links, estimates per-session token budgets, and locates steering files by when they load, all without ever writing, deleting or making network calls.MIT
- AlicenseNot gradedqualityCmaintenanceAutomatically synchronizes and deduplicates MCP configurations from Claude Code, Codex CLI, Cursor Agent, and custom sources, providing a centralized view and management interface.82 npmMIT
- AlicenseAqualityCmaintenanceEnumerates everything in a code checkout addressed to an AI agent, including instruction files, hook commands, declared MCP servers, and skills/subagents, so you can review what your agent will actually follow.587 npm1MIT
- AlicenseAqualityBmaintenanceInventory local Codex plugins and Skills, inspect recorded usage, and identify potential redundancy to support user-directed cleanup. Includes a local MCP service, dashboard, and companion Skills; requires Windows and a local Codex environment.131Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code users to inventory the MCP servers, skills, commands, agents and plugins installed on their machine, estimate how many tokens each one adds to every request, and switch them off per project or globally, including across other AI coding tools. It also monitors live sessions to report real token usage and the savings achieved from disabled items.5 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct target: project inventory (list_projects), loaded configuration (show_setup), detected problems (list_findings), and single-name resolution (explain_item). The show_setup vs. list_findings boundary is reinforced by descriptions—one reports what loads, the other reports what is wrong—so misselection is unlikely.
All four names follow the same verb_noun snake_case pattern: show_setup, list_findings, explain_item, list_projects. The verbs are predictable and match the read-only nature of the server.
Four tools is well-scoped for a read-only configuration diagnostic server; each covers a distinct query axis (projects, setup, findings, single item). There are no redundant or filler tools, and the count sits comfortably in the typical 3–15 range.
The read-only diagnostic surface is largely complete: projects, per-project setup, problem findings, and per-item resolution are all covered. Minor gaps remain—no raw config export, change history, or explicit gateway-status query—but these are not central to the stated purpose and are partly addressed by list_findings.