Hawkeye Solutions MCP Server

Published on npm as hawkeye-solutions-mcp. MCP Registry name: io.github.AlyBlak3/hawkeye-mcp (see MCP Registry quickstart).

This server plugs into Cursor, Claude Desktop, and other MCP clients. It answers common EA / ops template questions and points people to the right Hawkeye Solutions Gumroad listing.

What it does

Health check: hawkeye_ping → pong
Templates: Meeting prep, EOD handoff, weekly briefing, SOP, project intake, VA onboarding, free EA prompts, bundles — each returns structure + a Gumroad link.

Install from npm (recommended)

Requires Node 20+.

Cursor / Claude-style config (runs the published package; no clone needed):

{
  "mcpServers": {
    "hawkeye": {
      "command": "npx",
      "args": ["-y", "hawkeye-solutions-mcp@latest"]
    }
  }
}

Or global CLI after npm install -g hawkeye-solutions-mcp:

hawkeye-mcp

(point your MCP client at hawkeye-mcp as the command, no args).

Develop from this repo

npm install
npm run build

Local MCP config:

{
  "mcpServers": {
    "hawkeye": {
      "command": "node",
      "args": ["/absolute/path/to/hawkeye-mcp-server/dist/index.js"]
    }
  }
}

After code changes, run npm run build again.

Maintainer: publish to npm + MCP Registry

One-time setup

npm — Create an account at npmjs.com, verify email, create an Automation token: Access Tokens.
GitHub — In repo Settings → Secrets and variables → Actions, add NPM_TOKEN (the automation token).
Registry name — package.json → mcpName and server.json → name must both be io.github.AlyBlak3/hawkeye-mcp (GitHub’s allowed prefix is case-sensitive) and must match GitHub-based registry auth for user AlyBlak3.
server.json → packages[0].identifier must equal the npm name (hawkeye-solutions-mcp). Keep versions aligned with package.json on main, or rely on the workflow below to set them from the tag at publish time.

Automated publish (works while you’re offline)

Pushing a version tag runs .github/workflows/publish-mcp.yml: it sets package.json / server.json versions from the tag, builds, runs npm publish, then mcp-publisher publish using GitHub OIDC (mcp-publisher login github-oidc).

# After committing your changes to main:
git tag v1.0.1
git push origin v1.0.1

If OIDC login fails in Actions, publish the registry entry once from your machine: install mcp-publisher, then mcp-publisher login github and mcp-publisher publish.

First publish manually (optional)

If you prefer not to use Actions the first time:

npm login
npm run build
npm publish
mcp-publisher login github
mcp-publisher publish

If hawkeye-solutions-mcp is already taken on npm, change name in package.json, identifier in server.json, and the npx snippet in this README to a name you own.

What this does not do by itself

The MCP and registry are distribution: they help the right people find Hawkeye and open Gumroad from the assistant. Purchases still depend on listings, pricing, trust, and follow-up channels (e.g. AEO content, email, social). Treat this as the top of the funnel, not a substitute for those.

License

ISC — see LICENSE.

hawkeye-mcp

Quick Install