context-tracker-mcp1.0 1.0.13 → 1.0.15

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.
@@ -1,7 +1,9 @@
1
1
  ---
2
- description: Generate documentation for code
2
+ description: Generate code-level documentation (functions, APIs, examples)
3
3
  ---
4
4
 
5
+ # code-docs Workflow
6
+
5
7
  Generate clear documentation for the provided code:
6
8
 
7
9
  1. **README section** - Project overview, setup, usage
@@ -1,10 +1,10 @@
1
1
  ---
2
- description: Generate and maintain project documentation
2
+ description: Generate and maintain project-wide documentation
3
3
  ---
4
- # documentation Workflow
4
+ # project-docs Workflow
5
5
 
6
6
  1. Scan project structure
7
- 2. Generate docs
7
+ 2. Generate comprehensive project docs
8
8
  3. Setup auto-doc generation
9
9
 
10
10
  ## Usage
package/README.md CHANGED
@@ -1,321 +1,230 @@
1
1
  # Context Tracker MCP
2
2
 
3
- एक powerful MCP agent जो आपके development context को कभी नहीं भूलता और automatic documentation generate करता है।
3
+ ## Introduction
4
4
 
5
- ## 🚀 What's New (v1.0.0)
5
+ Context Tracker MCP is an intelligent Model Context Protocol (MCP) server designed to enhance development workflows through comprehensive context awareness. It serves as a bridge between the development environment and artificial intelligence assistants, enabling smarter, context-aware interactions during software development.
6
6
 
7
- **Concurrency Control** - Thread-safe operations with Mutex & ReadWriteLock
8
- ✅ **Unit Testing** - 70+ comprehensive Jest tests
9
- ✅ **Resource Pooling** - Smart caching with TTL management
10
- ✅ **Error Analysis** - Automatic error pattern detection
11
- ✅ **Project Intelligence** - Code metrics and recommendations
12
- ✅ **Configuration Management** - Dynamic config loading/updating
13
- ✅ **NPM Package Ready** - Distribute to any PC
14
-
15
- ---
16
-
17
- ## 📦 Installation & Deployment
18
-
19
- ### 1. Install Dependencies
20
-
21
- ```bash
22
- # MCP Server
23
- cd mcp
24
- npm install
25
-
26
- # VSCode Extension
27
- cd vscode-extension
28
- npm install
29
- ```
30
-
31
- ### 2. Build the Project
32
-
33
- ```bash
34
- # Build MCP Server
35
- cd mcp
36
- npm run build
37
-
38
- # Build VSCode Extension
39
- cd vscode-extension
40
- npm run compile
41
- ```
42
-
43
- ### 3. VSCode Extension Setup
44
-
45
- 1. VSCode में `Ctrl+Shift+P` press करें
46
- 2. `Extensions: Install from VSIX...` select करें
47
- 3. `vscode-extension` folder में generated `.vsix` file install करें
48
-
49
- ### 4. MCP Server Configuration
50
-
51
- अपने MCP client में यह configuration add करें:
52
-
53
- ```json
54
- {
55
- "mcpServers": {
56
- "context-tracker": {
57
- "command": "node",
58
- "args": ["path/to/context-tracker-mcp/dist/index.js"],
59
- "env": {
60
- "NODE_ENV": "production"
61
- }
62
- }
63
- }
64
- }
65
- ```
66
-
67
- ## 🎯 Usage
68
-
69
- ### VSCode Extension Commands
70
-
71
- - **`Ctrl+Shift+T`**: Track Current Context
72
- - **`Ctrl+Shift+H`**: Show Context History
73
- - **`Ctrl+Shift+D`**: Generate Documentation
74
- - **Right-click on CSS**: Track Styling
75
-
76
- ### Windsurf Workflows
77
-
78
- - **`/context-track`**: Start tracking new context
79
- - **`/context-update`**: Update existing context
80
- - **`/generate-docs`**: Generate documentation
81
- - **`/context-error`**: Log an error
82
-
83
- ### MCP Tools
84
-
85
- ```javascript
86
- // Track context
87
- await trackContext('start', {
88
- description: 'Adding user authentication',
89
- files: ['src/auth.ts', 'components/Login.tsx']
90
- });
91
-
92
- // Generate documentation
93
- const docs = await generateDocumentation('complete', 'markdown');
94
-
95
- // Log error
96
- await logError('TypeError: Cannot read property', 'Added null check', 'During login');
97
-
98
- // Track styling
99
- await trackStyling('.button', { color: 'blue', padding: '10px' }, 'styles.css');
100
- ```
101
-
102
- ## 📂 Project Structure
103
-
104
- ```
105
- context-tracker-mcp/
106
- ├── src/
107
- │ ├── index.ts # MCP Server entry point
108
- │ ├── context-tracker.ts # Core context tracking (Thread-safe)
109
- │ ├── documentation-generator.ts # Auto documentation
110
- │ ├── file-watcher.ts # File change monitoring
111
- │ ├── error-analyzer.ts # Error pattern analysis ⭐ NEW
112
- │ ├── project-intelligence.ts # Code metrics & insights ⭐ NEW
113
- │ ├── config-manager.ts # Configuration management ⭐ NEW
114
- │ ├── resource-manager.ts # Smart caching ⭐ NEW
115
- │ └── mutex.ts # Concurrency control ⭐ NEW
116
- ├── tests/ # Unit tests ⭐ NEW
117
- │ ├── context-tracker.test.ts
118
- │ ├── config-manager.test.ts
119
- │ ├── resource-manager.test.ts
120
- │ ├── error-analyzer.test.ts
121
- │ └── mutex.test.ts
122
- ├── vscode-extension/ # VSCode extension
123
- │ └── context-tracker-vscode-1.0.0.vsix
124
- ├── .windsurf/workflows/ # Windsurf workflows
125
- │ ├── co.md # Continue workflow ⭐ NEW
126
- │ ├── context-track.md
127
- │ └── generate-docs.md
128
- ├── context-data/ # Local data storage
129
- ├── DEPLOYMENT_GUIDE.md # Deployment instructions ⭐ NEW
130
- └── README.md
131
- ```
132
-
133
- ## 🔧 Configuration
134
-
135
- ### VSCode Settings
136
-
137
- ```json
138
- {
139
- "contextTracker.autoTrack": true,
140
- "contextTracker.watchedPaths": ["./src", "./components", "./styles"],
141
- "contextTracker.dataDirectory": "./context-data"
142
- }
143
- ```
144
-
145
- ### MCP Server Options
146
-
147
- ```javascript
148
- // Custom data directory
149
- const tracker = new ContextTracker('./my-context-data');
150
-
151
- // Custom watched paths
152
- await fileWatcher.initialize(['./src', './lib', './styles']);
153
- ```
154
-
155
- ## 📊 Data Storage
156
-
157
- सभी data locally store होता है:
158
-
159
- - **`context-data/context.json`**: Complete context history
160
- - **`context-data/errors.json`**: Error log with solutions
161
- - **`context-data/styling.json`**: Styling changes history
162
-
163
- ## 🎨 Examples
164
-
165
- ### Starting a New Feature
166
-
167
- ```bash
168
- # VSCode: Ctrl+Shift+T
169
- # Description: Adding user registration system
170
- # Files: src/auth/register.ts, components/RegisterForm.tsx
171
- ```
172
-
173
- ### Logging an Error
174
-
175
- ```bash
176
- # VSCode: Command Palette > Log Error
177
- # Error: Cannot read property 'email' of undefined
178
- # Solution: Added null validation before accessing email
179
- # Context: During user registration validation
180
- ```
181
-
182
- ### Tracking Styling
183
-
184
- ```css
185
- /* Select this CSS in VSCode and right-click > Track Styling */
186
- .button {
187
- background: #007bff;
188
- color: white;
189
- padding: 10px 20px;
190
- border-radius: 5px;
191
- }
192
- ```
193
-
194
- ### Generate Documentation
195
-
196
- ```bash
197
- # Windsurf: /generate-docs
198
- # Type: complete
199
- # Format: markdown
200
- ```
201
-
202
- ## 🚀 Advanced Usage
203
-
204
- ### Custom MCP Integration
205
-
206
- ```javascript
207
- import { ContextTracker } from './src/context-tracker.js';
208
-
209
- const tracker = new ContextTracker();
210
-
211
- // Track complex context
212
- await tracker.trackContext('start', {
213
- description: 'Building payment gateway',
214
- files: ['src/payment/', 'components/PaymentForm.tsx'],
215
- code: 'const payment = new PaymentProcessor();',
216
- metadata: {
217
- priority: 'high',
218
- estimatedHours: 8,
219
- dependencies: ['user-auth', 'database']
220
- }
221
- });
222
- ```
7
+ ## Requirements
223
8
 
224
- ### Custom Documentation
9
+ ### Prerequisites
225
10
 
226
- ```javascript
227
- import { DocumentationGenerator } from './src/documentation-generator.js';
11
+ Before installing Context Tracker MCP, ensure your system meets the following requirements:
228
12
 
229
- const generator = new DocumentationGenerator(tracker);
13
+ - **Node.js**: Version 18.0 or higher (LTS recommended)
14
+ - **npm**: Version 9.0 or higher (included with Node.js)
15
+ - **Operating System**: Windows, macOS, or Linux
230
16
 
231
- // Generate custom documentation
232
- const customDocs = await generator.generate('features', 'json');
233
- ```
17
+ ### Compatibility
234
18
 
235
- ## Deployment to Another PC
19
+ The MCP server is compatible with development environments that support the Model Context Protocol, including Windsurf IDE and other MCP-compatible editors.
236
20
 
237
- ### Method 1: NPM Package (Easiest)
21
+ ## Installation
238
22
 
239
- ```bash
240
- # On your PC (create package)
241
- npm run build
242
- npm pack
243
- # Creates: context-tracker-mcp-1.0.0.tgz
23
+ ### Quick Setup (Two Commands)
244
24
 
245
- # On other PC (install)
246
- npm install -g context-tracker-mcp-1.0.0.tgz
247
- context-tracker-mcp
248
- ```
25
+ Getting started with Context Tracker MCP requires only two simple commands:
249
26
 
250
- ### Method 2: VS Code Extension
27
+ **Step 1: Install the Package**
251
28
 
252
- ```bash
253
- # Package extension
254
- cd vscode-extension
255
- vsce package
256
- # Creates: .vsix file
29
+ Install the MCP server globally using npm. This command downloads and configures the package along with all its dependencies.
257
30
 
258
- # Install on other PC via VS Code
259
- # Extensions → Install from VSIX
260
- ```
31
+ **Step 2: Initialize Workflows**
261
32
 
262
- ### Method 3: Full Project
33
+ Navigate to your project directory and run the setup command. This creates the necessary configuration files and workflow definitions in your project.
263
34
 
264
- ```bash
265
- # Copy entire project folder
266
- # On other PC:
267
- npm install
268
- npm run build
269
- npm start
270
- ```
35
+ ### What Gets Installed
271
36
 
272
- ---
37
+ The installation process automatically configures:
273
38
 
274
- ## �🐛 Troubleshooting
39
+ - **MCP Server**: The core server that handles context tracking and analysis
40
+ - **Workflow Definitions**: Twelve pre-built workflows for common development tasks
41
+ - **Configuration Files**: Project-specific settings and preferences
42
+ - **Context Data Directory**: Storage location for tracked context and history
275
43
 
276
- ### Common Issues
44
+ ### Post-Installation Verification
277
45
 
278
- 1. **MCP Server Not Starting**
279
- ```bash
280
- npm run build
281
- node dist/index.js
282
- ```
46
+ After installation, the following directory structure will be present in your project:
283
47
 
284
- 2. **VSCode Extension Not Working**
285
- - Restart VSCode
286
- - Check MCP server is running
287
- - Verify configuration
48
+ - `.windsurf/mcp-config.json` - MCP server configuration
49
+ - `.windsurf/workflows/` - Workflow definition files
50
+ - `.context-data/` - Context tracking storage
288
51
 
289
- 3. **File Watching Not Working**
290
- - Check file permissions
291
- - Verify watched paths exist
292
- - Check .gitignore doesn't block files
52
+ ## Troubleshooting
293
53
 
294
- ### Debug Mode
54
+ ### Common Installation Issues
295
55
 
296
- ```bash
297
- # Enable debug logging
298
- DEBUG=context-tracker:* npm run dev
299
- ```
56
+ #### Node.js Not Found
300
57
 
301
- ## 🤝 Contributing
58
+ **Symptom**: Error messages indicating Node.js is not recognized or not installed.
302
59
 
303
- 1. Fork the repository
304
- 2. Create a feature branch
305
- 3. Make your changes
306
- 4. Add tests if needed
307
- 5. Submit a pull request
60
+ **Solution**: Download and install Node.js from the official website. Verify installation by running the version check command in your terminal.
308
61
 
309
- ## 📄 License
62
+ #### Permission Errors
310
63
 
311
- MIT License - see LICENSE file for details
64
+ **Symptom**: Access denied or permission-related errors during global installation.
312
65
 
313
- ## 🙏 Acknowledgments
66
+ **Solution**: On Windows, run your terminal as Administrator. On macOS and Linux, you may need to adjust npm permissions or use a Node version manager.
314
67
 
315
- - MCP (Model Context Protocol) team
316
- - VSCode extension API
317
- - Windsurf workflow system
68
+ #### Network Connectivity Issues
318
69
 
319
- ---
70
+ **Symptom**: Installation fails with timeout or network-related errors.
320
71
 
321
- **Made with ❤️ for developers who never want to lose context!**
72
+ **Solution**: Check your internet connection. If behind a corporate proxy, configure npm proxy settings. Alternatively, try installing at a different time when network conditions are stable.
73
+
74
+ #### Workflow Setup Fails
75
+
76
+ **Symptom**: The setup command reports missing files or directories.
77
+
78
+ **Solution**: Ensure you are running the setup command from your project root directory. The command must have write permissions to create the `.windsurf` and `.context-data` directories.
79
+
80
+ ### Configuration Issues
81
+
82
+ #### MCP Server Not Starting
83
+
84
+ **Symptom**: The development environment does not recognize the MCP server.
85
+
86
+ **Solution**: Verify that the global installation completed successfully. Check that the `.windsurf/mcp-config.json` file exists and contains valid JSON. Restart your development environment after configuration changes.
87
+
88
+ #### Workflow Commands Not Available
89
+
90
+ **Symptom**: Slash commands for workflows do not appear or execute.
91
+
92
+ **Solution**: Confirm that workflow files exist in the `.windsurf/workflows/` directory. Ensure your development environment has MCP support enabled and properly configured.
93
+
94
+ ### Getting Additional Help
95
+
96
+ If you encounter issues not covered in this section, consider the following resources:
97
+
98
+ - Verify system compatibility and requirements
99
+ - Check for updates to your development environment
100
+ - Review Node.js and npm documentation for environment-specific issues
101
+ - Consult the comprehensive documentation for detailed configuration options
102
+
103
+ ## Core Philosophy
104
+
105
+ The fundamental principle behind this tool is the preservation and intelligent utilization of development context. In modern software development, context is often lost between sessions, making it difficult for AI assistants to provide relevant assistance. This MCP server addresses this challenge by maintaining persistent context about codebases, errors, styling patterns, and project structures.
106
+
107
+ ## Architecture Overview
108
+
109
+ ### Context Management Layer
110
+ The server operates on a sophisticated context management layer that captures development activities in real-time. This layer tracks file changes, session activities, and project modifications, creating a comprehensive timeline of development work.
111
+
112
+ ### Intelligent Analysis Engine
113
+ At its core, the MCP incorporates analytical capabilities that examine project structures, identify patterns in errors, and analyze code organization. This engine provides insights that help developers understand their codebase better and make informed decisions.
114
+
115
+ ### Documentation Intelligence
116
+ The system includes specialized modules for documentation generation and maintenance. Rather than treating documentation as an afterthought, it integrates documentation creation into the development workflow itself.
117
+
118
+ ### Workflow Integration
119
+ A series of predefined workflows guide developers through common tasks. These workflows are not rigid procedures but intelligent guides that adapt to the specific needs of each project.
120
+
121
+ ## Key Capabilities
122
+
123
+ ### Session Tracking and Context Preservation
124
+ Development work happens in sessions, and each session generates valuable context. The system captures the essence of these sessions—what files were modified, what problems were encountered, what solutions were implemented. This preserved context enables continuity across interrupted work periods.
125
+
126
+ ### Error Pattern Recognition
127
+ Errors are not isolated incidents but patterns that emerge over time. By logging and analyzing errors along with their solutions, the system builds a knowledge base of common issues and their resolutions. This accumulated wisdom becomes invaluable for troubleshooting recurring problems.
128
+
129
+ ### Project Structure Analysis
130
+ Understanding how a project is organized is crucial for effective development. The system scans and analyzes project structures, identifying the relationships between components, the organization of files, and the overall architecture. This analysis helps in maintaining clean, well-organized codebases.
131
+
132
+ ### Automated Documentation
133
+ Documentation creation is often delayed or neglected due to time constraints. The system addresses this by providing automated documentation capabilities that generate comprehensive documentation from code structures and development activities.
134
+
135
+ ### Styling and Design Consistency
136
+ For projects involving user interfaces, maintaining consistent styling across components is essential. The system tracks styling decisions and patterns, ensuring visual coherence throughout the application.
137
+
138
+ ## Workflow System
139
+
140
+ The MCP includes twelve specialized workflows, each designed for specific development scenarios:
141
+
142
+ ### Code Organization Workflow
143
+ Focuses on improving code structure through logical file grouping, consistent naming conventions, and clear separation of concerns. It helps identify and eliminate duplicate code while establishing maintainable patterns.
144
+
145
+ ### Code Documentation Workflow
146
+ Concentrates on creating comprehensive documentation at the code level. This includes function-level explanations, API specifications, and usage examples that make code accessible to team members.
147
+
148
+ ### Project Documentation Workflow
149
+ Handles broader project documentation needs, including structural overviews, setup instructions, and maintenance guides. It ensures that project-level information is captured and preserved.
150
+
151
+ ### Context Tracking Workflow
152
+ Manages the capture and preservation of development context. It ensures that work sessions are tracked, important decisions are recorded, and context is available when needed.
153
+
154
+ ### Error Analysis Workflow
155
+ Specializes in examining errors, understanding their root causes, and documenting solutions. It builds a repository of troubleshooting knowledge that grows more valuable over time.
156
+
157
+ ### Explanation Workflow
158
+ Provides detailed explanations of code functionality. It helps team members understand complex implementations and architectural decisions.
159
+
160
+ ### Bug Fix Workflow
161
+ Guides the process of identifying, analyzing, and resolving bugs. It ensures systematic approaches to debugging and verification of fixes.
162
+
163
+ ### Optimization Workflow
164
+ Focuses on improving code performance and efficiency. It identifies bottlenecks, suggests improvements, and tracks optimization efforts.
165
+
166
+ ### Project Intelligence Workflow
167
+ Leverages accumulated project data to provide insights and suggestions. It helps identify trends, potential issues, and opportunities for improvement.
168
+
169
+ ### Refactoring Workflow
170
+ Supports code restructuring efforts while maintaining functionality. It ensures that refactoring is done systematically with proper testing.
171
+
172
+ ### Test Execution Workflow
173
+ Manages the running of test suites and analysis of results. It supports various testing modes including continuous testing and coverage analysis.
174
+
175
+ ### Test Generation Workflow
176
+ Automates the creation of unit tests and integration tests. It ensures comprehensive coverage and helps maintain code quality.
177
+
178
+ ## Data Storage and Persistence
179
+
180
+ The system stores its data in two primary locations within the project directory:
181
+
182
+ ### Context Data Directory
183
+ All tracking information, session histories, error logs, and analysis results are stored here. This includes the accumulated intelligence that the system builds over time.
184
+
185
+ ### Workflow Definitions
186
+ The predefined workflows are stored as markdown files, making them accessible and modifiable. These definitions guide how the system interacts with development tasks.
187
+
188
+ ### Configuration Management
189
+ The MCP maintains its own configuration settings, allowing customization of behavior, tracking preferences, and integration parameters.
190
+
191
+ ## Integration Model
192
+
193
+ The server integrates with development environments through the Model Context Protocol, a standardized interface for AI assistant communication. This integration enables seamless interaction between the development workflow and AI capabilities.
194
+
195
+ ### Real-time Monitoring
196
+ Through file watching capabilities, the system monitors project directories for changes. This real-time awareness allows immediate response to development activities.
197
+
198
+ ### Intelligent Suggestions
199
+ Based on accumulated context and patterns, the system provides context-aware suggestions. These suggestions are grounded in the actual state and history of the project.
200
+
201
+ ### Persistent Memory
202
+ Unlike transient development sessions, the system maintains persistent memory. This memory spans across sessions, providing continuity and building cumulative knowledge.
203
+
204
+ ## Benefits for Development Teams
205
+
206
+ ### Knowledge Preservation
207
+ When team members move between projects or leave the organization, their accumulated knowledge often disappears. The system preserves this knowledge, making it available to current and future team members.
208
+
209
+ ### Onboarding Acceleration
210
+ New team members can quickly understand project structure, common issues, and established patterns through the accumulated context and documentation.
211
+
212
+ ### Consistency Maintenance
213
+ By tracking patterns and enforcing workflows, the system helps maintain consistency across large codebases and distributed teams.
214
+
215
+ ### Reduced Cognitive Load
216
+ Developers don't need to remember every detail about the project. The system serves as an external memory, freeing mental resources for creative problem-solving.
217
+
218
+ ## Future Evolution
219
+
220
+ The architecture is designed for extensibility. Future enhancements may include:
221
+
222
+ - Integration with version control systems for deeper change tracking
223
+ - Enhanced pattern recognition using machine learning
224
+ - Collaboration features for team-wide context sharing
225
+ - Custom workflow creation capabilities
226
+ - Integration with project management tools
227
+
228
+ ## Conclusion
229
+
230
+ Context Tracker MCP represents a shift in how development context is managed. By treating context as a valuable asset to be preserved and utilized, it enables more intelligent development workflows. The combination of tracking, analysis, documentation, and workflow guidance creates an environment where AI assistance is truly context-aware and development knowledge is cumulative rather than ephemeral.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "context-tracker-mcp1.0",
3
- "version": "1.0.13",
3
+ "version": "1.0.15",
4
4
  "description": "MCP server for tracking context, code changes, and generating documentation",
5
5
  "main": "dist/index.js",
6
6
  "type": "module",