karea-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KAREA_URL | No | The URL of the Karea instance. | https://karea.app |
| KAREA_API_KEY | Yes | Your Karea API key. Get it at https://karea.app/dashboard/settings/api-keys. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| karea_list_projectsA | List all Karea projects with their IDs |
| karea_list_tasksA | List 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_taskC | Create a new task |
| karea_edit_taskC | Edit an existing task |
| karea_close_taskC | Mark a task as done |
| karea_delete_taskC | Delete a task (requires confirmation) |
| karea_quick_taskB | Log something you already did |
| karea_doingA | Create a task you are working on right now (status: in_progress) |
| karea_view_taskB | View full details of a task |
| karea_create_projectC | Create a new project |
| karea_delete_projectC | Delete a project |
| karea_create_categoryB | Create a new category in the current project |
| karea_delete_categoryC | Delete a category |
| karea_doneB | Mark multiple tasks as done at once |
| karea_share_projectB | Share a project with another user |
| karea_askB | Send a natural language message to Karea AI |
| karea_recapC | Get a recap of recent activity |
| karea_get_markdownA | Read 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 working on a task to avoid duplicating past research. |
| karea_set_markdownA | Write 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, solution design — planned or implemented, risks, trade-offs, and open questions. This is the single source of truth for everything learned about this task. Always append to existing content (read first with karea_get_markdown) rather than replacing it, unless restructuring. |
| karea_list_questionsC | List open questions in a project |
| karea_create_questionC | Create a new open question |
| karea_answer_questionC | Answer an open question |
| karea_edit_questionC | Edit an open question |
| karea_delete_questionC | Delete an open question |
| karea_list_resourcesA | List resources (text notes & files) in a project |
| karea_get_resourceA | Get a text resource content by ID |
| karea_create_resourceB | Create a text resource |
| karea_update_resourceC | Update a text resource |
| karea_delete_resourceC | Delete a resource |
| karea_upload_resourceB | Upload a binary file as a resource (base64-encoded) |
| karea_link_resource_to_taskA | Link 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_taskA | Remove the link between a resource and a task. Does not delete either side. |
| karea_list_notesC | List notes on a task |
| karea_add_noteC | Add a note to a task |
| karea_edit_noteB | Edit an existing note on a task |
| karea_delete_noteA | Delete a note from a task |
| karea_create_subtaskA | Create 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_subtasksB | List subtasks of a parent task. Accepts the parent by visual ID, name, or UUID. |
| karea_add_requisiteC | Add a closing requisite to a task |
| karea_toggle_requisiteB | Mark a closing requisite as complete or incomplete |
| karea_delete_requisiteB | Delete a closing requisite from a task |
| karea_get_jira_linkC | Get the JIRA link for a task |
| karea_link_jiraB | Link a Karea task to a JIRA issue by issue key (e.g. PROJ-123) |
| karea_unlink_jiraB | Remove the JIRA link from a Karea task |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/starecz/karea-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server