Hiveship Mcp Server

io.github.SorcRRPublished by GitHub account SorcRRv0.7.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyProductivity & Workflow Developer Tools

Server details

Identifier: io.github.SorcRR/hiveship-mcp-server
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 22, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account SorcRR for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.SorcRR%2Fhiveship-mcp-server.svg)](https://sourceweft.com/mcp/io.github.SorcRR%2Fhiveship-mcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets AI coding agents read and work with issues in the Hiveship issue tracker.

What you can do: Connect an AI coding agent to a Hiveship workspace so it can work with the issue tracker.
Issue tracking: the manifest lists no individual tools, so exact operations are not documented here; the server is described as letting coding agents interact with Hiveship issues.
Deep links: tool output can include links into the Hiveship web app.
When to use it: Use it when your team tracks work in Hiveship and you want a coding agent to see and act on issues while it works, instead of copying ticket details into the chat by hand.
Requirements: Runs locally over stdio via npx from the npm package @hiveship/mcp-server, so Node.js is needed. Requires HIVESHIP_API_TOKEN (an agent token or personal access token) and HIVESHIP_API_URL. HIVESHIP_WORKSPACE_ID is required for agent tokens and scoped tokens, optional for spanning tokens; HIVESHIP_WEB_URL is optional. Desktop only.

Before you install

The server holds a Hiveship API token that grants access to your workspace; treat HIVESHIP_API_TOKEN as a secret and prefer a narrowly scoped token. The manifest does not list the tools, so what the agent can change in the tracker is not documented here; check before letting it write. Issue data is sent to the Hiveship API.

Installation

In SourceWeft

Open Hiveship Mcp Server in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.7.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.