@graphite-atlas/mcp-server 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (52) hide show
  1. package/EXAMPLES.md +501 -0
  2. package/LICENSE +21 -0
  3. package/README.md +440 -0
  4. package/dist/client.d.ts +272 -0
  5. package/dist/client.d.ts.map +1 -0
  6. package/dist/client.js +335 -0
  7. package/dist/client.js.map +1 -0
  8. package/dist/index.d.ts +16 -0
  9. package/dist/index.d.ts.map +1 -0
  10. package/dist/index.js +124 -0
  11. package/dist/index.js.map +1 -0
  12. package/dist/tools/analytics.d.ts +9 -0
  13. package/dist/tools/analytics.d.ts.map +1 -0
  14. package/dist/tools/analytics.js +374 -0
  15. package/dist/tools/analytics.js.map +1 -0
  16. package/dist/tools/atlases.d.ts +7 -0
  17. package/dist/tools/atlases.d.ts.map +1 -0
  18. package/dist/tools/atlases.js +132 -0
  19. package/dist/tools/atlases.js.map +1 -0
  20. package/dist/tools/batch.d.ts +10 -0
  21. package/dist/tools/batch.d.ts.map +1 -0
  22. package/dist/tools/batch.js +154 -0
  23. package/dist/tools/batch.js.map +1 -0
  24. package/dist/tools/brain-dump.d.ts +7 -0
  25. package/dist/tools/brain-dump.d.ts.map +1 -0
  26. package/dist/tools/brain-dump.js +98 -0
  27. package/dist/tools/brain-dump.js.map +1 -0
  28. package/dist/tools/index.d.ts +18 -0
  29. package/dist/tools/index.d.ts.map +1 -0
  30. package/dist/tools/index.js +29 -0
  31. package/dist/tools/index.js.map +1 -0
  32. package/dist/tools/mage.d.ts +10 -0
  33. package/dist/tools/mage.d.ts.map +1 -0
  34. package/dist/tools/mage.js +531 -0
  35. package/dist/tools/mage.js.map +1 -0
  36. package/dist/tools/paths.d.ts +7 -0
  37. package/dist/tools/paths.d.ts.map +1 -0
  38. package/dist/tools/paths.js +245 -0
  39. package/dist/tools/paths.js.map +1 -0
  40. package/dist/tools/points.d.ts +7 -0
  41. package/dist/tools/points.d.ts.map +1 -0
  42. package/dist/tools/points.js +225 -0
  43. package/dist/tools/points.js.map +1 -0
  44. package/dist/tools/validation.d.ts +9 -0
  45. package/dist/tools/validation.d.ts.map +1 -0
  46. package/dist/tools/validation.js +323 -0
  47. package/dist/tools/validation.js.map +1 -0
  48. package/dist/tools/views.d.ts +9 -0
  49. package/dist/tools/views.d.ts.map +1 -0
  50. package/dist/tools/views.js +335 -0
  51. package/dist/tools/views.js.map +1 -0
  52. package/package.json +62 -0
package/EXAMPLES.md ADDED
@@ -0,0 +1,501 @@
1
+ # Graphite Atlas MCP Server - Usage Examples
2
+
3
+ Real-world examples of using the Graphite Atlas MCP server with Claude Desktop.
4
+
5
+ ## Basic Atlas Operations
6
+
7
+ ### Creating a Knowledge Graph
8
+
9
+ **User**: "Create a new atlas called 'Product Research' for tracking competitive analysis"
10
+
11
+ **Claude** will use:
12
+ - Tool: `create_atlas`
13
+ - Parameters: `{ name: "Product Research", description: "Competitive analysis tracking" }`
14
+
15
+ **Result**: New atlas created with ID returned
16
+
17
+ ---
18
+
19
+ ### Listing Your Atlases
20
+
21
+ **User**: "What atlases do I have?"
22
+
23
+ **Claude** will use:
24
+ - Tool: `list_atlases`
25
+
26
+ **Response**:
27
+ ```
28
+ You have 3 atlases:
29
+ 1. Product Research (ID: atlas-123)
30
+ - Competitive analysis tracking
31
+ - Created: 2025-12-15
32
+
33
+ 2. Meeting Notes (ID: atlas-456)
34
+ - Weekly team meeting summaries
35
+ - Created: 2025-12-10
36
+
37
+ 3. Reading List (ID: atlas-789)
38
+ - Books and articles to read
39
+ - Created: 2025-12-01
40
+ ```
41
+
42
+ ---
43
+
44
+ ## Building a Knowledge Graph
45
+
46
+ ### Adding Points (Entities)
47
+
48
+ **User**: "In my Product Research atlas, add these companies: Anthropic, OpenAI, and Google DeepMind"
49
+
50
+ **Claude** will use `create_point` three times:
51
+ ```javascript
52
+ create_point({
53
+ atlas_id: "atlas-123",
54
+ name: "Anthropic",
55
+ type: "Company",
56
+ properties: { founded: "2021", focus: "AI Safety" }
57
+ })
58
+
59
+ create_point({
60
+ atlas_id: "atlas-123",
61
+ name: "OpenAI",
62
+ type: "Company",
63
+ properties: { founded: "2015", focus: "AGI Research" }
64
+ })
65
+
66
+ create_point({
67
+ atlas_id: "atlas-123",
68
+ name: "Google DeepMind",
69
+ type: "Company",
70
+ properties: { founded: "2010", focus: "AI Research" }
71
+ })
72
+ ```
73
+
74
+ ---
75
+
76
+ ### Creating Relationships
77
+
78
+ **User**: "Add a 'competes_with' relationship between Anthropic and OpenAI"
79
+
80
+ **Claude** will use `create_path`:
81
+ ```javascript
82
+ create_path({
83
+ atlas_id: "atlas-123",
84
+ name: "competes with",
85
+ type: "COMPETES_WITH",
86
+ source_id: "point-abc", // Anthropic
87
+ target_id: "point-def", // OpenAI
88
+ properties: { market: "Enterprise AI", intensity: "high" }
89
+ })
90
+ ```
91
+
92
+ ---
93
+
94
+ ## AI-Powered Graph Generation (Brain Dump)
95
+
96
+ ### Convert Meeting Notes to Graph
97
+
98
+ **User**: "Take these meeting notes and add them to my Meeting Notes atlas:
99
+
100
+ Team Sync - Dec 19, 2025
101
+ Attendees: Alice (PM), Bob (Eng), Carol (Design)
102
+
103
+ Alice presented the new user dashboard feature. Bob raised concerns about API rate limits. Carol showed mockups for the mobile view. We decided to prioritize the API optimization first, then implement the dashboard.
104
+
105
+ Action items:
106
+ - Bob: Investigate caching strategy
107
+ - Carol: Finalize mobile designs
108
+ - Alice: Update roadmap
109
+ "
110
+
111
+ **Claude** will use `brain_dump`:
112
+ ```javascript
113
+ brain_dump({
114
+ atlas_id: "atlas-456",
115
+ text: "[meeting notes]",
116
+ process_name: "Team Sync Dec 19"
117
+ })
118
+ ```
119
+
120
+ **Expected Graph** (AI-generated):
121
+ - **Points**:
122
+ - Alice (Person, role: PM)
123
+ - Bob (Person, role: Engineer)
124
+ - Carol (Person, role: Designer)
125
+ - User Dashboard (Feature)
126
+ - API Rate Limits (Issue)
127
+ - Mobile View (Design)
128
+ - Caching Strategy (Task, owner: Bob)
129
+ - Mobile Designs (Task, owner: Carol)
130
+ - Roadmap Update (Task, owner: Alice)
131
+
132
+ - **Paths**:
133
+ - Alice → PRESENTED → User Dashboard
134
+ - Bob → RAISED → API Rate Limits
135
+ - Carol → SHOWED → Mobile View
136
+ - API Optimization → BLOCKS → User Dashboard
137
+ - Bob → ASSIGNED_TO → Caching Strategy
138
+ - etc.
139
+
140
+ ---
141
+
142
+ ## Search and Discovery
143
+
144
+ ### Finding Related Information
145
+
146
+ **User**: "In my Product Research atlas, find all points related to 'AI safety'"
147
+
148
+ **Claude** will use `search_points`:
149
+ ```javascript
150
+ search_points({
151
+ atlas_id: "atlas-123",
152
+ query: "AI safety"
153
+ })
154
+ ```
155
+
156
+ **Response**:
157
+ ```
158
+ Found 5 points related to "AI safety":
159
+ 1. Anthropic (Company) - Focus: AI Safety
160
+ 2. Constitutional AI (Concept)
161
+ 3. RLHF (Technique) - Used for alignment
162
+ 4. AI Safety Research (Category)
163
+ 5. Alignment Problem (Challenge)
164
+ ```
165
+
166
+ ---
167
+
168
+ ## Complex Workflows
169
+
170
+ ### Building a Product Comparison
171
+
172
+ **User**: "I want to compare Claude, GPT-4, and Gemini. Create a comparison graph in my Product Research atlas."
173
+
174
+ **Claude** will:
175
+
176
+ 1. Create company points:
177
+ ```javascript
178
+ create_point({ name: "Anthropic", type: "Company" })
179
+ create_point({ name: "OpenAI", type: "Company" })
180
+ create_point({ name: "Google", type: "Company" })
181
+ ```
182
+
183
+ 2. Create product points:
184
+ ```javascript
185
+ create_point({
186
+ name: "Claude",
187
+ type: "AI Model",
188
+ properties: {
189
+ context_window: "200K tokens",
190
+ strengths: "Long context, helpful",
191
+ release_date: "2023"
192
+ }
193
+ })
194
+
195
+ create_point({
196
+ name: "GPT-4",
197
+ type: "AI Model",
198
+ properties: {
199
+ context_window: "128K tokens",
200
+ strengths: "Versatile, powerful",
201
+ release_date: "2023"
202
+ }
203
+ })
204
+
205
+ create_point({
206
+ name: "Gemini",
207
+ type: "AI Model",
208
+ properties: {
209
+ context_window: "1M tokens",
210
+ strengths: "Multimodal, fast",
211
+ release_date: "2023"
212
+ }
213
+ })
214
+ ```
215
+
216
+ 3. Create relationships:
217
+ ```javascript
218
+ create_path({
219
+ name: "develops",
220
+ type: "DEVELOPS",
221
+ source_id: "anthropic_id",
222
+ target_id: "claude_id"
223
+ })
224
+
225
+ create_path({
226
+ name: "develops",
227
+ type: "DEVELOPS",
228
+ source_id: "openai_id",
229
+ target_id: "gpt4_id"
230
+ })
231
+
232
+ create_path({
233
+ name: "develops",
234
+ type: "DEVELOPS",
235
+ source_id: "google_id",
236
+ target_id: "gemini_id"
237
+ })
238
+ ```
239
+
240
+ ---
241
+
242
+ ## Data Management
243
+
244
+ ### Updating Information
245
+
246
+ **User**: "Update the Claude point to reflect that the context window is now 500K tokens"
247
+
248
+ **Claude** will use `update_point`:
249
+ ```javascript
250
+ update_point({
251
+ atlas_id: "atlas-123",
252
+ point_id: "point-claude",
253
+ properties: {
254
+ context_window: "500K tokens"
255
+ }
256
+ })
257
+ ```
258
+
259
+ ---
260
+
261
+ ### Bulk Operations
262
+
263
+ **User**: "Add tags to all AI model points in my Product Research atlas with tag 'LLM'"
264
+
265
+ **Claude** will:
266
+
267
+ 1. List all points: `list_points({ atlas_id: "atlas-123" })`
268
+ 2. Filter AI models
269
+ 3. Update each with tag:
270
+ ```javascript
271
+ update_point({
272
+ atlas_id: "atlas-123",
273
+ point_id: "point-claude",
274
+ properties: { tags: ["LLM"] }
275
+ })
276
+ // Repeat for GPT-4, Gemini, etc.
277
+ ```
278
+
279
+ ---
280
+
281
+ ## Visualization and Analysis
282
+
283
+ ### Getting Graph Statistics
284
+
285
+ **User**: "How many points and relationships are in my Product Research atlas?"
286
+
287
+ **Claude** will:
288
+
289
+ 1. List points: `list_points({ atlas_id: "atlas-123" })`
290
+ 2. List paths: `list_paths({ atlas_id: "atlas-123" })`
291
+
292
+ **Response**:
293
+ ```
294
+ Your Product Research atlas contains:
295
+ - 47 points (entities)
296
+ - 82 paths (relationships)
297
+
298
+ Breakdown by type:
299
+ Points:
300
+ - 12 Companies
301
+ - 18 Products
302
+ - 10 Concepts
303
+ - 7 People
304
+
305
+ Paths:
306
+ - 25 DEVELOPS relationships
307
+ - 20 COMPETES_WITH relationships
308
+ - 15 USES relationships
309
+ - 12 RELATED_TO relationships
310
+ - 10 FOUNDED_BY relationships
311
+ ```
312
+
313
+ ---
314
+
315
+ ## Advanced Use Cases
316
+
317
+ ### Research Paper Analysis
318
+
319
+ **User**: "I just read this AI safety paper. Add it to my Reading List atlas and extract key concepts:
320
+
321
+ [Paste abstract of AI alignment paper...]
322
+ "
323
+
324
+ **Claude** will use `brain_dump` to:
325
+ - Create point for the paper
326
+ - Extract key concepts (alignment, reward hacking, value learning, etc.)
327
+ - Create relationships between concepts
328
+ - Link authors to the paper
329
+
330
+ ---
331
+
332
+ ### Project Planning
333
+
334
+ **User**: "Help me plan a new project called 'Mobile App Redesign' in my Product Research atlas"
335
+
336
+ **Claude** will create a project graph:
337
+
338
+ 1. Main project point:
339
+ ```javascript
340
+ create_point({
341
+ name: "Mobile App Redesign",
342
+ type: "Project",
343
+ properties: {
344
+ status: "Planning",
345
+ deadline: "Q2 2026",
346
+ priority: "High"
347
+ }
348
+ })
349
+ ```
350
+
351
+ 2. Feature points:
352
+ - User Authentication
353
+ - Dark Mode
354
+ - Offline Support
355
+ - Push Notifications
356
+
357
+ 3. Dependencies:
358
+ - Authentication → BLOCKS → Dark Mode
359
+ - Dark Mode → BLOCKS → Offline Support
360
+
361
+ 4. Team members:
362
+ - Alice (PM) → OWNS → Mobile App Redesign
363
+ - Bob (Eng) → WORKS_ON → User Authentication
364
+ - Carol (Design) → WORKS_ON → Dark Mode
365
+
366
+ ---
367
+
368
+ ## Integration Patterns
369
+
370
+ ### Daily Standup Notes
371
+
372
+ **User**: "Convert today's standup notes to my Meeting Notes atlas"
373
+
374
+ Use brain_dump regularly to build a historical graph of:
375
+ - What team members worked on
376
+ - Blockers and dependencies
377
+ - Decisions made
378
+ - Action items
379
+
380
+ Over time, this builds a searchable knowledge base of your team's work.
381
+
382
+ ---
383
+
384
+ ### Personal Knowledge Management
385
+
386
+ Use multiple atlases:
387
+ - **Daily Notes**: Brain dump daily journal entries
388
+ - **Reading**: Track books, articles, papers with brain dump
389
+ - **Projects**: Manually curate project structure
390
+ - **People**: Network graph of contacts and relationships
391
+
392
+ Ask Claude:
393
+ - "What did I work on last week?" (search Meeting Notes)
394
+ - "Who do I know at Google?" (search People atlas)
395
+ - "What papers have I read about transformers?" (search Reading atlas)
396
+
397
+ ---
398
+
399
+ ## Tips and Best Practices
400
+
401
+ ### 1. Use Descriptive Names
402
+
403
+ **Good**:
404
+ ```javascript
405
+ create_point({
406
+ name: "Claude 3.5 Sonnet",
407
+ type: "AI Model",
408
+ properties: { version: "3.5", variant: "Sonnet" }
409
+ })
410
+ ```
411
+
412
+ **Bad**:
413
+ ```javascript
414
+ create_point({
415
+ name: "Model 1",
416
+ type: "Thing"
417
+ })
418
+ ```
419
+
420
+ ### 2. Consistent Relationship Types
421
+
422
+ Use ALL_CAPS for relationship types to match graph database conventions:
423
+ - `WORKS_AT`
424
+ - `KNOWS`
425
+ - `DEPENDS_ON`
426
+ - `PART_OF`
427
+
428
+ ### 3. Leverage Properties
429
+
430
+ Store rich metadata in properties:
431
+ ```javascript
432
+ create_point({
433
+ name: "Research Paper: Attention is All You Need",
434
+ type: "Paper",
435
+ properties: {
436
+ authors: ["Vaswani", "Shazeer", "Parmar"],
437
+ year: 2017,
438
+ citations: 85000,
439
+ url: "https://arxiv.org/abs/1706.03762",
440
+ tags: ["transformers", "attention", "NLP"]
441
+ }
442
+ })
443
+ ```
444
+
445
+ ### 4. Use Brain Dump for Speed
446
+
447
+ Instead of manually creating points and paths, use brain_dump for:
448
+ - Meeting notes
449
+ - Articles/papers
450
+ - Brainstorming sessions
451
+ - Interview transcripts
452
+
453
+ Then refine manually if needed.
454
+
455
+ ### 5. Regular Searches
456
+
457
+ Don't just add data—query it!
458
+ - "What concepts am I tracking about AI safety?"
459
+ - "Show me all the projects blocked by API work"
460
+ - "Which people are connected to the mobile app project?"
461
+
462
+ ---
463
+
464
+ ## Troubleshooting Examples
465
+
466
+ ### "I can't find a point I just created"
467
+
468
+ Try searching:
469
+ ```
470
+ "Search for [point name] in my [atlas name] atlas"
471
+ ```
472
+
473
+ If still not found, list all points:
474
+ ```
475
+ "List all points in my [atlas name] atlas"
476
+ ```
477
+
478
+ ### "Wrong atlas used"
479
+
480
+ Always specify the atlas:
481
+ ```
482
+ "In my Product Research atlas, create a point called..."
483
+ ```
484
+
485
+ Not:
486
+ ```
487
+ "Create a point called..."
488
+ ```
489
+
490
+ ### "Relationship creation failed"
491
+
492
+ Check that both points exist first:
493
+ ```
494
+ "List points in my atlas and show IDs"
495
+ ```
496
+
497
+ Then create path with correct IDs.
498
+
499
+ ---
500
+
501
+ **For more examples, see the [Graphite Atlas documentation](https://docs.graphiteatlas.com).**
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2025 Graphite Atlas
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.