HypAware

ai.hypaware由 hypaware.ai 發布官方發布者v1.43.0更新於 Nov 3, 2026

Query your team's AI coding history and act on HypAware recommendations from any MCP client.

已驗證Streamable HTTP可網頁執行知識與記憶開發者工具

概覽

AI 產生的概覽

HypAware 讓助理查詢團隊記錄的 AI 程式開發歷程並處理 HypAware 建議,可透過託管 MCP 伺服器或本機 npm 套件使用。

可以做什麼
  • 查詢組織記錄的 AI 程式開發歷程
  • 處理 HypAware 建議,包括標記建議狀態
  • 發布與刪除報告
  • 透過託管遠端伺服器連線,或在本機執行 npm 套件讀取自己的 HypAware 資料
  • 附帶兩個技能,說明如何查詢歷程以及 HypAware 是什麼
適用情境
當團隊使用 HypAware 記錄 AI 程式開發工作階段,並希望助理在 Claude Code、Cursor 或其他 MCP 用戶端中查詢這些歷程、跟進建議或管理報告時使用。
執行需求
需要 HypAware 帳號與 agent token,以 hyp CLI 產生(npm install -g hypaware,接著 hyp remote login --no-forward 與 hyp remote mint --scope query)。權杖透過 Authorization 標頭或 HYPAWARE_AGENT_TOKEN 環境變數傳入。遠端方式需要連線至託管端點的網路;npm 套件方式需要本機執行 HypAware 收集器才有資料。
安裝前請注意
權杖以簽發者身分行事,直到過期(預設 21 天,最長 90 天)或被撤銷,任何持有者都能做同樣的事。它可以讀取組織記錄的歷程、變更建議狀態、發布與刪除報告。不要放進會提交的檔案,用完請撤銷。外掛本身不記錄任何內容。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 HypAware,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.hypaware%2Fhypaware/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "hypaware": {
      "type": "http",
      "url": "https://api.hypaware.ai/v1/mcp"
    }
  }
}

README

HypAware plugin

Connect Claude Code, Cursor, or any agent that reads skills to the hosted HypAware MCP server. Your agent can then query your team's AI coding history and act on HypAware recommendations.

The plugin holds two things:

  • The MCP connection to https://api.hypaware.ai/v1/mcp, sent with your agent token in the Authorization header.
  • Two skills: hypaware-query (how to query the history and act on recommendations) and hypaware-reference (what HypAware is and how data flows). They are copies of the skills in the HypAware release this plugin is pinned to.

The plugin only reads and acts. It has no hooks, commands, agents, or binaries; it records nothing and runs nothing on your machine. Recording is the job of the hyp CLI and hyp attach.

Get a token

The plugin reads your token from the HYPAWARE_AGENT_TOKEN environment variable. If you have never minted one:

  1. Install the CLI: npm install -g hypaware.
  2. Sign in for queries only: hyp remote login --no-forward. This opens a browser sign-in and does not turn on any recording.
  3. Mint a token: hyp remote mint --scope query --label <where-it-runs>. It lasts the server's default, 21 days today. Ask for longer with --expires-days <n>, up to the server's limit (90 days by default).
  4. Put it in the environment your client starts in, such as export HYPAWARE_AGENT_TOKEN=<token> in your shell profile, or in the client's own secret store. Never put it in a file you commit.
  5. When you stop using it, revoke it: hyp remote tokens lists your tokens and hyp remote tokens revoke <jti> revokes one.

What the token can do. It acts as you, the person who minted it, until it expires or you revoke it. It can read your organization's recorded history, mark a recommendation's status, publish reports, and delete reports. It cannot change configuration, record or upload sessions, manage the organization, or mint more tokens. Anyone holding it can do the same, so keep it secret.

Install

Claude Code

In Claude Code:

text
/plugin marketplace add hyparam/hypaware-plugin/plugin install hypaware@hypaware

Or from a shell:

sh
claude plugin marketplace add hyparam/hypaware-pluginclaude plugin install hypaware@hypaware

Start Claude Code from a shell where HYPAWARE_AGENT_TOKEN is set. If claude mcp list shows the hypaware server as "Failed to connect" with HTTP 401, the token is unset or no longer valid.

Cursor, for a team

A team admin opens the Cursor dashboard, then Plugins & MCPs, Add Marketplace, Import from Repo, and enters hyparam/hypaware-plugin. The admin then sets HYPAWARE_AGENT_TOKEN under Plugins, Configure. Cursor lets only team admins set plugin variables.

Cursor, for one person

Cursor has no plugin install for one person, so set it up in two steps:

  1. Add the remote hypaware block from the Cursor section of the MCP guide to ~/.cursor/mcp.json (or a project's .cursor/mcp.json). It reads the token as ${env:HYPAWARE_AGENT_TOKEN}, so export the token before you start Cursor.
  2. Add the skills: npx skills add hyparam/hypaware-plugin -a cursor.

Other agents

For any agent the skills CLI knows (Pi, Codex, OpenCode and others):

sh
npx skills add hyparam/hypaware-plugin

This installs the two skills only. Connect the MCP server by following the MCP guide for your client.

If you already run hyp attach

hyp attach installs the same skills. With it, you need the plugin only for the MCP connection. In Claude Code both copies load side by side (the plugin's are named hypaware:hypaware-query and so on), so nothing is overwritten.

The MCP Registry entry

registry/server.json lists two ways to run the server:

  • The remote is the hosted server. Pick it if you have an agent token.
  • The npm package runs hyp mcp serve against your own local HypAware data. Pick it if you run the HypAware collector on your machine; without the collector it has nothing to show.

Updating the skills

Never edit a file under skills/ by hand. Change the skill in hypaware, release it, then run node scripts/sync-skills.js <version> here and commit the result. CI fails if skills/ differs from that release or any version field disagrees with it.

License

MIT. See LICENSE.

來源:README.md,提交 10a4883

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.43.0最新Oct 19, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分