F
licenseB
qualityD
maintenanceAn MCP server that bridges Claude Code with Emacs via emacsclient, enabling buffer, file, org-mode, git, and diff operations.
55
-
Emacs Org-Mode MCP Server
by scanner
Related Servers
Alternatives to Emacs Org-Mode MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude to pause and ask clarifying questions via Emacs.5 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to control a running Emacs instance via MCP, supporting file opening, Magit integration, and server status checks.4MIT
- AlicenseBqualityDmaintenanceAn MCP server that connects Claude with Todoist for complete task and project management through natural language.86167 npm245MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for project planning inside Claude. It tracks progress, knows your codebase, and resumes exactly where you left off every session.6 npm5-
- AlicenseNot gradedqualityAmaintenanceTask and project management MCP server with OAuth for Claude Desktop, Cursor bridge, semantic search, staged write approval7 npmMIT
TDQS
A3.6/5.0
Scored across 19 tools
Disambiguation4/5
Tools are mostly distinct per resource and action, with clear descriptions separating get/list/search. Minor overlap exists between move_task and update_task (which can also move tasks via status changes), and diagnostic_env is unrelated to the org-mode domain.
Naming Consistency4/5
The dominant verb_noun pattern is consistent across tasks, journal entries, and projects (get_, create_, update_, search_, list_). Exceptions like diagnostic_env and the varying resource names (task vs journal_entry) are minor deviations, but the overall pattern remains predictable.
Tool Count3/5
At 19 tools, the set is on the heavy side for an MCP server covering three domains. Most tools have a clear purpose, but diagnostic_env is out of place and the paired list/search tools add some redundancy.
Completeness3/5
Tasks, journal entries, and projects all have create, read, and update coverage, but there are no delete operations for any resource type—an obvious lifecycle gap. Otherwise the core workflows are well covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues