All servers / Project management / Opsee MCP server
Opsee MCP server
Opsee MCP server — manage projects, tasks, docs, and cycles from AI coding environments
Tested by ConnectATDScore 81 out of 100. Tested 2026-11-18 on package version 0.11.46. Package: @opsee/mcp-server
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 19 / 20 | |
| Package safety | 12 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (4.8 seconds including download)
- Tools offered: 94
- Last published: 2026-11-18
- Weekly downloads (npm): 3,282
- License: none listed · Direct dependencies: 10
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
opsee_get_meno parametersGet the currently authenticated Opsee user's profile (name, email, role, company).
opsee_list_users2 of 2 parameters describedLists users in the authenticated company. Opsee scopes users at the Company level — there is no project-scoped user listing because Users do not have a per-project relation. Use this to resolve assignee names to IDs.
opsee_get_user1 of 1 parameter describedGet full details of a specific user by ID.
opsee_list_projectsno parametersList all Opsee projects the authenticated user has access to.
opsee_get_project1 of 1 parameter describedGet details of a specific Opsee project by ID.
opsee_list_tasks19 of 19 parameters describedList tasks in an Opsee project. Supports filtering by status, assignee, board column, cycle, labels, priority, type, milestone, parent, due date, and update/create recency. labelIds uses AND semantics; multi-id filters (priorityIds/taskTypeIds/milestoneIds) use OR semantics. Supports sorting via sortBy (created_at|updated_at|due_date|priority|title|id|display_order) and sortDir (asc|desc).
opsee_get_task2 of 2 parameters describedGet full details of a specific task by ID. Pass includeContext=true when picking up a ticket to also get its labels, comments, dependencies (both directions), parent task, and subtasks in the same call — saves ~5 round-trips.
opsee_create_task13 of 13 parameters describedCreate a new task in an Opsee project. Use opsee_list_task_types, opsee_list_task_priorities, and opsee_list_board_columns first to get valid values for optional fields.
opsee_update_task14 of 14 parameters describedUpdate a task's fields (patch semantics - only provided fields are changed). Fetches the current task first, merges your changes, and sends the full update.
opsee_bulk_update_tasks12 of 12 parameters describedApply the same field changes to many tasks at once — reassign, reprioritize, move to a column or cycle, or any combination. Backend wraps all updates in one DB transaction. Per-task lookup failures (task not visible to your company, or unknown ID) are silently skipped — compare updated_count against taskIds.length to detect partial application. Omitted fields are not touched. labelIds with a non-empty list replaces each task's labels; empty/omitted leaves them alone.
opsee_replace_task_labels2 of 2 parameters describedReplace the entire set of labels on a single task. Use opsee_update_task with labelIds for the same effect, but this tool is more discoverable for the common 'set my labels to [...]' flow.
opsee_link_task_to_initiative2 of 2 parameters describedLink an existing task to an Initiative — use this to bring an already-existing task into an initiative's scope. To create NEW tasks under an initiative, use opsee_decompose_initiative (first time) or opsee_reconcile_initiative (re-planning) instead. Fetches the task first so no other fields are blanked.
opsee_unlink_task_from_initiative1 of 1 parameter describedDetach a task from its current Initiative. Fetches the task first so no other fields are blanked.
opsee_delete_task1 of 1 parameter describedDelete a task by ID. This is permanent.
opsee_bulk_delete_tasks2 of 2 parameters describedDelete multiple tasks in one call. Tasks not visible to your company or not found are silently skipped — compare deletedCount against taskIds.length to detect partial application. This is permanent.
opsee_list_task_types1 of 1 parameter describedGet available task types (Bug, Feature, etc.) for an Opsee project. Use these IDs when creating or updating tasks.
opsee_list_task_priorities1 of 1 parameter describedGet priority levels (Critical, High, Medium, Low, etc.) for an Opsee project. Use these IDs when creating or updating tasks.
opsee_list_boards1 of 1 parameter describedList Kanban boards for an Opsee project. Use the board ID to list board columns.
opsee_list_board_columns1 of 1 parameter describedGet board columns/statuses (To Do, In Progress, Done, etc.) for a board. Use these IDs when creating or updating tasks.
opsee_list_cycles1 of 1 parameter describedList cycles/sprints in an Opsee project.
opsee_get_cycle1 of 1 parameter describedGet details of a specific cycle/sprint by ID.
opsee_create_cycle5 of 5 parameters describedCreate a new cycle/sprint in an Opsee project.
opsee_update_cycle7 of 7 parameters describedUpdate a cycle's fields (patch semantics — only provided fields change). Fetches the current cycle first, merges your changes, sends the full update.
opsee_close_cycle6 of 6 parameters describedClose a cycle (mark inactive) and carry its UNFINISHED tasks forward to a target cycle. Tasks in a done/archived column stay behind so the closed cycle keeps an accurate completion record. Pass createNextCycle:true with name/startDate/endDate to also create the next cycle and carry forward into it in the same call. Omit both target options to close without moving anything.
opsee_get_active_cycle1 of 1 parameter describedReturn the currently-active cycle for a project, or 'No active cycle' if none.
opsee_delete_cycle1 of 1 parameter describedDelete a cycle by ID. This is permanent. Tasks assigned to the cycle are not deleted, but their cycle reference is cleared.
opsee_list_doc_spaces1 of 1 parameter describedList documentation spaces in an Opsee project.
opsee_list_doc_pages1 of 1 parameter describedList documentation pages in an Opsee project.
opsee_get_doc_page1 of 1 parameter describedRead a documentation page's content by ID.
opsee_create_doc_page5 of 5 parameters describedCreate a new documentation page in an Opsee project.
opsee_update_doc_page6 of 6 parameters describedUpdate a documentation page's title, content, or contentType. Read-merge-write: fields you don't pass are preserved. No optimistic lock -- a concurrent edit from the web UI can be silently lost. Content cannot be cleared to an empty string; that call is rejected up front rather than reporting a false success. Ordering is not settable here -- it belongs to opsee_move_doc_page. Changing title or content snapshots the prior version into page history unless snapshotVersion: false.
opsee_delete_doc_page1 of 1 parameter describedDelete a documentation page. Soft delete with no cascade: child pages are neither deleted nor reparented, so they keep pointing at the deleted parent -- still listable, but gone from the page tree. No undo through this API. Requires Admin or Owner; a User-role caller gets a permission error. To hide a page reversibly instead, use opsee_set_doc_page_archived.
opsee_set_doc_page_archived2 of 2 parameters describedArchive or unarchive a documentation page. This does not cascade to child pages. Archived pages are excluded from the doc page tree view by default. Reversible: call again with archived: false to restore it.
opsee_list_repositories1 of 1 parameter describedList connected VCS repositories (GitHub/GitLab) for an Opsee project.
opsee_list_milestones1 of 1 parameter describedList milestones in an Opsee project.
opsee_get_milestone1 of 1 parameter describedGet details of a specific milestone by ID.
opsee_create_milestone6 of 6 parameters describedCreate a new milestone in an Opsee project.
opsee_update_milestone6 of 6 parameters describedUpdate a milestone's fields. Fetches the current milestone first, then applies only the provided changes.
opsee_list_milestone_tasks1 of 1 parameter describedList tasks attached to a specific milestone.
opsee_attach_task_to_milestone2 of 2 parameters describedAttach an existing task to a milestone.
opsee_detach_task_from_milestone1 of 1 parameter describedDetach a task from a milestone. Requires the MilestoneTask ID (not the task ID) — use opsee_list_milestone_tasks to find it.
opsee_list_labels3 of 3 parameters describedList labels defined in an Opsee project. Use opsee_list_task_labels for labels attached to a specific task.
opsee_get_label1 of 1 parameter describedGet full details of a specific label by ID.
opsee_create_label5 of 5 parameters describedCreate a new label in an Opsee project.
opsee_update_label5 of 5 parameters describedUpdate a label's fields (patch semantics - only provided fields are changed). Fetches the current label first, merges your changes, and sends the full update.
opsee_delete_label1 of 1 parameter describedDelete a label permanently. Attached TaskLabel rows are not cleaned up automatically by this tool — backend behavior dictates whether cascade applies.
opsee_attach_label_to_task2 of 2 parameters describedAttach an existing label to a task. Returns the TaskLabel join-row ID needed for opsee_detach_label_from_task.
opsee_detach_label_from_task1 of 1 parameter describedPass the TaskLabel join-row id (returned from opsee_list_task_labels), not the labelId. Proto DeleteTaskLabelRequest takes the join PK.
opsee_list_task_labels3 of 3 parameters describedList labels attached to a specific task (returns TaskLabel join rows with embedded Label data).
opsee_list_comments4 of 4 parameters describedList comments on a task or an Initiative, oldest first. Includes both regular and internal comments visible to the caller. Provide exactly one of taskId or initiativeId.
opsee_add_comment4 of 4 parameters describedAdd a comment to a task or an Initiative. Posts as the authenticated user. Provide exactly one of taskId or initiativeId. Set isInternal=true to mark the comment as internal (visibility depends on backend RBAC).
opsee_edit_comment3 of 3 parameters describedEdit an existing comment's content and/or internal flag. Posts as the original author. Use opsee_list_comments first to confirm the comment ID.
opsee_delete_comment1 of 1 parameter describedDelete a comment by ID. This is permanent.
opsee_create_task_dependency3 of 3 parameters describedCreate a dependency relationship between two tasks. Use BLOCKS when the from-task must be completed before the to-task. Use BLOCKED_BY for the inverse. Use DUPLICATES when tasks are duplicates. Use RELATES_TO for a general association.
opsee_list_task_dependencies3 of 3 parameters describedList all dependencies for a task — returns both outgoing (task blocks others) and incoming (task is blocked by others) relationships.
opsee_delete_task_dependency1 of 1 parameter describedDelete a task dependency by its ID. This is permanent.
opsee_get_dependency_chain3 of 3 parameters describedServer-side BFS over the BLOCKS/BLOCKED_BY graph from a task. Returns the reachable tasks and the edges that connect them. Use direction='blocks' for downstream (what does this task unblock), 'blocked_by' for upstream (what is this task waiting on), 'both' for the full neighborhood. Depth caps at 10.
opsee_list_work_logs1 of 1 parameter describedList all work-log entries for a task, oldest first. Includes the user who logged each entry, hours, and optional description.
opsee_log_work3 of 3 parameters describedLog time against a task. Posts as the authenticated user. Hours must be > 0.
opsee_delete_work_log2 of 2 parameters describedDelete a work-log entry by ID. This is permanent.
opsee_get_task_actual_hours1 of 1 parameter describedSum of all work_log hours on a task. Use this to compare against opsee_get_task's estimatedHours when assessing whether a task is over budget.
opsee_list_my_notifications3 of 3 parameters describedInbox-style listing of the authenticated user's notifications, newest first. Common notification_type values: task_assigned, comment_added, mention, task_blocked_unblocked, ai_workflow_status_change. Pass unreadOnly:true to see just the inbox.
opsee_mark_notification_read1 of 1 parameter describedMark a notification as read. Read-modify-write: fetches the current notification and re-issues EditNotification with is_read=true so other fields aren't clobbered.
opsee_mark_all_notifications_read1 of 1 parameter describedLoop through every unread notification and mark each read. Best-effort: per-notification failures are reported in the summary but don't abort the call. Caller can pass a maximum to bound the call.
opsee_list_task_acceptance_criteria1 of 1 parameter describedLists STRUCTURED acceptance criteria from a separate DB entity, NOT the checklist items inside the task description. Most tasks have their AC inline in the description as `- [ ]` markdown — to read those, fetch the task description via opsee_get_task and parse the checklist lines yourself. This tool only returns rows from the `acceptance_criteria` table, which is the automation/power-user path, not the main UI. Returns items ordered by display_order then id with text + done flag + display_order.
opsee_add_acceptance_criterion3 of 3 parameters describedPOWER-USER PATH — writes a STRUCTURED criterion to the `acceptance_criteria` DB table, which does NOT surface in the task detail UI. For typical AC, use opsee_update_task and write `- [ ]` checkbox lines under a `## Acceptance criteria` heading in the task description instead — those render as clickable checkboxes via BlockNote. Use this tool only when you need machine-trackable AC for automation (e.g. mapping criteria to PRs, AI workflow outputs, reporting). display_order defaults to 0; pass an explicit value to control ordering.
opsee_update_acceptance_criterion4 of 4 parameters describedPOWER-USER PATH — patches a STRUCTURED criterion in the `acceptance_criteria` DB table. Does NOT touch description-embedded checkboxes; those live in the task description and are edited via opsee_update_task's description field. Use this only for the automation path that created the criterion via opsee_add_acceptance_criterion. Patch semantics: any subset of text / done / displayOrder; fields not supplied are left alone.
opsee_delete_acceptance_criterion1 of 1 parameter describedPOWER-USER PATH — deletes a STRUCTURED criterion row from the `acceptance_criteria` DB table by ID. Does NOT remove `- [ ]` lines from a task description; for those, edit the description via opsee_update_task. Soft delete; this is permanent at the application layer.
opsee_list_initiatives2 of 2 parameters describedList initiatives in an Opsee project. Pass `search` to find a specific initiative by keyword — it matches the title and summary, tokenized, and ranks the best match first (most-recently-updated breaks ties). Use this to resume work by name, e.g. for "resume the auth-refactor initiative" call with search: "auth". Without `search`, returns all initiatives, most recent first.
opsee_get_initiative1 of 1 parameter describedGet details of a specific initiative by ID (title, status, summary, core idea). To pick up or resume WORK on it — the task tree, memory log, and PRs together — call opsee_get_initiative_context instead.
opsee_create_initiative8 of 8 parameters describedCreate a new initiative in an Opsee project. After creating, expand the plan in the core idea (the coreIdea field); when the plan is ready, propose a decomposition with opsee_decompose_initiative rather than creating tasks by hand.
opsee_update_initiative8 of 8 parameters describedUpdate an initiative's fields. Fetches the current initiative first, then applies only the provided changes. Status lifecycle: draft → active (opsee_decompose_initiative flips this automatically) → completed when the work is done. For dropped work, set status to 'abandoned' WITH a reason (in the summary or a memory entry) rather than deleting — that preserves the shared brain.
opsee_delete_initiative1 of 1 parameter describedDelete an initiative permanently. Prefer setting status to 'abandoned' (via opsee_update_initiative) with a reason — that preserves the initiative's memory/shared brain for later reference. Only hard-delete an initiative created in error.
opsee_get_initiative_context2 of 2 parameters describedLoad an entire Initiative work session in one call: the core-idea doc body, the execution task tree with parallel slices (what can run concurrently vs sequentially), the append-only memory log, and rolled-up PRs. Call this FIRST when picking up or resuming work on an Initiative. The response ends with a working agreement: treat this context as the source of truth, log decisions/blockers/learnings as you go with opsee_add_initiative_memory, and call opsee_checkpoint when you finish a unit of work.
opsee_get_initiative_graph1 of 1 parameter describedGet the task dependency graph for an initiative, including parallel execution batches (slices). Use the slices to choose the next batch of tasks that can be worked concurrently. (opsee_get_initiative_context already includes this graph — call this only when you need the graph on its own.)
opsee_decompose_initiative3 of 3 parameters describedMaterialize a proposed breakdown as real Tasks under the Initiative. PROPOSE FIRST: present the task tree (titles, structure, dependencies) to the human and get approval BEFORE calling — that approval is the confirm step, and not calling is how the human declines. One atomic operation; also moves a draft Initiative to active. Wire the tree with temporary `ref` ids: `parentRef` nests a subtask, `edges` (from_ref blocks to_ref) express sequencing, and tasks with no blocking edge run in parallel. All-or-nothing: a bad ref rolls the whole thing back.
opsee_reconcile_initiative4 of 4 parameters describedDiff a proposed task tree against an Initiative that already has tasks, and optionally apply it. For first-time task creation on a fresh Initiative use opsee_decompose_initiative instead. Workflow (follow every time): 1. opsee_get_initiative_context to load the current tree; note each task's ID. 2. Build the proposed list. Set existingTaskId to a real ID to keep that task; omit it for new tasks. 3. Call with dryRun:true to preview the changeset. 4. Present it to the human, ESPECIALLY flagged items: those carry execution state (PRs, worklogs, in-progress) and are never deleted — they stay on the board and the human decides their fate. 5. Only after explicit approval, call again with dryRun:false.
opsee_add_initiative_memory7 of 7 parameters describedLog a SINGLE decision, outcome, learning, blocker, or context entry to the Initiative's append-only memory the moment it happens — the as-you-go granular logger. Cite the source task or PR where relevant. For end-of-unit wrap-ups, use opsee_checkpoint instead.
opsee_checkpoint5 of 5 parameters describedEnd-of-unit wrap-up for an Initiative: records what a unit of work accomplished to the Initiative's memory and links what it touched. Call this when you finish a coherent chunk of work (a task, a PR, an investigation) — distinct from opsee_add_initiative_memory, which logs a single decision/blocker the moment it happens. Defaults the entry kind to 'outcome'.
opsee_list_initiative_memory4 of 4 parameters describedList memory entries for an initiative (newest first). Optionally filter by kind, source type, or source ID.
opsee_get_doc_space1 of 1 parameter describedGet full details of a specific doc space by ID.
opsee_create_doc_space4 of 4 parameters describedCreate a new documentation space in an Opsee project. Requires the Admin or Owner role; the User role has read-only access to doc spaces.
opsee_update_doc_space5 of 5 parameters describedUpdate a doc space's fields (patch semantics - only provided fields are changed). EditDocSpaceRequest has no field mask, so this fetches the current doc space first and resends every field. The slug is regenerated only when title changes.
opsee_delete_doc_space1 of 1 parameter describedDelete a doc space. Doc pages are not linked to doc spaces in the data model — pages are attached directly to the project. Deleting a doc space only removes this grouping row; it has no effect on any doc pages.
opsee_list_doc_templates1 of 1 parameter describedList documentation templates in an Opsee project.
opsee_create_doc_template4 of 4 parameters describedCreate a new documentation template in an Opsee project.
opsee_update_doc_template5 of 5 parameters describedUpdate a doc template's fields (patch semantics - only provided fields are changed). There is no GetDocTemplate RPC, so projectId is required: this tool looks up the current template via opsee_list_doc_templates for that project, merges in your changes, and resends the full update (UpdateDocTemplateRequest has no field mask).
opsee_delete_doc_template1 of 1 parameter describedDelete a doc template. Soft delete (the row is marked deleted, not erased), so it is recoverable by an operator but not through this API. Requires the Admin or Owner role; the User role can only list templates.
opsee_list_task_doc_pages1 of 1 parameter describedList doc pages attached to a specific task.
opsee_attach_doc_page3 of 3 parameters describedAttach an existing doc page to a task or a milestone. Pass exactly one of taskId / milestoneId.
opsee_detach_doc_page3 of 3 parameters describedDetach a doc page from a task or a milestone. Pass exactly one of taskId / milestoneId. The delete RPCs take the join-row id, which callers never have — this tool resolves it by listing the links and matching on docPageId.
opsee_list_milestone_doc_pages1 of 1 parameter describedList doc pages attached to a specific milestone.
opsee_read_run_record7 of 7 parameters describedRead an Initiative's Run Record — the Foreman's append-only log of what its unattended Workers did: every dispatch, how each turn ended, the Gate results (exit codes), the Verifier's Verdicts and Defects, human steering from the CLI, spend, and any Breaker that halted the night. Call this at the start of a planning session to ask what happened since you last looked, and before re-planning an Initiative the Foreman has been running. Filter by kind and by task, narrow to a time range, and page with afterId. Everything an agent wrote or a command printed comes back quoted as data.
opsee_file_defect7 of 7 parameters describedFile one failure you observed while verifying a Task as a Defect Task, exactly as the Foreman's unattended Verifier would: a sibling Task in the same Initiative (never a subtask), type Bug, related to the Task you found it on, carrying the dispatch label so the next tick schedules the fix, with a Goal / Acceptance Criteria / Verification / Boundaries description. Use this after verifying work by hand in an attended session — not for planned work, which belongs in the task tree. Everything you write here is quoted as data in the new Task, so a Worker reads it as a record of what you saw, never as instructions.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.