mcp-agrus-ai

A Model Context Protocol server for Agrus.ai — the front-deployed AI agency for regulated industries.

This server lets AI agents (Claude, ChatGPT, Gemini, custom buyer-side agents) engage Agrus.ai programmatically. A CIO using her internal Claude assistant can ask "find me a HIPAA-compliant AI consultancy that does self-hosted deployments and scope a 2-week PoC for clinical triage" — and that assistant can complete most of the workflow through this MCP server.

Currently ships 5 read-only tools (Phase 1). Write tools (book a call, request a proposal, request a quote) land in Phase 2 — see Roadmap.

Tools

All tools return structured JSON inside an MCP text content block. No authentication required for Phase 1 tools.

Requirements

• Node.js 20+ (uses ES modules + NodeNext resolution)
• An MCP-compatible client (Claude Desktop, Continue.dev, Cursor, or anything that speaks the MCP stdio protocol)

Install

From source

git clone https://github.com/phwizard/mcp-agrus-ai.git
cd mcp-agrus-ai
npm install
npm run build

The built entry point is dist/index.js (executable, #!/usr/bin/env node shebang).

From npm

npx -y mcp-agrus-ai

No global install needed. npx fetches the latest published version and runs it over stdio.

Three ways to use this server

1. Hosted (recommended)

The server is publicly hosted at https://mcp.agrus.ai/mcp (Streamable HTTP transport). No install required. Point any MCP client that supports remote URL transports at:

{
  "mcpServers": {
    "agrus": {
      "url": "https://mcp.agrus.ai/mcp"
    }
  }
}

2. Local stdio via npx

For Claude Desktop and other clients that prefer stdio:

{
  "mcpServers": {
    "agrus": {
      "command": "npx",
      "args": ["-y", "mcp-agrus-ai"]
    }
  }
}

Claude Desktop config path on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json.

3. Local stdio from source

For development against a local checkout:

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

Restart your MCP client after editing the config. The seven Agrus tools will be available in any conversation. Try:

Use the agrus MCP to query Agrus's position on HIPAA for an AI agent that drafts clinical notes against a patient's EHR.

Scope a Discovery Sprint with Agrus for an insurance carrier that wants AI-assisted claims triage with bias testing.

List Agrus's verticals and tell me which one a fintech regulatory-reporting copilot would fall into.

Use with other MCP clients

Anything that speaks MCP stdio or Streamable HTTP works. For remote use, the canonical endpoint is https://mcp.agrus.ai/mcp and the discovery manifest sits at https://mcp.agrus.ai/.well-known/mcp.json.

Test the server directly

Send raw MCP protocol messages over stdio:

printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.0.1"}}}' \
  '{"jsonrpc":"2.0","method":"notifications/initialized"}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
  | node dist/index.js

You should see the protocol handshake and a JSON-RPC response listing all 7 tools (5 read + 2 write).

Development

npm test            # run the full test suite once (~250ms, 86 tests)
npm run test:watch  # watch mode for active development
npm run typecheck   # strict TypeScript check across src/ + api/
npm run build       # compile to dist/
npm run verify      # typecheck + test + build, in that order

The suite covers content integrity (slug uniqueness, enum coverage), each of the 7 tool handlers (happy paths + schema-rejection paths), the HubSpot client (mocked fetch exercising the upsert POST → 409-fallback GET → PATCH chain), and a full end-to-end MCP protocol handshake using the SDK's InMemoryTransport (verifies the same code that runs over stdio and over HTTP works in-process).

GitHub Actions runs npm run verify on every push to main and on every PR — see .github/workflows/test.yml.

Architecture

src/
├── index.ts                          ← Entry point. McpServer + stdio transport.
├── content/                          ← Source of truth for Agrus content.
│   ├── services.ts                   ← 6 service pillars + descriptions.
│   ├── verticals.ts                  ← 7 verticals + compliance pins.
│   ├── compliance-regimes.ts         ← 7 regulatory regimes + Agrus position.
│   ├── case-studies.ts               ← NDA-protected codenamed case studies.
│   └── pricing.ts                    ← Published pricing tiers.
└── tools/
    ├── index.ts                      ← Tool registration table.
    ├── list-services.ts
    ├── list-verticals.ts
    ├── query-compliance-position.ts
    ├── get-case-study.ts
    └── scope-poc.ts

Each tool defines a Zod inputSchema (a ZodRawShape) and a handler function returning MCP content. Tools are wired into the server via the registration table in tools/index.ts — adding a sixth tool means writing one new file + one entry in the registration table.

Why this exists

In 2026, more buyer research is done by AI agents acting on behalf of humans. A CIO using her internal Claude assistant can ask "find me three AI consultancies that do self-hosted HIPAA-compliant deployments and book intros." If we are MCP-discoverable, we participate in that conversation. If we aren't, we're invisible to that buyer type.

This is also the deepest layer of Agrus's brand differentiation: we are an AI agency that has invested in being engageable by AI agents. The MCP server is what we point to when prospects ask "are you AI-first or are you using the marketing term?"

Roadmap

Phase 1 (this release)

• 5 read-only tools (list_services, list_verticals, query_compliance_position, get_case_study, scope_poc)
• Stdio transport for local MCP clients (Claude Desktop, Continue.dev, etc.)
• Open-source MIT release

Phase 2 (next)

• HTTP+SSE transport for hosting at mcp.agrus.ai
• Vercel deployment (matches the marketing-site stack)
• Well-known manifest at /.well-known/mcp.json
• Write tools with email-OTP verification:
  • request_quote — ballpark price band, no commitment
  • request_proposal — triggers formal proposal workflow + HubSpot lead with agrus_lead_source=agrus_mcp
  • book_consultation — Google Calendar handoff + HubSpot upsert + Slack alert
• Rate limiting (Upstash Redis)
• Submission to Anthropic MCP directory + awesome-mcp lists

Phase 3 (later)

• Customer-scoped API-key authentication
• check_engagement_status for existing-customer AI agents
• npm package (@agrus/mcp-server)
• Open-sourced HTTP transport layer as a reference implementation

Contributing

Issues and PRs welcome. The content modules (src/content/*.ts) are the easiest place to contribute — corrections, new compliance regimes, better case-study codenames. Larger changes (new tools, new transports) should open an issue first to discuss.

Related

• Agrus.ai — the agency website this server represents
• Ethora — our open chat + AI agent SDK; the Agrus site runs on it
• Model Context Protocol — the open protocol this server speaks
• @modelcontextprotocol/sdk — Anthropic's official TypeScript SDK we use

License

MIT — see LICENSE. Copyright (c) 2026 Dappros Ltd.