by cbunting99
Kiro Memory is project tracking software for developers, offering task tracking, automatic detection, and context-aware
Provides intelligent memory management and task tracking for development projects with semantic search, automatic project detection, and persistent context across coding sessions.
Kiro Memory is a community-built MCP server published by cbunting99 that provides AI assistants with tools and capabilities via the Model Context Protocol. Kiro Memory is project tracking software for developers, offering task tracking, automatic detection, and context-aware It is categorized under ai ml, productivity.
You can install Kiro Memory in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Kiro Memory is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We wired Kiro Memory into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Kiro Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Kiro Memory has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated Kiro Memory against two servers with overlapping tools; this profile had the clearer scope statement.
I recommend Kiro Memory for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Kiro Memory surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, Kiro Memory benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Kiro Memory is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: Kiro Memory surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired Kiro Memory into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 31
⚡ Optimized for Claude Sonnet 4 - This MCP server works best with Claude Sonnet 4 for optimal performance and AI-powered features.
An enhanced MCP (Model Context Protocol) server for intelligent memory and task management, designed for AI assistants and development workflows. Features semantic search, automatic task extraction, knowledge graphs, and comprehensive project management.
enhanced-mcp-memory/
├── mcp_server_enhanced.py # Main MCP server with FastMCP integration
├── memory_manager.py # Core memory/task logic and project detection
├── sequential_thinking.py # Thinking chains and context optimization
├── database.py # Database operations with retry mechanisms
├── requirements.txt # Python dependencies
├── setup.py # Package configuration
├── data/ # SQLite database storage
├── logs/ # Application logs
# Install and run with uvx
uvx enhanced-mcp-memory
# Clone and install
git clone https://github.com/cbunting99/enhanced-mcp-memory.git
cd enhanced-mcp-memory
pip install -e .
# Run the server
enhanced-mcp-memory
# Clone repository
git clone https://github.com/cbunting99/enhanced-mcp-memory.git
cd enhanced-mcp-memory
# Install dependencies
pip install -r requirements.txt
# Run directly
python mcp_server_enhanced.py
Add to your MCP client configuration:
{
"mcpServers": {
"memory-manager": {
"command": "uvx",
"args": ["enhanced-mcp-memory"],
"env": {
"LOG_LEVEL": "INFO",
"MAX_MEMORY_ITEMS": "1000",
"ENABLE_AUTO_CLEANUP": "true"
}
}
}
}
{
"mcpServers": {
"memory-manager": {
"command": "python",
"args": ["mcp_server_enhanced.py"],
"cwd": "/path/to/enhanced-mcp-memory",
"env": {
"LOG_LEVEL": "INFO",
"MAX_MEMORY_ITEMS": "1000",
"ENABLE_AUTO_CLEANUP": "true"
}
}
}
}
get_memory_context(query) - Get relevant memories and contextcreate_task(title, description, priority, category) - Create new tasksget_tasks(status, limit) - Retrieve tasks with filteringget_project_summary() - Get comprehensive project overviewstart_thinking_chain(objective) - Begin structured reasoning processadd_thinking_step(chain_id, stage, title, content, reasoning) - Add reasoning stepsget_thinking_chain(chain_id) - Retrieve complete thinking chainlist_thinking_chains(limit) - List recent thinking chainscreate_context_summary(content, key_points, decisions, actions) - Compress context for token optimizationstart_new_chat_session(title, objective, continue_from) - Begin new conversation with optional continuationconsolidate_current_session() - Compress current session for handoffget_optimized_context(max_tokens) - Get token-optimized contextestimate_token_usage(text) - Estimate token count for planningauto_process_conversation(content, interaction_type) - Extract memories and tasks automaticallydecompose_task(prompt) - Break complex tasks into subtasksauto_learn_project_conventions(project_path) - Automatically detect and learn project patternsget_project_conventions_summary() - Get formatted summary of learned conventionssuggest_correct_command(user_command) - Suggest project-appropriate command correctionsremember_project_pattern(pattern_type, pattern, description) - Manually store project patternsupdate_memory_context() - Refresh memory context with latest project conventionshealth_check() - Check server health and connectivityget_performance_stats() - Get detailed performance metricscleanup_old_data(days_old) - Clean up old memories and tasksoptimize_memories() - Remove duplicates and optimize storageget_database_stats() - Get comprehensive database statisticsThe Enhanced MCP Memory Server automatically learns and remembers project-specific conventions to prevent AI assistants from suggesting incorrect commands or approaches:
# Instead of generic commands, suggests project-specific ones:
User types: "node server.js"
AI suggests: "Use 'npm run dev' instead for this project"
User types: "python main.py"
AI suggests: "Use 'uvicorn main:app --reload' for this FastAPI project"
cmd.exe and Windows-appropriate path separatorsdir instead of ls)All learned conventions are stored as high-importance memories that:
Configure via environment variables:
| Variable | Default | Description |
|---|---|---|
LOG_LEVEL | INFO | Logging level (DEBUG, INFO, WARNING, ERROR) |
MAX_MEMORY_ITEMS | 1000 | Maximum memories per project |
MAX_CONTEXT_TOKENS | 8000 | Token threshold for auto-compression |
CLEANUP_INTERVAL_HOURS | 24 | Auto-cleanup interval |
ENABLE_AUTO_CLEANUP | true | Enable automatic cleanup |
MAX_CONCURRENT_REQUESTS | 5 | Max concurrent requests |
REQUEST_TIMEOUT | 30 | Request timeout in seconds |
DATA_DIR | ~/ClaudeMemory | Where to store data and logs |
This package is production-ready and does not include a test suite in the distributed version. For development or CI, refer to the repository for test scripts and additional resources.
The server includes built-in performance tracking:
Access via the get_performance_stats() and health_check() tools.
Default locat
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.