F
licenseNot graded
qualityB
maintenanceModel Context Protocol server for MCPGRAM that enables MCP clients to interact with connectors like GitHub, Slack, and Notion through stdio or Streamable HTTP transports.
-
nexusm-mcp-server
by 10CG
Related Servers
Alternatives to nexusm-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for the Synapse ecosystem that exposes the Synapse Memory API, Browser Proxy, and SSH Proxy as MCP tools, enabling multi-tenant, stateful interactions via stdio or HTTP/SSE.5 npm1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that exposes the Nexidion knowledge base as tools, enabling node management, search, and task creation through the MCP protocol. Supports stdio and OAuth-protected HTTP modes with per-user permissions.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that wraps the nexus CLI, giving AI agents cross-session memory, semantic search, preference learning, and smart context injection.109 npmMIT
orca-mcpofficial
AlicenseNot gradedqualityAmaintenanceExternal MCP server for controlling Orca worktrees, agent sessions, and multi-agent orchestration from any MCP client via stdio or Streamable HTTP.20 npm1MIT- AlicenseAqualityCmaintenanceProvides a Model Context Protocol server with tools for knowledge base search, retrieval, and addition, plus system time, resources, and prompts. Supports stdio and Streamable HTTP transports for local and shared deployments.4MIT
TDQS
A3.9/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: context_retrieve for broad context, memory_create for storing, memory_feedback for feedback, memory_search for targeted search. No overlap.
Naming Consistency4/5
All tools follow nexus_verb_noun pattern with snake_case. Slight inconsistency: two use 'memory_' prefix, one uses 'context_', but this reflects functional difference.
Tool Count5/5
Four tools cover core memory operations perfectly: creation, two retrieval modes, and feedback. No redundancy, each tool earns its place.
Completeness3/5
CRUD surface is incomplete: update and delete for memories are missing. Feedback partially addresses quality improvement, but lifecycle management has gaps.
Maintenance
ActivityMaintained
ResponsivenessNo issues