Claudia MCP server

Read from the package source without running it. The installed server may list more.

• display_kanban

  Display tasks in a Kanban board format with columns for each status.

• display_legend

  Display the legend for status icons, priority indicators, and task types.

• display_progress

  Display project progress summary with charts and statistics.

• display_sprint

  Display a sprint as a detailed card with task breakdown and progress.

• display_sprints

  Display all sprints in a formatted list with progress indicators.

• display_task

  Display a single task as a detailed card with all information.

• display_tasks

  Display tasks in a formatted CLI table view. Great for visual overview of task status.

• project_createwrite action

  Create a new project. Projects group tasks and sprints together.

• project_current

  Get the currently selected project. If no project is selected, returns null with a list of available projects.

• project_deletewrite action

  Delete a project. Tasks and sprints in the project are orphaned (project_id set to null).

• project_list

  List all projects.

• project_read

  Get project details by ID.

• project_select

  Select a project as the current working project. Subsequent task/sprint operations will be scoped to this project.

• project_updatewrite action

  Update project properties.

• sprint_activate

  Set a sprint as the active sprint.

• sprint_createwrite action

  Create a new sprint with optional date range.

• sprint_deletewrite action

  Delete a sprint (tasks are unassigned, not deleted).

• sprint_list

  List all sprints with status and task counts.

• sprint_show

  Get sprint details with associated tasks.

• sprint_updatewrite action

  Update sprint properties.

• task_abandon

  Abandon a task and return it to pending status. Use when you cannot complete a task and need to release it. A reason is required and will be recorded in the task context. The task becomes available for other agents to claim.

• task_blocked

  List tasks with unsatisfied dependencies.

• task_claim

  CRITICAL: Use this when starting work on a task. Atomically claims the task AND automatically transitions it to 'in_progress'. You MUST call this before working on any task. Returns success status and the updated task.

• task_context_get

  Retrieve stored agent context from a task.

• task_context_merge

  Merge context into existing task context (deep merge). Max 64KB total.

• task_context_set

  Store agent context/memory on a task (overwrites existing). Max 64KB.

• task_createwrite action

  Create a new task with optional parent, priority, acceptance criteria, and metadata. Returns the created task.

• task_create_manywrite action

  Create multiple tasks atomically (max 100). Returns array of created tasks.

• task_deletewrite action

  Delete a task by ID. Children are orphaned (parent_id set to null).

• task_dependencies

  Get dependencies and dependents for a task.

• task_dependency_add

  Add a dependency between tasks (task depends on another).

• task_dependency_removewrite action

  Remove a dependency between tasks.

• task_finish

  RECOMMENDED: Complete a task you're working on. This is the preferred way to mark a task as done. Optionally provide a completion summary. Use this instead of: task_transition(id, "completed") The task must be in_progress and claimed by you. Returns the completed task.

• task_handoff

  Hand off a task to another agent. Transfers ownership of the task while preserving its current status. Optionally include notes for the receiving agent. Handoff history is recorded in the task context.

• task_list

  Query tasks with filtering, sorting, and pagination. Returns array of tasks.

• task_read

  Retrieve a single task by ID with full details including context and metadata.

• task_ready

  List tasks ready to work on (all dependencies satisfied).

• task_release

  Release a claimed task. Only succeeds if task is claimed by the specified agent.

• task_start

  RECOMMENDED: Create a new task AND immediately start working on it. This is the preferred way to create tasks you'll work on right away. Automatically sets status to "in_progress" and claims the task for you. Use this instead of: task_create + task_claim Returns the created task (already in_progress).

• task_transition

  Change task status with workflow validation. IMPORTANT: Use this to mark task as 'completed' when you finish working on it. Returns the updated task and transition details.

• task_transition_many

  Transition multiple tasks to a new status with validation.

• task_tree

  Get hierarchical view of task and all descendants.

• task_updatewrite action

  Update one or more fields on an existing task. Returns the updated task.

• task_update_manywrite action

  Update multiple tasks with the same changes.

• task_verification_status

  Get verification status for a task's acceptance criteria. Returns all criteria with their verification status and overall progress.

• task_verify

  VERIFY: Mark an acceptance criterion as verified with optional evidence. Use this to record that you've verified a specific acceptance criterion on a task. Returns the updated criterion and overall verification progress. Criterion IDs are like 'ac-1', 'ac-2', etc. Use task_verification_status to see all criteria.

• task_workspace

  SESSION CONTEXT: Call this when starting a new session to understand your workspace. Returns: - Your session agent ID - Tasks currently in_progress (yours and orphaned) - Pending tasks ready to work on - Suggested next actions - Current project context This helps you resume work or pick up where another session left off.

• workflow_info

  WORKFLOW REFERENCE: PREFERRED: Use compound operations (task_start, task_finish) - they handle workflow automatically. ALTERNATIVE: If using separate operations: 1. STARTING WORK: Call task_claim first → auto-moves to "in_progress" 2. FINISHING WORK: Call task_transition(id, "completed") Note: Any mutation to a pending task now auto-claims it (implicit workflow). Returns the current workflow rules

• Code scan27 source files scanned13/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 215 days ago4/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

57/100

higher than 10% of 1,299 Productivity servers

Tools

48

the typical Productivity server has 7

Tools that change things

25%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

15

more than 81% of 854 Productivity servers

Downloads a week

43

more than 31% of 427 Productivity servers with a package

Claudia: common questions

Is Claudia MCP server safe?

With care: it is graded C, so read the findings first (57/100). Read the Claudia safety report

How do I install Claudia?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Claudia need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Claudia maintained?

The last commit was 249 days ago (2026-02-28). The latest release is v0.1.3.

What can I use instead of Claudia?

Servers from other publishers that do the same job: Agent Tasks MCP server.

How does Claudia compare with other Productivity MCP servers?

safety score 57/100 (higher than 10% of 1,299 Productivity servers); tools 48 (the typical Productivity server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.