# @hiveship/mcp-server MCP server for AI coding agents to interact with the Hiveship issue tracker - **Type:** MCP server - **Trust:** 60/100 (B), scored on the package rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 0.7.0 - **Author:** Unknown - **License:** MIT - **npm:** @hiveship/mcp-server - **Source:** https://github.com/SorcRR/HiveShip - **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport) ## Trust 60/100 (B), scored on the package rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-09-22T18:51:01.190Z - **Version scanned:** 0.7.0 - **CVEs:** none found by OSV at scan time ## Tools 33 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `list_projects` — List the projects in a Hiveship workspace (paginated). Pass includeInbox: true to also surface the triage Inbox (hidden by default) when you need its id to file - `list_project_updates` — Read a project status-update timeline (newest first). Use this before posting a new update so the draft reflects what actually changed since the last one. Long - `create_project_update` — Post a project status update — a health snapshot + markdown note on the project timeline; also stamps the project's current health. Check list_project_updates f - `list_issues` — List issues in a project. Optional filters: status/priority/assignee/label arrays, sprint (or currentSprint), delegateType (HUMAN vs AGENT), date ranges, free-t - `get_issue` — Get detailed info about a specific issue - `create_issue` — Create a new issue. Server defaults: status BACKLOG, priority NONE. Session-scoped agent tokens can only create into the workspace triage Inbox (find its id via - `update_issue` — Update an issue — pass only the fields to change. null clears assigneeId / storyPoints / dueDate / sprintId ([] clears labelIds); description cannot be cleared, - `link_pr` — Link a pull request to an issue after opening it — the PR shows on the issue page and, while open, the review queue. One-directional: if the PR description does - `get_issue_context` — Full pre-work briefing for one issue in a single call: the issue core (status, assignee, linked PRs), its most recent comments, and its recent agent activity. U - `list_comments` — List an issue’s comment thread (author, date, body; one level of replies nested), oldest first. Long bodies are truncated with an explicit marker; raise limit f - `add_comment` — Add a comment to an issue - `post_activity` — Post a structured activity event to an agent session. `kind` is one of thought / tool_use / elicitation / response / error. `content` shape varies by kind: thou - `search_issues` — Search a workspace by text. Matches issue titles, issue numbers (e.g. "42" or "ENG-42"), project names, and comment bodies. Comment hits link back to their pare - `list_labels` — List all labels in a Hiveship workspace. Labels can be attached to issues via update_issue. - `list_workspaces` — List the workspaces the current user belongs to (ids, names, plan tier, member/agent counts). Use the returned `id` as `workspaceId` for other tools. Requires a - `get_workspace_insights` — Workspace-wide analytics: agent-vs-human work share, weekly throughput, open-issue load per assignee, agent-ops health (run-failure + PR-merge rates), and what - `get_project_insights` — Analytics for a single project: burndown (remaining-issue series + agent/human completion split), velocity per sprint, and cycle-time percentiles (p50/p75/p95) - `list_sprints` — List sprints in a project (planning, active, and completed) with issue + story-point completion counts. Pass `currentOnly: true` to get just the active sprint. - `list_agent_sessions` — List agent work sessions (live + historical) with status, token usage, and model. Filter by status or agentId; paginated. Use get_agent_session_activity to see - `get_agent_session_activity` — Get the chronological activity feed for one agent session (thoughts, tool calls, elicitations, responses, errors). Cursor-paginated, oldest-first within the pag - `get_my_queue` — The calling agent's own work queue — issues delegated to you, oldest first (FIFO); poll it to find waiting work. Requires an agent bearer token (hsa_); PAT-auth - `update_session` — Update your own agent work session — move it through its lifecycle (QUEUED → WORKING → WAITING_INPUT → COMPLETED/ERRORED) and report modelUsage, tokenUsage, mod - `get_guidance` — Get agent guidance for the workspace — conventions, PR checklists, review rules a team configured. Read this before starting work; pass projectId once you know - `list_playbooks` — List the named playbooks configured for a Hiveship workspace — reusable, versioned conventions a team saved (e.g. "how we fix flaky tests here"). Returns each p - `get_playbook` — Fetch a single playbook by name and return its full step-by-step body. Use list_playbooks first to discover available names. - `list_members` — List the human members of a workspace with their role (OWNER / ADMIN / MEMBER / VIEWER). Use the returned `user id` when assigning an issue to a person via upda - `list_notifications` — List the calling user's notifications in a workspace (issue assignments, status changes, comment replies, agent-session outcomes, PR links). Pass `type: "COMMEN - `list_workflow_statuses` — List the workflow statuses available in a workspace (e.g. BACKLOG / TODO / IN_PROGRESS / DONE plus any custom statuses). Use the returned `value` as the `status - `list_custom_views` — List the calling user's saved views (issue filters) for a project — each view’s name, id, and filters. Run one with execute_custom_view. Requires the PRO+ custo - `execute_custom_view` - `list_recent_activity` - `get_setup_status` - `configure` ## Install **Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for. **Cautions** (coverage gaps and advisories — never blocking) - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@hiveship/mcp-server\"\n ],\n \"env\": {\n \"HIVESHIP_API_TOKEN\": \"\"\n }\n }\n }\n}" ``` **Credentials it will ask for** (names only — Forge never holds a value): - `HIVESHIP_API_TOKEN` — Hiveship API Token (required) Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one. - This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset. ## Blast radius Moderate blast radius — holds an api key; runs on your machine. - Floor 23, ceiling 23 (tier: moderate) - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/%40hiveship%2Fmcp-server - Install plan: https://forgeregistry.com/api/v1/packages/%40hiveship%2Fmcp-server/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/%40hiveship%2Fmcp-server - HTML page: https://forgeregistry.com/registry/%40hiveship%2Fmcp-server - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.