Nogra MCP
OfficialRelated Servers
Alternatives to Nogra MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides tools for AI agents to manage long-term memories, daily notes, and TODO lists through a structured markdown file system. It enables context awareness by allowing agents to read, write, and search entries for persistent information storage.6 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage a file-backed ticketing system directly within a local repository using a structured state machine and directory hierarchy. It enforces strict markdown schemas and provides specialized tools for claiming tasks, appending work logs, and validating ticket metadata.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and tools to share durable, approved knowledge, current decisions, task ownership, and handoffs from a local-first workspace kept outside any single AI product. Markdown holds human-readable rules, goals, and narratives while SQLite tracks agents, sessions, tasks, leases, and audit events behind one transport-independent core.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with local documents (PDF, Markdown, TXT) through tools for discovery, reading, extraction, summarization, comparison, keyword extraction, search, and analysis, ensuring privacy and offline capability.-
- AlicenseNot gradedqualityFmaintenanceEnables secure local filesystem operations and interactive terminal sessions for AI assistants. Provides 12 tools for file management, directory operations, code searching, and running interactive REPLs with security protections.11 npmMIT
- AlicenseAqualityBmaintenanceProvides an AI agent with a searchable markdown notes vault, offering tools to create, read, list, search, update, and delete notes stored as plain .md files.6MIT
TDQS
Scored across 32 tools
Many tools overlap in purpose, particularly the transport_* suite (register, update, status, return, watch, ack, cleanup, dispatch, etc.) and the run/event tools (update_run, recent_runs, post_event). Despite detailed descriptions, the boundaries between transport runs and regular runs are unclear, leading to likely misselection.
Names follow multiple patterns: brief_* is consistent, but there is a mix of verb_noun (post_event, update_run) and transport_verb (transport_register, transport_submit_report) plus outliers like chain_pm_then_agent. No single convention dominates.
32 tools is on the high side for a workflow management server. While many tools serve distinct lifecycle stages, the transport/run duplication inflates the count. A more streamlined set of 15-20 tools would be more appropriate.
Covers brief CRUD, event logging, run updates, and handoff construction. However, there are gaps: no tool to delete a brief, no single-run retrieval (only recent_runs and transport_status), and no direct run creation (transport_register is separate). Core workflows are present but not fully closed.