TinyTasks

Provides task management via MCP endpoints for Claude Desktop and Claude Web, including status, stats, listing, creation, updates, toggling, and deletion.
  • javascript

0

GitHub Stars

javascript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

TinyTasks MCP Server is a hybrid MCP server that works with both Claude Desktop and Claude Web. It exposes eight built-in tools to manage tasks, and you can run it locally for desktop usage or deploy it publicly for Claude Web integration.

How to use

You can interact with TinyTasks MCP Server through an MCP client by connecting to either your local instance or a public deployment. The server exposes eight tools that let you check API status, view task statistics, list tasks with filters, create and update tasks, toggle their state, and delete tasks.

How to install

Prerequisites: Node.js and a supported MCP client. If you plan to run the server locally for Claude Desktop, you will configure Claude Desktop to point to the local MCP instance. If you plan to deploy for Claude Web, you will publish a REST API endpoint that the client can reach.

Local (Claude Desktop) setup are the following steps.

# 1) Prepare and run locally with Node
node index.js

Web deployment can be done using Railway or Vercel. Follow the deployment flow to publish a public URL and then configure your MCP client to point to that URL.

# Railway deployment flow (example commands)
npm i -g @railway/cli
railway login
railway init
railway up
railway variables set WEB_MODE=true
railway status
# Vercel deployment flow (example commands)
npm i -g vercel
vercel --prod

Additional content

Configuration notes: Claude Desktop usage requires a local MCP server command configured under your Claude Desktop setup, while Claude Web usage requires a publicly accessible URL. The same API powers both modes.

Notes on usage and endpoints

Endpoints available when the server is deployed publicly include a root information endpoint, an endpoint listing all tools, and an execute endpoint to run a selected tool.

Available tools

get_api_status

Returns the current status of the API, including health and basic metadata.

get_tasks_stats

Provides statistical data about tasks, such as counts by status or priority.

list_tasks

Lists tasks with support for filters to narrow results by properties like status, priority, and created date.

get_task

Fetches a specific task by its identifier, returning full task details.

create_task

Creates a new task with given attributes such as title and priority.

update_task

Updates properties of an existing task, including title, priority, and status.

toggle_task

Toggles the active state or other binary properties of a task.

delete_task

Removes a task from the system by its identifier.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational