io.github.phwizardPublished by GitHub account phwizardv0.2.0Updated Oct 27, 2026
AI consulting agency for regulated industries. Scope a PoC, query compliance, request a proposal.
Lets an assistant browse Agrus.ai's AI consulting services, verticals, compliance positions and case studies, and draft a PoC scope or request a proposal.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
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/io.github.phwizard%2Fmcp-agrus-ai/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.Add this to your client's mcpServers config.
{
"mcpServers": {
"agrus-ai-enterprise-ai-agency": {
"type": "http",
"url": "https://mcp.agrus.ai/mcp"
}
}
}[Test] [License: MIT] [Node] [MCP]
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.
All tools return structured JSON inside an MCP text content block. No authentication required for Phase 1 tools.
NodeNext resolution)The built entry point is dist/index.js (executable, #!/usr/bin/env node shebang).
No global install needed. npx fetches the latest published version and runs it over stdio.
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:
For Claude Desktop and other clients that prefer stdio:
Claude Desktop config path on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json.
For development against a local checkout:
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.
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.
Send raw MCP protocol messages over stdio:
You should see the protocol handshake and a JSON-RPC response listing all 7 tools (5 read + 2 write).
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.
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.
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?"
mcp.agrus.ai/.well-known/mcp.jsonrequest_quote — ballpark price band, no commitmentrequest_proposal — triggers formal proposal workflow + HubSpot lead with agrus_lead_source=agrus_mcpbook_consultation — Google Calendar handoff + HubSpot upsert + Slack alertawesome-mcp listscheck_engagement_status for existing-customer AI agents@agrus/mcp-server)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.
MIT — see LICENSE. Copyright (c) 2026 Dappros Ltd.
Source: README.md at commit e0ffe7f
Lists Agrus's six service pillars with descriptions, deliverables, and price bands. Plus the four published pricing tiers (Scoping Call, Discovery Sprint, Build Engagement, Managed SLA). Use this for the 'what does Agrus do?' question.
verticalLists Agrus's seven year-one verticals (healthcare, insurance, legal, private equity, family offices, corporate intelligence, pro sports) with compliance pins, sample use cases, and the sequencing rationale. Use this for the 'do they work in my industry?' question.
Takes no parameters.
Returns Agrus's documented position on a specific regulatory regime (HIPAA, SOC 2, ISO 27001, EU AI Act, NAIC, ABA Model Rules, AML/KYC) as it applies to a described AI use case. Includes key controls, common gotchas, the first question Agrus would ask, and the agency's reference architecture for the regime. Use this when a buyer-side AI agent is evaluating Agrus's compliance fluency.
regimerequireduse_caserequireddata_typesReturns one or more Agrus case studies (NDA-protected; customer names are kept private, codenames + technology + outcomes are open). Filter by slug or vertical, or call with no args to list all. Use this for proof of prior work.
slugverticalDrafts a structured Discovery Sprint scope for an AI use case. Returns a 3-week plan, team composition, price band, follow-on Build Engagement estimate, open questions Agrus would ask, and recommended services. Use this to convert a hypothetical use case into a concrete engagement proposal that can be reviewed by a human buyer.
use_caserequiredverticalrequireddata_typestimeline_hinttarget_outcomescompliance_constraintsReturns a heuristic ballpark price band for the described AI deployment. Output is NOT a binding offer — Agrus confirms quotes only on a 30-minute scoping call. Read-only: this tool does not contact Agrus or create any record. For a tracked, follow-up-able request use request_proposal instead. Use request_quote when the buyer wants order-of-magnitude pricing before committing to a real proposal.
summaryrequiredurgencyverticalrequiredcompliance_constraintsTriggers a formal Agrus proposal workflow. Creates a contact in Agrus's HubSpot CRM tagged with lead source 'agrus_mcp' and a verbatim note containing the scope summary. A human at Agrus replies by email within 24 hours (business days) with a one-paragraph engagement recommendation and a calendar option. Use this when the buyer (human or AI agent acting on their behalf) wants to formally engage Agrus — not for exploratory scoping.
rolecompanyrequiredurgencyverticalrequiredcontact_namerequiredcontact_emailrequiredscope_summaryrequiredpersona_contextcompliance_constraints100% 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.
git clone https://github.com/phwizard/mcp-agrus-ai.gitcd mcp-agrus-ainpm installnpm run buildnpx -y mcp-agrus-ai{ "mcpServers": { "agrus": { "url": "https://mcp.agrus.ai/mcp" } }}{ "mcpServers": { "agrus": { "command": "npx", "args": ["-y", "mcp-agrus-ai"] } }}{ "mcpServers": { "agrus": { "command": "node", "args": ["/absolute/path/to/mcp-agrus-ai/dist/index.js"] } }}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.jsnpm test # run the full test suite once (~250ms, 86 tests)npm run test:watch # watch mode for active developmentnpm run typecheck # strict TypeScript check across src/ + api/npm run build # compile to dist/npm run verify # typecheck + test + build, in that ordersrc/├── 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