@graphite-atlas/mcp-server 1.2.1 → 1.2.2

package/dist/client.js

@@ -12,7 +12,7 @@ export class GraphiteAtlasClient {
             headers: {
                 Authorization: `Bearer ${config.accessToken}`,
                 "Content-Type": "application/json",
-                "User-Agent": "graphite-atlas-mcp/1.2.1",
+                "User-Agent": "graphite-atlas-mcp/1.2.2",
                 "X-Graphite-Source": "mcp",
             },
             timeout: 30000, // 30 second timeout

package/dist/tools/query.js

@@ -43,17 +43,17 @@ The atlas_id is automatically injected as the $atlasId parameter — use it in y
 
 Only read-only queries are allowed (MATCH, RETURN, WITH, WHERE, ORDER BY, LIMIT, UNWIND, OPTIONAL MATCH). Write operations (CREATE, MERGE, DELETE, SET) are blocked.
 
-GRAPH SCHEMA:
+CYPHER SCHEMA:
 
-Node labels:
-- :Point — all data nodes (people, processes, systems, etc.)
-- :Atlas — the atlas container node (one per atlas)
-- :Class — schema/ontology type definitions (internal)
+Cypher labels (used in MATCH patterns):
+- :Point — all points in the atlas (people, processes, systems, etc.)
+- :Atlas — the atlas container (one per atlas)
+- :Class — ontology type definitions (internal, rarely needed)
 
-Edge labels:
-- :PATH — all user-created relationships between points (has_role, reports_to, has_step, etc.). The relationship type is stored in the 'type' property on the edge, NOT as a separate label.
-- :CONTAINS — structural edge from Atlas → Point (every point is linked to its atlas)
-- :INSTANCE_OF — links a Point to its Class definition (internal)
+Cypher relationship types (used in path patterns):
+- :PATH — all paths between points (has_role, reports_to, has_step, etc.). The specific path type is stored in the 'type' property, NOT as a separate Cypher type.
+- :CONTAINS — structural link from Atlas to its Points (every point belongs to an atlas)
+- :INSTANCE_OF — links a Point to its ontology Class (internal, rarely needed)
 
 Point properties:
 - id (string) — unique identifier
@@ -70,20 +70,20 @@ Point properties:
 - updatedAt (string) — ISO timestamp
 - deletedAt (string, optional) — soft delete timestamp (filter with WHERE p.deletedAt IS NULL)
 
-PATH (edge) properties:
+Path properties:
 - id (string) — unique identifier
-- type (string) — relationship type from ontology (has_role, reports_to, followed_by, etc.)
+- type (string) — path type from ontology (has_role, reports_to, followed_by, etc.)
 - name (string) — same as type
-- description (string, optional) — context for this specific relationship
+- description (string, optional) — context for this specific path
 - properties (JSON string, optional) — arbitrary key-value pairs
 - createdAt, updatedAt, deletedAt — same as points
 
 IMPORTANT PATTERNS:
-- Always filter by atlasId: MATCH (p:Point {atlasId: $atlasId})
+- Always scope to the atlas: MATCH (p:Point {atlasId: $atlasId})
 - Always exclude soft-deleted: WHERE p.deletedAt IS NULL
-- Filter edges by type: WHERE r.type = 'has_role'
+- Filter paths by type: WHERE r.type = 'has_role'
 - The standard traversal: MATCH (a:Atlas {id: $atlasId})-[:CONTAINS]->(p:Point)
-- No result size limit is enforced server-side — use LIMIT in your queries to avoid huge result sets
+- No result size limit is enforced server-side — use LIMIT in your queries to avoid large result sets
 
 Example queries:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@graphite-atlas/mcp-server",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "Model Context Protocol server for Graphite Atlas",
   "type": "module",
   "main": "dist/index.js",