karea-mcp (starecz/karea-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 49 tools. No publisher has claimed this listing.
MCP server for Karea task management, enabling creation, editing, closing, and linking tasks with 44 tools from Claude Code and other MCP clients.
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
starecz
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
karea_list_projectsList all Karea projects with their IDs
karea_list_tasksList tasks in a project. Defaults to open tasks (open, in_progress, blocked, review, backlog) capped at 200 to keep responses small. To see closed tasks pass status="done" and optionally closedSince (e.g. "14d", "7d", "24h"). To list everything, pass status="all".
karea_create_taskCreate a new task in a project and return it with its visual ID (e.g. KA42), status, priority and category. Defaults when omitted: status open, priority 3, the first category of the project. Use karea_quick_task to log something already finished, or karea_doing for work in progress.
karea_edit_taskUpdate fields of an existing task (title, status, priority, deadline, category, assignee, description, tags, or add a note) located by visual ID, name or UUID. Only the fields you pass change; the rest are left untouched. Returns the updated task.
karea_close_taskMark a task as done: sets status to done and stamps the close time. Reports any unmet closing requisites first unless confirm is set. To close several tasks at once use karea_done.
karea_delete_taskPermanently delete a task and its history. Irreversible; requires confirm=true. To merely close a task instead, use karea_close_task.
karea_quick_taskLog something you already finished as a done task (it shows up in Recap) and return it. Status is always done; relative-time params set when it happened. For in-progress work use karea_doing instead.
karea_doingCreate a task you are working on right now (status: in_progress)
karea_view_taskReturn one task with all its details (status, priority, deadline, category, description, notes, requisites, links), located by visual ID, name or UUID. Pass includeContext=true to also inline the task's AI Context in the response — avoids a follow-up karea_get_context round-trip. Read-only.
karea_create_projectCreate a new Karea project owned by you and seed it with the default categories (Coding, Testing, Documenting, Reviewing). Returns the new project id. To add a category to an existing project, use karea_create_category instead.
karea_delete_projectPermanently delete a project and everything inside it (tasks, categories, notes, history). Irreversible; requires confirm=true.
karea_create_categoryCreate a new category (a task bucket) inside an existing project and return it. To create a whole project, use karea_create_project.
karea_delete_categoryPermanently delete a category AND every task inside it, including history. Irreversible; requires confirm=true. To delete a single task instead, use karea_delete_task.
karea_doneMark several tasks as done in one call, each given by visual ID or name; returns a per-task result. For a single task with closing-requisite checks, use karea_close_task.
karea_share_projectGive another user access to a project by email at a chosen role (owner, editor, commenter or viewer). Records the share so that user can see and, per role, edit the project.
karea_askSend a natural-language request to the Karea AI assistant, which may read or modify your tasks to carry it out, and return its reply. Consumes your monthly AI usage allowance.
karea_recapReturn a summary of recent activity (tasks created, closed and updated) over a recent time window. Read-only; handy for standups and reviews.
karea_get_markdownRead the markdown document attached to a task. This is the task's knowledge base — it contains investigation findings, technical and functional documentation, root cause analysis, solution design, implementation notes, and any other long-form content the task has accumulated. Always read this before…
karea_set_markdownWrite the markdown document for a task. Overwrites any existing content. Use this to persist: investigation findings and research, technical documentation (architecture, APIs, schemas), functional documentation (requirements, acceptance criteria, user flows), root cause analysis and debugging logs, …
karea_get_contextRead the task's Context — titled entries of AI working memory that hold the FULL HISTORY of a task (not just its current state): what was tried, decided, discovered, and abandoned along the way. ALWAYS read this first when picking a task up so you inherit the journey instead of re-deriving it. Each …
karea_set_contextWrite a titled entry of the task's Context — the AI-facing cross-session working memory. Context tracks the FULL HISTORY of a task, not just its current state: what was tried, what worked, what failed, what was decided and why. Update incrementally so the journey is preserved (never overwrite the wh…
karea_list_questionsList open questions (unresolved decisions or blockers) in a project, newest first. Defaults to status open; pass status to include answered, cancelled or all. Read-only.
karea_create_questionCreate an open question (a decision or blocker to resolve) in a project, optionally linked to tasks, and return it with its short ID (e.g. KAQ3).
karea_answer_questionAnswer an open question, located by short ID or text match: sets its answer and flips its status to answered. Returns the updated question.
karea_edit_questionEdit an open question: change its text, status (open, answered or cancelled), answer, or linked tasks. Only the fields you pass change. Returns the updated question.
karea_delete_questionPermanently delete an open question. Irreversible. To keep it but mark it resolved, set its status to cancelled via karea_edit_question instead.
karea_list_resourcesList resources (text notes & files). With a projectId it returns every resource belonging to that project - whether assigned to it directly, linked to one of its tasks, or filed under a folder named after the project (e.g. knowledge-base docs). Omit projectId to list all your resources, including un…
karea_get_resourceReturn a text resource with its full content and metadata, by ID. Read-only.
karea_create_resourceCreate a text resource (a note or document) in a project or folder and return it with its ID. To attach an existing resource to a task, use karea_link_resource_to_task.
karea_update_resourceOverwrite a text resource content and/or metadata, by ID, and return the updated resource. Replaces the existing content rather than appending.
karea_delete_resourcePermanently delete a resource (text or file) by ID. Irreversible. To only detach it from a task, use karea_unlink_resource_from_task.
karea_upload_resourceUpload a binary file as a resource (base64-encoded)
karea_link_resource_to_taskLink an existing resource (text or file) to a task. The resource and task must belong to the same user/project scope. Use this to attach release notes, design docs, references, etc. to one or more tasks. To link a resource to multiple tasks, call this once per task.
karea_unlink_resource_from_taskRemove the link between a resource and a task. Does not delete either side.
karea_list_notesList the notes (human-readable updates) on a task, newest first. Read-only.
karea_link_sessionLink your current AI coding session (Claude Code, OpenCode, Codex, Cursor, Aider) to a Karea task so the user can see the session history for that task and copy a command to resume the session later. Call this once per task you're working on. For Claude Code, pass sessionId as the CLI session id; fo…
karea_list_sessionsList AI coding sessions linked to a task (provider, sessionId, label, last active, resume command). Read-only.
karea_unlink_sessionRemove a previously-linked AI session from a task. Use the row ID from karea_list_sessions or karea_link_session.
karea_add_noteAdd a note to a task. Notes are human-readable updates/observations (the user reads them). For private AI working memory that persists across sessions, use karea_set_context instead.
karea_edit_noteChange the text of an existing note on a task, by note ID, and return the updated note.
karea_delete_notePermanently delete a note from a task, by note ID. Irreversible.
karea_create_subtaskCreate a subtask under a parent task. Accepts the parent by visual ID (e.g. KPL77), name, or UUID. Supports the same params as karea_create_task.
karea_list_subtasksList subtasks of a parent task. Accepts the parent by visual ID, name, or UUID.
karea_add_requisiteAdd a closing requisite (a checklist item that must be completed before the task may be closed) to a task, and return it.
karea_toggle_requisiteMark a closing requisite complete or incomplete, by ID. This affects whether karea_close_task warns about unmet requisites.
karea_delete_requisitePermanently delete a closing requisite from a task, by ID. Irreversible.
karea_get_jira_linkReturn the linked JIRA issue (key and URL) for a task, if one exists. Read-only.
karea_link_jiraLink a Karea task to a JIRA issue by issue key (e.g. PROJ-123)
karea_unlink_jiraRemove the JIRA link from a Karea task
KAREA_API_KEYKAREA_PUBLIC_URLKAREA_URLTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
49/49 tools missing one or more hints — karea_list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); karea_list_tasks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); karea_create_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +46 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tests exist
No test files found
Add tests that exercise each declared tool.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/starecz/karea-mcp)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check