@hiveship/mcp-server

MCPcommunity
v0.7.0UnknownMITUpdated todaynpmGitHub

MCP server for AI coding agents to interact with the Hiveship issue tracker

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
8Downloads/wk
todayLast update
Needs 1 credential before it runs
  • HIVESHIP_API_TOKENAPI keyrequired

    Bearer token — agent token (hsa_...) or personal access token (hsp_...)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.7.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface33 tools · none privileged
Security scan✓ Cleanv0.7.0 · todayHow well does this scan work?
EvalsNone
IndexedSep 22, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

33 tools · none privileged
Statically extracted from the published packagev0.7.0 · 8m ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_projectsList 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 triage issues.

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 triage issues.

No input schema was published for this tool.

list_project_updatesRead 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 update bodies are truncated with an explicit marker; raise limit for more.

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 update bodies are truncated with an explicit marker; raise limit for more.

No input schema was published for this tool.

create_project_updatePost a project status update — a health snapshot + markdown note on the project timeline; also stamps the project's current health. Check list_project_updates first so the note reflects real change. Requires the write:projects PAT scope.

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 first so the note reflects real change. Requires the write:projects PAT scope.

No input schema was published for this tool.

list_issuesList issues in a project. Optional filters: status/priority/assignee/label arrays, sprint (or currentSprint), delegateType (HUMAN vs AGENT), date ranges, free-text query, sorting; paginated.

List issues in a project. Optional filters: status/priority/assignee/label arrays, sprint (or currentSprint), delegateType (HUMAN vs AGENT), date ranges, free-text query, sorting; paginated.

No input schema was published for this tool.

get_issueGet detailed info about a specific issue

Get detailed info about a specific issue

No input schema was published for this tool.

create_issueCreate 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 list_projects with includeInbox: true); workspace-scoped tokens can create anywhere.

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 list_projects with includeInbox: true); workspace-scoped tokens can create anywhere.

No input schema was published for this tool.

update_issueUpdate an issue — pass only the fields to change. null clears assigneeId / storyPoints / dueDate / sprintId ([] clears labelIds); description cannot be cleared, omit to keep it.

Update an issue — pass only the fields to change. null clears assigneeId / storyPoints / dueDate / sprintId ([] clears labelIds); description cannot be cleared, omit to keep it.

No input schema was published for this tool.

link_prLink 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 not already carry the issue URL, edit it in too. Idempotent: re-linking the same provider + number refreshes it. Agent tokens need a live…

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 not already carry the issue URL, edit it in too. Idempotent: re-linking the same provider + number refreshes it. Agent tokens need a live…

No input schema was published for this tool.

get_issue_contextFull 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. Use this BEFORE starting work on an issue; use the lighter get_issue for a quick look.

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. Use this BEFORE starting work on an issue; use the lighter get_issue for a quick look.

No input schema was published for this tool.

list_commentsList 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 for more.

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 for more.

No input schema was published for this tool.

add_commentAdd a comment to an issue

Add a comment to an issue

No input schema was published for this tool.

post_activityPost a structured activity event to an agent session. `kind` is one of thought / tool_use / elicitation / response / error. `content` shape varies by kind: thought/response = { text }, tool_use = { toolName, args, result?, durationMs? }, elicitation = { question }, error = { message, stack? }.

Post a structured activity event to an agent session. `kind` is one of thought / tool_use / elicitation / response / error. `content` shape varies by kind: thought/response = { text }, tool_use = { toolName, args, result?, durationMs? }, elicitation = { question }, error = { message, stack? }.

No input schema was published for this tool.

search_issuesSearch 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 parent issue.

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 parent issue.

No input schema was published for this tool.

list_labelsList all labels in a Hiveship workspace. Labels can be attached to issues via update_issue.

List all labels in a Hiveship workspace. Labels can be attached to issues via update_issue.

No input schema was published for this tool.

list_workspacesList 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 spanning PAT (hsp_); workspace-scoped tokens are rejected here.

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 spanning PAT (hsp_); workspace-scoped tokens are rejected here.

No input schema was published for this tool.

get_workspace_insightsWorkspace-wide analytics: agent-vs-human work share, weekly throughput, open-issue load per assignee, agent-ops health (run-failure + PR-merge rates), and what needs attention (stale/unassigned issues, open PRs). Optional from/to bound the window. Requires the insights plan feature.

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 needs attention (stale/unassigned issues, open PRs). Optional from/to bound the window. Requires the insights plan feature.

No input schema was published for this tool.

get_project_insightsAnalytics for a single project: burndown (remaining-issue series + agent/human completion split), velocity per sprint, and cycle-time percentiles (p50/p75/p95) with agent-vs-human medians. Requires the insights plan feature.

Analytics for a single project: burndown (remaining-issue series + agent/human completion split), velocity per sprint, and cycle-time percentiles (p50/p75/p95) with agent-vs-human medians. Requires the insights plan feature.

No input schema was published for this tool.

list_sprintsList sprints in a project (planning, active, and completed) with issue + story-point completion counts. Pass `currentOnly: true` to get just the active sprint. Requires the PRO+ sprint-management plan feature.

List sprints in a project (planning, active, and completed) with issue + story-point completion counts. Pass `currentOnly: true` to get just the active sprint. Requires the PRO+ sprint-management plan feature.

No input schema was published for this tool.

list_agent_sessionsList agent work sessions (live + historical) with status, token usage, and model. Filter by status or agentId; paginated. Use get_agent_session_activity to see what a specific session actually did.

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 what a specific session actually did.

No input schema was published for this tool.

get_agent_session_activityGet the chronological activity feed for one agent session (thoughts, tool calls, elicitations, responses, errors). Cursor-paginated, oldest-first within the page; pass the returned cursor back to load more.

Get the chronological activity feed for one agent session (thoughts, tool calls, elicitations, responses, errors). Cursor-paginated, oldest-first within the page; pass the returned cursor back to load more.

No input schema was published for this tool.

get_my_queueThe 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-authenticated servers get a 403 — use list_issues / list_agent_sessions instead.

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-authenticated servers get a 403 — use list_issues / list_agent_sessions instead.

No input schema was published for this tool.

update_sessionUpdate your own agent work session — move it through its lifecycle (QUEUED → WORKING → WAITING_INPUT → COMPLETED/ERRORED) and report modelUsage, tokenUsage, modelUsed, or externalUrls. Report your usage on the COMPLETED/ERRORED call: nothing else records it, and a session that never reports is show…

Update your own agent work session — move it through its lifecycle (QUEUED → WORKING → WAITING_INPUT → COMPLETED/ERRORED) and report modelUsage, tokenUsage, modelUsed, or externalUrls. Report your usage on the COMPLETED/ERRORED call: nothing else records it, and a session that never reports is show…

No input schema was published for this tool.

get_guidanceGet agent guidance for the workspace — conventions, PR checklists, review rules a team configured. Read this before starting work; pass projectId once you know which project the issue belongs to for project-specific guidance too.

Get agent guidance for the workspace — conventions, PR checklists, review rules a team configured. Read this before starting work; pass projectId once you know which project the issue belongs to for project-specific guidance too.

No input schema was published for this tool.

list_playbooksList the named playbooks configured for a Hiveship workspace — reusable, versioned conventions a team saved (e.g. "how we fix flaky tests here"). Returns each playbook name, its "when to use" hint, and version, but NOT the body. Fetch a full playbook with get_playbook once you know its name.

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 playbook name, its "when to use" hint, and version, but NOT the body. Fetch a full playbook with get_playbook once you know its name.

No input schema was published for this tool.

get_playbookFetch a single playbook by name and return its full step-by-step body. Use list_playbooks first to discover available names.

Fetch a single playbook by name and return its full step-by-step body. Use list_playbooks first to discover available names.

No input schema was published for this tool.

list_membersList 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 update_issue. (Email is not exposed to agent callers.)

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 update_issue. (Email is not exposed to agent callers.)

No input schema was published for this tool.

list_notificationsList the calling user's notifications in a workspace (issue assignments, status changes, comment replies, agent-session outcomes, PR links). Pass `type: "COMMENT_REPLY"` to see only mentions/replies, or `unreadOnly: true` for the unread inbox.

List the calling user's notifications in a workspace (issue assignments, status changes, comment replies, agent-session outcomes, PR links). Pass `type: "COMMENT_REPLY"` to see only mentions/replies, or `unreadOnly: true` for the unread inbox.

No input schema was published for this tool.

list_workflow_statusesList 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` argument when creating, updating, or filtering issues.

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` argument when creating, updating, or filtering issues.

No input schema was published for this tool.

list_custom_viewsList 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+ custom-views plan feature.

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+ custom-views plan feature.

No input schema was published for this tool.

execute_custom_viewNo description published

This tool published no description. Forge does not invent one.

list_recent_activityNo description published

This tool published no description. Forge does not invent one.

get_setup_statusNo description published

This tool published no description. Forge does not invent one.

configureNo description published

This tool published no description. Forge does not invent one.

29 of 33 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for AI coding agents to interact with the Hiveship issue tracker

Keywords
mcpmodel-context-protocolhiveshipissue-trackerai-agentsclaude-codecursorcodex
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-22 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.