Taskr

AI-native task management for Claude Code and MCP-compatible agents.

---

Why Taskr?

Stop paying for SaaS to manage your projects with teams. No more Jira. No more Asana. No more Linear. Just use Taskr (free) and GitHub Projects/Issues (also free).

The magic? Your code and your tasks live together in the same place. GitHub becomes your single source of truth—perfect for open-source projects, closed-source projects, or anything in between. AI loves when all the data lives in one place, and so will your team.

Taskr automates Claude Code to create plans in GitHub, then update and follow those plans like a real software development team. Just say:

> "use taskr triage to ______"

...and whatever you need to get done, that's it. Taskr will set up the plan.

If Claude ever stops mid-task? Just say "use taskr triage" again. Triage is designed to figure out where your project left off, keep the backlog clean, keep the project organized, and more.

While this is just the start of what Taskr can do for teams, it's enough to double or triple your Claude Code output starting today.

It's a low-opinionated way to keep projects organized using the best coding agent in the world—Claude Code—without getting in Claude's way. Use Claude Code how you love to use it, but invoke taskr triage whenever you need to make sure Claude is following the plan.

Taskr Building Taskr

We use Taskr to build Taskr. Here's what it looks like:

GitHub Projects kanban—tasks move from Todo → In Progress → Done

GitHub Issues with labels—all managed by Claude Code via Taskr

---

Taskr Learns Over Time

The secret sauce? Devlogs.

Every time Claude makes a decision, fixes a bug, or learns something about your codebase, Taskr records it. These aren't just logs—they're persistent AI memory that survives across sessions, context windows, and even different Claude instances.

This means:

• 🧠 Claude remembers what worked (and what didn't) in your codebase
• 🔍 Searchable history of every architectural decision, bugfix, and pattern
• 📚 Institutional knowledge that doesn't walk out the door when a session ends
• ⚡ Faster ramp-up when Claude starts a new session—it can search devlogs first

Coming Soon: Deep Sleep with taskr-worker

For pro teams, we're building taskr-worker—a background service that runs during off-hours to:

• 🌙 Consolidate memory - Summarize and compress devlogs while preserving key insights
• 🧹 Trim what doesn't matter - Automatically archive stale or low-value entries
• 🔗 Build connections - Link related devlogs, issues, and decisions together
• 📈 Improve over time - The more you use Taskr, the smarter it gets

More details coming soon. For now, devlogs alone will transform how Claude Code works on your projects.

---

Features

• Task Management - Create, track, and search tasks with full CRUD operations
• Development Logs - Persistent AI memory across sessions (decisions, bugfixes, patterns)
• Agent Sessions - Coordinate multi-agent work with handoffs and work claiming
• GitHub Integration - Projects V2, issues, and PRs built-in (no plugin needed)
• Dual Database Support - PostgreSQL for teams, SQLite for local use
• Plugin Architecture - Extend with Skillflows, Supabase, and custom integrations

Quick Start

Local Setup (SQLite - Zero Config)

pip install taskr-mcp
taskr-mcp

Add to your Claude Code MCP config (~/.claude/claude_code_config.json):

{
  "mcpServers": {
    "taskr": {
      "command": "taskr-mcp",
      "env": {
        "GITHUB_TOKEN": "your-github-token"
      }
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your-github-token"
      }
    }
  }
}

> Note: Create a GitHub Personal Access Token with repo and project scopes. Use the same token for both servers. > > Why both? GitHub MCP cannot manage Projects V2 (no create/read/update/delete). Since GitHub Projects are now org-level (not repo-level), taskr provides the missing project CRUD. GitHub MCP handles repo operations (issues, PRs, search, comments).

Team Setup (PostgreSQL)

pip install taskr-mcp

# Configure database
export TASKR_DATABASE_URL="postgresql://user:pass@host:5432/taskr"

# Run migrations
taskr-mcp migrate

# Start server
taskr-mcp

Configuration

Create ~/.taskr/config.yaml:

database:
  type: sqlite  # or "postgres"
  sqlite:
    path: ~/.taskr/taskr.db
  postgres:
    url_env: TASKR_DATABASE_URL

identity:
  author: your-name
  agent_id: claude-code

plugins:
  enabled:
    - github

Core Tools

Task Management

• taskr_list - List tasks with filters
• taskr_create - Create new task
• taskr_show - Show task details
• taskr_update - Update task
• taskr_search - Search tasks
• taskr_assign - Assign to user
• taskr_close - Mark complete

Development Logs (AI Memory)

• devlog_add - Create log entry
• devlog_list - List entries
• devlog_search - Full-text search
• devlog_get - Get full content

Agent Sessions

• session_start - Start session with context
• session_end - End with handoff notes
• claim_work - Atomically claim work item
• release_work - Release claimed work
• what_changed - See recent changes

SQL Tools

• taskr_sql_query - Execute ad-hoc SQL queries
• taskr_sql_explain - Analyze query performance
• taskr_sql_migrate - Run SQL with audit logging

GitHub Projects V2 (GitHub MCP can't do this)

GitHub MCP has no project management capabilities. Since Projects V2 are org-level (not repo-level), taskr provides the missing CRUD:

• github_project_create - Create a new Project V2
• github_project_items - List project items with minimal output
• github_project_add_item - Add issue/PR to project
• github_project_close / github_project_reopen - Archive/restore projects
• github_create_issue_in_project - Create issue AND link to project atomically
• github_pr_create - Create PR with smart issue linking (auto-adds to project)
• github_get_issue_id / github_get_org_id - Get node IDs for API calls

> Note: Use GitHub MCP (mcp__github__*) for repo-level operations: reading issues, searching, commenting, listing PRs, etc.

Utility

• taskr_triage - Workflow guidance
• taskr_health - Database health check
• taskr_migrate - Run pending migrations

Plugins

Install optional plugins for extended functionality:

# Workflow definitions
pip install taskr-plugin-skillflows

# Supabase deployments
pip install taskr-plugin-supabase

Enable in config:

plugins:
  enabled:
    - skillflows

Development

# Clone
git clone https://github.com/rhea-impact/taskr.git
cd taskr

# Install in dev mode
pip install -e packages/taskr-core
pip install -e packages/taskr-mcp

# Run tests
pytest tests/

License

MIT License - see [LICENSE](LICENSE)

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: rhea-impact
• Source: rhea-impact/taskr
• License: MIT

Install and usage instructions live in the source repository linked above.