mapnotes
Related Servers
Alternatives to mapnotes
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Neo4j graph databases through natural language, supporting Cypher queries, schema management, data manipulation, and graph algorithms.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create, edit, and export flowcharts through a local web-based editor with visual drag-and-drop, real-time sync, and 14 MCP tools for full node/edge CRUD.2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Gremlin-compatible graph databases through natural language, supporting schema discovery, complex graph queries, relationship analysis, and data import/export operations.15 npm9MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to interact with LightRAG knowledge graphs, supporting smart upsert for Obsidian vaults, semantic queries, and document/graph management.188Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to read and edit a spatial canvas board of notes, tasks and ideas through the running desktop app, creating, updating, linking, grouping and arranging nodes, importing files, focusing the view and undoing changes so edits appear instantly and stay reversible.257 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to explore and extend a local-first, SQLite-backed visual knowledge graph through 12 tools for listing maps, searching and reading nodes, and creating, updating, or linking nodes and edges. Every AI-written node carries provenance and is checked against near-duplicate titles, so agent-added ideas appear in a shared graph that people also edit by hand.MIT
TDQS
Scored across 14 tools
Each tool targets a distinct resource/action pair: graph file I/O (load/save), whole-graph retrieval, node/edge CRUD, graph property editing, and style management. get_node vs find_nodes are clearly differentiated (detail vs search), and edit_node/edit_edge/edit_graph_properties have non-overlapping targets.
All tool names use a consistent snake_case verb_noun pattern (load_graph, save_graph, get_node, add_edge, edit_node, remove_style, etc.). There are no deviations into camelCase or vague single-word names.
The 14 tools precisely cover the graph-notes domain without redundancy. Each tool earns its place by handling a specific operation on nodes, edges, graph properties, or styles.
Core lifecycle coverage is strong: nodes have add/get/list/edit/remove, edges have add/edit/remove, and graph properties/styles are editable. Minor gaps exist: no direct get_edge or list_styles/get_style, though these can be inferred from get_graph or get_node.