mcp-task-manager
MCP server that wraps a personal task manager REST API, enabling Claude to read and manage tasks via tools like get_tasks and add_task.
README
mcp-task-manager
MCP (Model Context Protocol) server that wraps the personal task manager REST API, so Claude (Claude Code / Cowork / claude.ai) can read and manage tasks.
Two transports, same tools:
- stdio (
dist/index.js) — for local Claude Code on the server - streamable HTTP (
api/mcp.ts) — serverless function for Vercel, endpoint/mcp
Tools
get_categories, get_tasks, get_task, add_task, add_subtask, update_task, complete_task, reopen_task, delete_task
Field conventions: priority/effort ∈ Low|Medium|High; due_date = YYYY-MM-DD; reminder_at = YYYY-MM-DDTHH:MM (server local time, triggers a Telegram message).
Environment variables
| Variable | Value |
|---|---|
TASKS_API_URL |
Base URL of the task manager API, e.g. https://<tunnel>.trycloudflare.com/api. Defaults to http://localhost:3131/api. |
TASKS_API_KEY |
API key; sent as Authorization: Bearer <key> on every call. |
Local build & stdio registration
npm install
npm run build # tsc → dist/
Claude Code config (~/.claude.json → mcpServers):
{
"mcpServers": {
"task-manager": {
"command": "node",
"args": ["/home/zsomb/Scripts/Personal/mcp-task-manager/dist/index.js"],
"env": { "TASKS_API_KEY": "<key from task-manager/.env>" }
}
}
}
Deploy to Vercel
-
Push this repo to GitHub:
git remote add origin git@github.com:<you>/mcp-task-manager.git git push -u origin main -
On vercel.com: Add New → Project → Import the GitHub repo. Framework preset: Other. No build settings needed (functions compile automatically).
-
Project → Settings → Environment Variables, add for Production:
TASKS_API_URL=https://<tunnel>.trycloudflare.com/apiTASKS_API_KEY= the key from the task manager.env
-
Deploy. The MCP endpoint will be:
https://<project-name>.vercel.app/mcp(
vercel.jsonrewrites/mcp→ theapi/mcpfunction; stateless streamable HTTP, JSON responses.)
⚠️ The trycloudflare quick-tunnel URL changes every time the tunnel restarts — after a server reboot, run tunnel-url on the server and update TASKS_API_URL in Vercel (then redeploy).
Recommended Servers
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.
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.
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.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
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.
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.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
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.