HypAware

ai.hypawarePublished by hypaware.aiOfficial publisherv1.43.0Updated Nov 3, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

HypAware lets an assistant query a team's recorded AI coding history and act on HypAware recommendations, via a hosted MCP server or a local npm package.

What you can do
  • Query your organization's recorded AI coding history
  • Act on HypAware recommendations, including marking a recommendation's status
  • Publish and delete reports
  • Connect through the hosted remote server or run the npm package locally against your own HypAware data
  • Ship two skills that explain how to query the history and what HypAware is
When to use it
Use it when your team records AI coding sessions with HypAware and you want an agent to look up that history, follow up on recommendations, or manage reports from Claude Code, Cursor or another MCP client.
Requirements
A HypAware account and an agent token, minted with the hyp CLI (npm install -g hypaware, then hyp remote login --no-forward and hyp remote mint --scope query). The token is passed in the Authorization header or the HYPAWARE_AGENT_TOKEN environment variable. The remote option needs network access to the hosted endpoint; the npm package needs a local HypAware collector to have data.
Before you install
The token acts as the person who minted it until it expires (21 days by default, up to 90) or is revoked, and anyone holding it can do the same. It can read your organization's recorded history, change recommendation status, and publish or delete reports. Keep it out of committed files and revoke it when done. The plugin itself records nothing.

Installation

In SourceWeft

  1. Open HypAware in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.hypaware%2Fhypaware/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "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.

Source: README.md at commit 10a4883

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.43.0LatestOct 19, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts