task

This MCP server provides two runtime interfaces for managing tasks via the MCP protocol. The STDIO mode lets you interact with the server through command-line or AI agents using a streaming stdin/stdout transport, while the HTTP+SSE mode exposes a web-friendly endpoint that clients can connect to via Server-Sent Events. Core capabilities include listing tasks, creating new tasks with customizable fields, updating task properties (description, status, category, priority), and deleting tasks when appropriate. The included example client code demonstrates how to connect with both STDIO and HTTP transports and how to invoke tools such as listTasks, createTask, updateTask, and deleteTask to manage tasks programmatically.

Prerequisites:

• Node.js 16.x or higher
• npm or pnpm

1. Clone the repository

git clone https://github.com/yourusername/milkosten-task-mcp-server.git
cd milkosten-task-mcp-server

2. Install dependencies

npm install

or

pnpm install

3. Create an environment file or set environment variables

# .env (example)
TASK_MANAGER_API_BASE_URL=https://your-task-api-url.com/api
TASK_MANAGER_API_KEY=your_api_key_here
TASK_MANAGER_HTTP_PORT=3000

4. Build the project

npm run build

5. Run the server (choose mode)

• STDIO mode:

npm start

(or

node dist/index.js
```) 

- HTTP+SSE mode:

npm run start:http

(or

node dist/http-server.js

6) Verify by connecting a client via the respective transport (STDIO or HTTP SSE) and invoking task tools.

Notes and tips:

• Ensure your external Task API credentials are correctly configured in environment variables. The server relies on TASK_MANAGER_API_BASE_URL and TASK_MANAGER_API_KEY to communicate with the Task API.
• The HTTP server defaults to port 3000 but can be overridden with TASK_MANAGER_HTTP_PORT or an equivalent PORT variable. If you run both modes simultaneously, ensure distinct ports or separate environments to avoid conflicts.
• The README describes available tools (listTasks, createTask, updateTask, deleteTask). When using the STDIO client, you’ll typically connect via a StdioClientTransport and then call these tools with the appropriate arguments.
• If you encounter build-time or runtime errors, start with npm run build, then inspect dist/ logs for details. The MCP SDK integration can emit detailed validation messages for incorrect tool arguments.
• In development, you can run tests with npm test to verify behavior end-to-end; the test suite will build, start the server, run a test client, and shut down automatically.