Eureka Labo Task Management MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EUREKA_API_KEY | Yes | Your project-specific API key (starts with pk_live_) | |
| EUREKA_API_URL | Yes | Your Eureka Labo API URL (production URL with HTTPS) | |
| WORKSPACE_PATH | No | Path to your git repository workspace (optional - automatically uses Claude Code's current directory) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tasksA | List tasks for the project. Optionally filter by status, assignee, or search term. |
| get_taskA | Get detailed information about a specific task, including change history. |
| create_taskB | Create a new task in the project. |
| update_taskB | Update an existing task. |
| start_work_on_taskA | Begin working on a task. Captures git baseline for change tracking. Requires clean working directory (no uncommitted changes). |
| complete_task_workA | Complete work on a task. Captures all git changes since work started and logs them to the task. |
| get_active_sessionsA | List all active work sessions. |
| cancel_work_sessionA | Cancel an active work session without logging changes. |
| list_project_membersA | List all members of the project (for task assignment). Project is automatically determined from API key. |
| upload_task_attachmentB | Upload a file attachment to a task. |
| list_branch_tasksB | List all tasks worked on in the current git branch. Shows tasks that are part of the branch session. |
| create_pull_requestA | Create a GitHub pull request for all tasks in the current branch. Generates PR description from work sessions. Requires GitHub integration configured for the project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Tools are mostly distinct, with clear separation between task CRUD, work sessions, members, attachments, and PR creation. Minor potential confusion exists between list_tasks and list_branch_tasks, but descriptions clarify the branch-specific scope.
Uses a consistent snake_case verb_noun pattern overall. Slight inconsistency between start_work_on_task and complete_task_work breaks the parallel structure, but the pattern is still readable and predictable.
12 tools is well within the ideal range and each tool serves a distinct purpose in the task management and GitHub workflow. No redundant or extraneous tools.
Covers task CRUD, work session lifecycle, attachments, members, and PR creation. Missing a delete_task/archive tool is a minor gap, but the core task management and integration workflow is otherwise complete.