HypAware MCP server

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:

agent token in the Authorization header.

• The MCP connection to https://api.hypaware.ai/v1/mcp, sent with your

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.

• Two skills: hypaware-query (how to query the history and act on

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 HYPAWAREAGENTTOKEN environment variable. If you have never minted one:

browser sign-in and does not turn on any recording.

1. Install the CLI: npm install -g hypaware.
2. Sign in for queries only: hyp remote login --no-forward. This opens a

It lasts the server's default, 21 days today. Ask for longer with --expires-days , up to the server's limit (90 days by default).

1. Mint a token: hyp remote mint --scope query --label .

export HYPAWAREAGENTTOKEN= in your shell profile, or in the client's own secret store. Never put it in a file you commit.

1. Put it in the environment your client starts in, such as

and hyp remote tokens revoke revokes one.

1. When you stop using it, revoke it: hyp remote tokens lists your tokens

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:

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

Or from a shell:

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

Start Claude Code from a shell where HYPAWAREAGENTTOKEN 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 HYPAWAREAGENTTOKEN 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:

Cursor section of the MCP guide to ~/.cursor/mcp.json (or a project's .cursor/mcp.json). It reads the token as ${env:HYPAWAREAGENTTOKEN}, so export the token before you start Cursor.

1. Add the remote hypaware block from the

1. 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):

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:

Shortened. The full README is on GitHub.