About MCP Task Manager Server
MCP Task Manager Server is an MCP server and task-management example for AI assistants and developers. It offers task tools over stdio or an HTTP API, with in-memory storage and an extensible tool structure.
Key features
- 01Create, list, and complete tasks
- 02Filter tasks by status
- 03MCP stdio and HTTP interfaces
- 04In-memory task storage
- 05Extensible tool registry
Use cases
- 01Manage tasks through an MCP-compatible assistant
- 02Expose task operations to a web application
- 03Use as a template for adding MCP tools
MCP support
Exposes task creation, listing, and completion tools to MCP clients over stdio. The same task operations are also available through an HTTP API.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README🔌 MCP Tool Server - AI Agent Toolkit
A powerful and extensible Model Context Protocol (MCP) server that enables AI agents to interact with external tools and services. This implementation provides a task management system that demonstrates how to build and deploy MCP-compatible tools for AI assistants.
🌟 What is MCP?
The Model Context Protocol (MCP) is a standard that allows AI models to interact with external tools, data sources, and services. This server implements the MCP specification, enabling AI assistants like Claude and GPT to execute real-world actions through a standardized interface.
✨ Features
- MCP-Compatible Tools: Ready-to-use tools for AI assistants
- Task Management System: Create, list, and complete tasks
- Dual Interface: Works with both MCP stdio mode and HTTP API
- Extensible Architecture: Easily add new tools and capabilities
- Developer-Friendly: Clear documentation and examples
- Lightweight: In-memory storage for quick setup and testing
🛠️ Available Tools
1. create-task
Creates a new task with a title and description.
Parameters:
title: String (required) - The title of the taskdescription: String (required) - The description of the task
2. list-tasks
Lists all tasks currently stored in memory.
Parameters:
status: String (optional) - Filter by status: "all", "pending", or "completed"
3. pending-tasks
Lists all pending tasks.
Parameters: None
4. complete-task
Marks a specific task as completed.
Parameters:
id: String (required) - The ID of the task to mark as completed
🚀 Getting Started
Prerequisites
- Node.js (v18 or later)
- npm or yarn
Installation
- Clone the repository:
git clone https://github.com/yourusername/mcp-server.git
cd mcp-server
- Install dependencies:
npm install
- Build the TypeScript code:
npm run build
🏃♂️ Running the Server
MCP Mode (for AI Assistants)
npm start
This runs the server in stdio mode, making it compatible with MCP clients like Claude for Desktop.
HTTP Mode (for Web Applications)
npm run http
The HTTP server runs on port 3000 by default. You can access it at http://localhost:3000.
Customize the port using the PORT environment variable:
PORT=8080 npm run http
🌐 HTTP API Endpoints
Create a Task
POST /api/tasks
Request body:
{
"title": "Task title",
"description": "Task description"
}
List All Tasks
GET /api/tasks?status=[all|pending|completed]
List Pending Tasks
GET /api/tasks/pending
Complete a Task
PATCH /api/tasks/:id/complete
Execute MCP Tool Directly
POST /api/mcp/execute
Request body:
{
"tool": "tool-name",
"params": {
"param1": "value1",
"param2": "value2"
}
}
🔮 Building Your Own MCP Tools
This server provides a template for creating your own MCP-compatible tools. To add a new tool:
- Define your tool in the
src/toolsdirectory - Register it in the tool registry
- Implement the necessary logic
- Update the HTTP API if needed
Check the existing tools for examples of how to structure your implementations.
🧪 Testing with AI Assistants
- Start the server in MCP mode:
npm start - Connect to the server using an MCP-compatible AI assistant
- The AI can now use the available tools to manage tasks:
- Create a task:
create-taskwith title and description - List all tasks:
list-tasks - Complete a task:
complete-taskwith the task ID
- Create a task:
🔄 Integration with Web Clients
This server pairs perfectly with the agent-client-example project, which provides a web interface for interacting with AI assistants and MCP tools.
📋 Future Enhancements
- Persistent storage options (MongoDB, PostgreSQL)
- Authentication and authorization
- Additional tool categories (file management, web search, etc.)
- WebSocket support for real-time updates
- Tool execution metrics and logging
📄 License
MIT
Empowering AI agents with real-world capabilities 🤖✨
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.