npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@claydiffrient/repo-tasks-mcp-server

v0.1.2

Published

MCP server for repo-tasks task management

Readme

repo-tasks MCP Server

Model Context Protocol (MCP) server for repo-tasks task management. This server allows LLMs like Claude to interact with your tasks through natural language.

Features

The MCP server exposes all repo-tasks functionality through MCP tools:

Task Management

  • list_tasks - List tasks by status, priority, or tag
  • show_task - Display detailed task information
  • create_task - Create new tasks with title, priority, tags, and notes
  • update_task - Update existing task properties
  • move_task - Move tasks between statuses
  • start_task - Begin work on a task (move to in-progress + create git branch)

Search & Discovery

  • search_tasks - Full-text search across all tasks with regex support

Version Control

  • save_tasks - Commit task changes to git

Editor Integration

  • open_task - Open task in default editor

Installation

From npm (Recommended)

Install the MCP server globally:

npm install -g @claydiffrient/repo-tasks-mcp-server

This will make the repo-tasks-mcp command available in your PATH.

Prerequisites

The MCP server requires the repo-tasks CLI to be installed. Install it using one of these methods:

# Homebrew (macOS/Linux)
brew install claydiffrient/tap/repo-tasks

# Cargo (all platforms)
cargo install repo-tasks

# From source
git clone https://github.com/claydiffrient/repo-tasks.git
cd repo-tasks
cargo install --path .

Note: Node.js v18 or later is required for the MCP server.

From Source (Development)

If you want to build from source or contribute:

  1. Clone the repository:

    git clone https://github.com/claydiffrient/repo-tasks.git
    cd repo-tasks/mcp-server
  2. Install dependencies:

    npm install
  3. Build the TypeScript code:

    npm run build
  4. Test the server:

    node dist/index.js

Configuration

Claude Code

Add to your Claude Code MCP settings (~/.config/claude-code/mcp_settings.json):

If installed via npm:

{
  "mcpServers": {
    "repo-tasks": {
      "command": "repo-tasks-mcp"
    }
  }
}

If running from source:

{
  "mcpServers": {
    "repo-tasks": {
      "command": "node",
      "args": [
        "/absolute/path/to/repo-tasks/mcp-server/dist/index.js"
      ]
    }
  }
}

Replace /absolute/path/to/repo-tasks with the actual path to your repo-tasks repository.

After adding the configuration, restart Claude Code or reload the MCP servers.

Claude Desktop

The server also works with Claude Desktop. Add to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS:

If installed via npm:

{
  "mcpServers": {
    "repo-tasks": {
      "command": "repo-tasks-mcp"
    }
  }
}

If running from source:

{
  "mcpServers": {
    "repo-tasks": {
      "command": "node",
      "args": [
        "/absolute/path/to/repo-tasks/mcp-server/dist/index.js"
      ]
    }
  }
}

Other MCP Clients

The server uses stdio transport and follows the standard MCP protocol. Configure your MCP client to run:

If installed via npm:

repo-tasks-mcp

If running from source:

node /path/to/mcp-server/dist/index.js

Usage Examples

Once configured, you can interact with repo-tasks through natural language in Claude Code:

Creating Tasks

Create a new high priority task titled "Add user authentication" with tags "security,backend"

Listing and Searching

Show me all tasks in the todo status

Search for tasks related to "authentication"

List all high priority tasks

Working on Tasks

Start working on task 20260110184347

Move task create-start-command to testing

Show details for task 20260110201217

Version Control

Save all task changes with message "Update sprint tasks"

Tool Reference

list_tasks

List tasks with optional filters.

Parameters:

  • status (string, optional): Filter by status (todo, in-progress, testing, done). Default: "todo"
  • priority (string, optional): Filter by priority (Low, Medium, High, Critical)
  • tag (string, optional): Filter by tag

Example:

{
  "status": "in-progress",
  "priority": "High"
}

show_task

Show detailed information about a specific task.

Parameters:

  • task_id (string, required): Task ID or slug

Example:

{
  "task_id": "20260110184347"
}

create_task

Create a new task.

Parameters:

  • title (string, required): Task title
  • priority (string, optional): Priority level. Default: "Medium"
  • tags (string, optional): Comma-separated tags
  • notes (string, optional): Task description/notes

Example:

{
  "title": "Implement user authentication",
  "priority": "High",
  "tags": "security,backend",
  "notes": "Add JWT-based authentication system"
}

update_task

Update task properties (interactive).

Parameters:

  • task_id (string, required): Task ID or slug

move_task

Move a task to a different status.

Parameters:

  • task_id (string, required): Task ID or slug
  • new_status (string, required): New status (todo, in-progress, testing, done)

Example:

{
  "task_id": "20260110184347",
  "new_status": "testing"
}

start_task

Start working on a task (recommended for beginning work).

Moves the task to in-progress and creates a git branch with format {id}-{slug}.

Parameters:

  • task_id (string, required): Task ID or slug

Example:

{
  "task_id": "20260110184347"
}

search_tasks

Search tasks by content.

Parameters:

  • query (string, required): Search query (regex supported)

Example:

{
  "query": "authentication"
}

save_tasks

Commit task changes to git.

Parameters:

  • message (string, optional): Commit message (auto-generated if not provided)

Example:

{
  "message": "Update sprint tasks"
}

open_task

Open a task in the default editor.

Parameters:

  • task_id (string, required): Task ID or slug

Development

Watch Mode

Run TypeScript compiler in watch mode:

npm run watch

Testing

Test the server manually using the MCP inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Troubleshooting

"repo-tasks binary not found"

The server looks for the repo-tasks binary in:

  1. System PATH
  2. ./target/release/repo-tasks (local release build)
  3. ./target/debug/repo-tasks (local debug build)

Ensure repo-tasks is installed or built from source.

Changes not reflected

After modifying the TypeScript code, rebuild:

npm run build

Then restart Claude Code to reload the MCP server.

Server not showing in Claude

  1. Check the configuration file path (~/.config/claude-code/mcp_settings.json)
  2. Verify the absolute path to dist/index.js is correct
  3. Check Claude Code logs for errors
  4. Restart Claude Code after configuration changes

License

Same as repo-tasks: MIT OR Apache-2.0