kontexta
Related Servers
Alternatives to kontexta
- AlicenseAqualityBmaintenanceProvides AI assistants with real-time visibility into your codebase's internal libraries, team patterns, naming conventions, and usage frequencies to generate code that matches your team's actual practices.11310 npm68Elastic 2.0
Related Servers
- AlicenseAqualityCmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.3763 npm6MIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server that gives AI agents structured access to a personal Obsidian knowledge vault, with semantic search, organization through Maps of Content, and git-backed history.-
- AlicenseNot gradedqualityAmaintenanceLocal-first knowledge base MCP server. Lets AI agents (Claude Code, Cursor, etc.) read and write your personal knowledge base through 20 MCP tools. Zero cloud dependency — all files stay on your machine.1,758 npm704MIT
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server that gives AI assistants long-term memory by storing, searching, and recalling notes as Markdown files on your machine.14 npmMIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that gives AI coding agents persistent memory and context across sessions.4 npmMIT
- AlicenseAqualityCmaintenanceLocal MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.1667 npm1MIT
TDQS
Scored across 58 tools
Tools are clearly namespaced by subsystem (files_, tags_, calendar_events_, etc.) and each has a distinct action/resource, so most selections are unambiguous. There is still some overlap among browsing, search, and diagnostic tools such as files_list vs projects_map vs admin_overview, and files_search vs files_regex_search vs files_find_related, but the descriptions provide explicit selection guidance.
All 58 tools use snake_case with a predictable subsystem-prefix pattern (files_create, tags_add, calendar_events_update, hands_confirm, etc.). A few outliers like files_diff_against_disk and calendar_export_ics exist, but the overall convention is highly consistent.
58 tools is far beyond the typical 3-15 well-scoped range and risks overloading an agent's tool-selection process. The broad Kontexta platform does have several legitimate subdomains, so this is not an arbitrary explosion, but the set is still too heavy and could be consolidated.
The surface covers CRUD, search, history, tags, resources, journal, calendar entities/events, and Hands approvals comprehensively. Minor lifecycle gaps remain, such as no explicit project unregister/delete, no dedicated profile update tool, and no folder rename.