karea-mcp
# karea-mcp
The MCP server for [Karea](https://karea.app). <!-- SYNC:TOOL_COUNT -->64<!-- /SYNC:TOOL_COUNT --> tools so Claude Code, Cursor, and any other MCP-compatible client can create, edit, close, recap, link, and otherwise manage your tasks while you code.
[](https://www.npmjs.com/package/karea-mcp)
[](https://github.com/starecz/karea-mcp/blob/main/LICENSE)
[](https://glama.ai/mcp/servers/starecz/karea-mcp)
## What you can do with it
- Create / edit / close / delete tasks and subtasks from inside Claude Code while it codes
- Read and write long-form markdown on any task (perfect for solution design + investigation notes)
- Track open questions per task and answer them later
- Attach resources (file references, links) to tasks
- Link tasks to Jira and back
- Get a productivity recap across a date range
- Manage categories, projects, and project sharing
## Install
```bash
npx karea-mcp
```
## Configure (Claude Code)
Add to `~/.claude.json` (or run `claude mcp add`):
```json
{
"mcpServers": {
"karea": {
"command": "npx",
"args": ["-y", "karea-mcp"],
"env": {
"KAREA_API_KEY": "your_key_here",
"KAREA_URL": "https://karea.app"
}
}
}
}
```
Get your API key at <https://karea.app/dashboard/settings?section=api-keys>.
## Configure (Cursor)
Add to `.cursor/mcp.json` in your project, or to `~/.cursor/mcp.json` globally:
```json
{
"mcpServers": {
"karea": {
"command": "npx",
"args": ["-y", "karea-mcp"],
"env": {
"KAREA_API_KEY": "your_key_here"
}
}
}
}
```
## Tool catalogue
<!-- SYNC:TOOL_CATALOGUE -->
**64 tools** (regenerated by `scripts/sync-metadata.mjs`):
- `karea_add_note`
- `karea_add_requisite`
- `karea_answer_question`
- `karea_ask`
- `karea_check_reminders`
- `karea_close_task`
- `karea_create_category`
- `karea_create_meeting`
- `karea_create_project`
- `karea_create_question`
- `karea_create_reminder`
- `karea_create_resource`
- `karea_create_subtask`
- `karea_create_task`
- `karea_delete_category`
- `karea_delete_meeting`
- `karea_delete_note`
- `karea_delete_project`
- `karea_delete_question`
- `karea_delete_requisite`
- `karea_delete_resource`
- `karea_delete_task`
- `karea_dismiss_reminder`
- `karea_doing`
- `karea_done`
- `karea_edit_meeting`
- `karea_edit_note`
- `karea_edit_question`
- `karea_edit_task`
- `karea_get_context`
- `karea_get_jira_link`
- `karea_get_markdown`
- `karea_get_resource`
- `karea_link_jira`
- `karea_link_question_to_meeting`
- `karea_link_resource_to_task`
- `karea_link_session`
- `karea_link_task_to_meeting`
- `karea_list_meetings`
- `karea_list_notes`
- `karea_list_projects`
- `karea_list_questions`
- `karea_list_resources`
- `karea_list_sessions`
- `karea_list_subtasks`
- `karea_list_tasks`
- `karea_mark_reminder_done`
- `karea_quick_task`
- `karea_recap`
- `karea_set_context`
- `karea_set_markdown`
- `karea_share_project`
- `karea_snooze_reminder`
- `karea_toggle_requisite`
- `karea_unlink_jira`
- `karea_unlink_question_from_meeting`
- `karea_unlink_resource_from_task`
- `karea_unlink_session`
- `karea_unlink_task_from_meeting`
- `karea_update_resource`
- `karea_upload_resource`
- `karea_view_meeting`
- `karea_view_task`
- `karea_view_tasks`
<!-- /SYNC:TOOL_CATALOGUE -->
## Workflow example
```
You: I'm starting on the auth bug.
Claude (via karea-mcp): karea_doing("auth bug")
--> status set to in_progress
You: Add a closing requisite: must pass the failing test.
Claude: karea_add_requisite(...)
You (later): I fixed it.
Claude: karea_toggle_requisite(...) then karea_done("auth bug")
```
## License
MIT. See [LICENSE](https://github.com/starecz/karea-mcp/blob/main/LICENSE).
TDQS
Scored across 49 tools
Each tool has a distinct and well-documented purpose. Descriptions explicitly clarify boundaries (e.g., karea_add_note vs. karea_set_context, karea_create_task vs. karea_doing vs. karea_quick_task), making it easy to differentiate even among many tools.
All tools follow the consistent pattern 'karea_verb_noun' using snake_case, e.g., list_tasks, create_project, delete_resource. Minor exceptions like 'karea_doing' and 'karea_done' are still intuitive and fit the overall style.
At 49 tools, the server feels overloaded. While each tool serves a specific purpose, the count significantly exceeds the typical well-scoped range of 3-15 tools, making the surface heavy and harder for an agent to navigate efficiently.
The toolset covers nearly every expected operation for a task management system: full CRUD for tasks, projects, categories, notes, resources, questions, and requisites, plus context/markdown management, Jira integration, session linking, and bulk actions. No obvious gaps.