bjjgraph
Related Servers
Alternatives to bjjgraph
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables Claude to search, query, and interact with an Enterprise Knowledge Management System (EKMS). Supports semantic search, knowledge recommendations, relationship graphs, and feedback recording for enterprise knowledge bases.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to intelligently analyze and query codebases using knowledge graphs, supporting natural language code search, relationship discovery, and incremental updates.11-
- AlicenseAqualityBmaintenanceEnables Claude to recall context from a merged knowledge graph of your Obsidian vault and code projects, providing tools to search, find neighbors, and discover paths before editing files. Works offline by reading a local brain.json.71MIT
- FlicenseAqualityDmaintenanceAutomatically organizes and merges learned CS knowledge into a graph structure using Claude for entity/relation extraction and SQLite for storage, with tools for ingestion, querying, merging, and managing nodes and edges.6-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to automatically extract entities and relationships from URLs, PDFs, and YouTube videos to build structured knowledge graphs in Neo4j. It supports custom schemas, academic citation extraction, and community detection for advanced research and content analysis.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables document ingestion and typed knowledge graph queries through Claude MCP tools, allowing agents to extract, store, and retrieve typed entities and relations from documents.2MIT
TDQS
Scored across 8 tools
Each tool targets a fairly distinct resource+action: search (fuzzy across all), list (enumerate one kind), get_technique/get_position/get_concept (detail per entity type), position_options (menu for a role), find_paths (routing), about (metadata). The closest pair is bjj_list vs bjj_search and bjj_position_options vs bjj_get_position, but the descriptions make the boundaries clear enough that an agent should pick correctly.
All tools share the bjj_ prefix and snake_case, with a mostly predictable verb-first pattern (search, list, get_technique, get_position, get_concept, find_paths) plus two noun-ish outliers (position_options, about). Minor deviation but highly readable.
Eight tools is well-scoped for a read-only knowledge graph: retrieval by search, enumeration, per-entity detail, position menus, pathfinding, and metadata. No obvious redundancy or missing bulk operations that would warrant extra tools.
The surface covers discovery (search/list), drill-down (get_technique/get_position/get_concept), role-based options, and navigation (find_paths), plus version metadata. Minor gaps like no explicit reverse lookup (e.g. techniques that end in a position) or bulk compare are workaroundable via search and find_paths.