Agentic Tools MCP Server

Agentic Tools MCP Server

A Model Context Protocol server providing AI assistants with comprehensive project, task, and subtask management capabilities with project-specific storage.

Category
Visit Server

README

Agentic Tools MCP Server

A comprehensive Model Context Protocol (MCP) server providing AI assistants with powerful task management and agent memories capabilities with project-specific storage.

Features

🎯 Complete Task Management System

  • Projects: Organize work into distinct projects with descriptions
  • Tasks: Break down projects into manageable tasks
  • Subtasks: Further decompose tasks into actionable subtasks
  • Hierarchical Organization: Projects → Tasks → Subtasks
  • Progress Tracking: Monitor completion status at all levels
  • Project-Specific Storage: Each working directory has isolated task data
  • Git-Trackable: Task data can be committed alongside your code

🧠 Agent Memories System

  • Persistent Memory: Store and retrieve agent memories with titles and detailed content
  • Intelligent Search: Multi-field text search with relevance scoring across titles, content, and categories
  • Smart Ranking: Advanced scoring algorithm prioritizes title matches (60%), content matches (30%), and category bonuses (20%)
  • Rich Metadata: Flexible metadata system for enhanced context
  • JSON Storage: Individual JSON files organized by category, named after memory titles
  • Project-Specific: Isolated memory storage per working directory

🔧 MCP Tools Available

Project Management

  • list_projects - View all projects in a working directory
  • create_project - Create a new project in a working directory
  • get_project - Get detailed project information
  • update_project - Edit project name/description
  • delete_project - Delete project and all associated data

Task Management

  • list_tasks - View tasks (optionally filtered by project)
  • create_task - Create a new task within a project
  • get_task - Get detailed task information
  • update_task - Edit task details or mark as completed
  • delete_task - Delete task and all associated subtasks

Subtask Management

  • list_subtasks - View subtasks (filtered by task or project)
  • create_subtask - Create a new subtask within a task
  • get_subtask - Get detailed subtask information
  • update_subtask - Edit subtask details or mark as completed
  • delete_subtask - Delete a specific subtask

Agent Memory Management

  • create_memory - Store new memories with title and detailed content
  • search_memories - Find memories using intelligent multi-field search with relevance scoring
  • get_memory - Get detailed memory information
  • list_memories - List memories with optional filtering
  • update_memory - Edit memory title, content, metadata, or categorization
  • delete_memory - Delete a memory (requires confirmation)

Important: All tools require a workingDirectory parameter to specify where the data should be stored. This enables project-specific task and memory management.

Installation

Quick Start

npx -y @pimzino/agentic-tools-mcp

Global Installation

npm install -g @pimzino/agentic-tools-mcp

Usage

With Claude Desktop

Add to your Claude Desktop configuration:

{
  "mcpServers": {
    "agentic-tools": {
      "command": "npx",
      "args": ["-y", "@pimzino/agentic-tools-mcp"]
    }
  }
}

Note: The server now includes both task management and agent memories features.

With AugmentCode

  1. Open Augment Settings Panel (gear icon)
  2. Add MCP server:
    • Name: agentic-tools
    • Command: npx -y @pimzino/agentic-tools-mcp
  3. Restart VS Code

Features Available: Task management, agent memories, and text-based search capabilities.

With Other MCP Clients

The server uses STDIO transport and can be integrated with any MCP-compatible client:

npx -y @pimzino/agentic-tools-mcp

Data Models

Project

{
  id: string;           // Unique identifier
  name: string;         // Project name
  description: string;  // Project overview
  createdAt: string;    // ISO timestamp
  updatedAt: string;    // ISO timestamp
}

Task

{
  id: string;           // Unique identifier
  name: string;         // Task name
  details: string;      // Enhanced description
  projectId: string;    // Parent project reference
  completed: boolean;   // Completion status
  createdAt: string;    // ISO timestamp
  updatedAt: string;    // ISO timestamp
}

Subtask

{
  id: string;           // Unique identifier
  name: string;         // Subtask name
  details: string;      // Enhanced description
  taskId: string;       // Parent task reference
  projectId: string;    // Parent project reference
  completed: boolean;   // Completion status
  createdAt: string;    // ISO timestamp
  updatedAt: string;    // ISO timestamp
}

Memory

{
  id: string;                    // Unique identifier
  title: string;                 // Short title for file naming (max 50 characters)
  content: string;               // Detailed memory content/text (no limit)
  metadata: Record<string, any>; // Flexible metadata object
  createdAt: string;            // ISO timestamp
  updatedAt: string;            // ISO timestamp
  category?: string;            // Optional categorization
}

Example Workflow

  1. Create a Project

    Use create_project with:
    - workingDirectory="/path/to/your/project"
    - name="Website Redesign"
    - description="Complete overhaul of company website"
    
  2. Add Tasks

    Use create_task with:
    - workingDirectory="/path/to/your/project"
    - name="Design mockups"
    - details="Create wireframes and high-fidelity designs"
    - projectId="[project-id-from-step-1]"
    
  3. Break Down Tasks

    Use create_subtask with:
    - workingDirectory="/path/to/your/project"
    - name="Create wireframes"
    - details="Sketch basic layout structure"
    - taskId="[task-id-from-step-2]"
    
  4. Track Progress

    Use update_task and update_subtask to mark items as completed
    Use list_projects, list_tasks, and list_subtasks to view progress
    (All with workingDirectory parameter)
    

Agent Memories Workflow

  1. Create a Memory

    Use create_memory with:
    - workingDirectory="/path/to/your/project"
    - title="User prefers concise technical responses"
    - content="The user has explicitly stated they prefer concise responses with technical explanations. They value brevity but want detailed technical information when relevant."
    - metadata={"source": "conversation", "confidence": 0.9}
    - category="user_preferences"
    
  2. Search Memories

    Use search_memories with:
    - workingDirectory="/path/to/your/project"
    - query="user preferences responses"
    - limit=5
    - threshold=0.3
    - category="user_preferences"
    
  3. List and Manage

    Use list_memories to view all memories
    Use update_memory to modify existing memories (title, content, metadata, category)
    Use delete_memory to remove outdated memories
    (All with workingDirectory parameter)
    

📖 Quick Start: See docs/QUICK_START_MEMORIES.md for a step-by-step guide to agent memories.

Data Storage

  • Project-specific: Each working directory has its own isolated task and memory data
  • File-based: Task data stored in .agentic-tools-mcp/tasks/, memory data in .agentic-tools-mcp/memories/
  • Git-trackable: All data can be committed alongside your project code
  • Persistent: All data persists between server restarts
  • Atomic: All operations are atomic to prevent data corruption
  • JSON Storage: Simple file-based storage for efficient memory organization
  • Backup-friendly: Simple file-based storage for easy backup and migration

Storage Structure

your-project/
├── .agentic-tools-mcp/
│   ├── tasks/              # Task management data for this project
│   │   └── tasks.json      # Projects, tasks, and subtasks data
│   └── memories/           # JSON file storage for memories
│       ├── preferences/    # User preferences category
│       │   └── User_prefers_concise_technical_responses.json
│       ├── technical/      # Technical information category
│       │   └── React_TypeScript_project_with_strict_ESLint.json
│       └── context/        # Context information category
│           └── User_works_in_healthcare_needs_HIPAA_compliance.json
├── src/
├── package.json
└── README.md

Working Directory Parameter

All MCP tools require a workingDirectory parameter that specifies:

  • Where to store the .agentic-tools-mcp/ folder
  • Which project's task and memory data to access
  • Enables multiple projects to have separate task lists and memory stores

Benefits of Project-Specific Storage

  • Git Integration: Task and memory data can be committed with your code
  • Team Collaboration: Share task lists and agent memories via version control
  • Project Isolation: Each project has its own task management and memory system
  • Multi-Project Workflow: Work on multiple projects simultaneously with isolated memories
  • Backup & Migration: File-based storage travels with your code
  • Text Search: Simple content-based memory search for intelligent context retrieval
  • Agent Continuity: Persistent agent memories across sessions and deployments

Error Handling

  • Validation: All inputs are validated with comprehensive error messages
  • Directory Validation: Ensures working directory exists and is accessible
  • Referential Integrity: Prevents orphaned tasks/subtasks with cascade deletes
  • Unique Names: Enforces unique names within scope (project/task)
  • Confirmation: Destructive operations require explicit confirmation
  • Graceful Degradation: Detailed error messages for troubleshooting
  • Storage Errors: Clear messages when storage initialization fails

Development

Building from Source

git clone <repository>
cd agentic-tools-mcp
npm install
npm run build
npm start

Project Structure

src/
├── features/
│   ├── task-management/
│   │   ├── tools/           # MCP tool implementations
│   │   │   ├── projects/    # Project CRUD operations
│   │   │   ├── tasks/       # Task CRUD operations
│   │   │   └── subtasks/    # Subtask CRUD operations
│   │   ├── models/          # TypeScript interfaces
│   │   └── storage/         # Data persistence layer
│   └── agent-memories/
│       ├── tools/           # Memory MCP tool implementations
│       │   └── memories/    # Memory CRUD operations
│       ├── models/          # Memory TypeScript interfaces
│       └── storage/         # JSON file storage implementation
├── server.ts            # MCP server configuration
└── index.ts             # Entry point

Troubleshooting

Common Issues

"Working directory does not exist"

  • Ensure the path exists and is accessible
  • Use absolute paths for reliability
  • Check directory permissions

"Text search returns no results" (Agent Memories)

  • Try using different keywords or phrases
  • Check that memories contain the search terms
  • Verify that the query content matches memory content

"Memory files not found" (Agent Memories)

  • Ensure the working directory exists and is writable
  • Check that the .agentic-tools-mcp/memories directory was created

Version History

See CHANGELOG.md for detailed version history and release notes.

Current Version: 1.4.0

  • ✅ Complete task management system
  • ✅ Agent memories with title/content architecture and JSON file storage
  • ✅ Intelligent multi-field search with relevance scoring
  • ✅ Cross-platform file path handling
  • ✅ Project-specific storage with comprehensive MCP tools
  • ✅ Simplified schema with enhanced documentation

Acknowledgments

We're grateful to the open-source community and the following projects that make this MCP server possible:

Core Technologies

Development & Validation

  • Zod - TypeScript-first schema validation for robust input handling
  • ESLint - Code quality and consistency
  • Prettier - Code formatting

File Storage & Search

  • JSON - Simple, human-readable data format for memory storage
  • Text Search - Efficient content-based search across memory files

Special Thanks

  • Open Source Community - For creating the tools and libraries that make this project possible

License

MIT License - see LICENSE file for details.

Contributing

Contributions are welcome! Please feel free to submit issues and pull requests.

Development Setup

git clone <repository>
cd agentic-tools-mcp
npm install
npm run build
npm start

Support

For issues and questions, please use the GitHub issue tracker.

Documentation

Getting Help

  • 🐛 Report bugs via GitHub issues
  • 💡 Request features via GitHub discussions

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured