opsdoctor-mcp

MCPcommunity
v2.1.0Resolution AIApache-2.0Updated 1d agonpmGitHub

AI-powered operations diagnostic and workflow audit MCP server for SMB consulting — CRM diagnostics, multi-stage workflow audits, industry knowledge base, and branded PDF reports

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
111Downloads/wk
1d agoLast update
Needs 2 credentials before it runs
  • GEMINI_API_KEYAPI keyrequired

    Google Gemini API key for AI-powered diagnostics and audits

  • OPSDOCTOR_KB_API_KEYAPI keyrequired

    API key for authenticating with the OpsDoctor knowledge base API

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorResolution AI
LicenseApache-2.0
Version2.1.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv2.1.0 · todayHow well does this scan work?
EvalsNone
IndexedSep 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev2.1.0 · 3h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_audit_historyRetrieve past diagnostic and audit results. Filter by client name, result type, or limit. Returns structured history entries with IDs that can be used with generate_report to produce branded PDFs.

Retrieve past diagnostic and audit results. Filter by client name, result type, or limit. Returns structured history entries with IDs that can be used with generate_report to produce branded PDFs.

No input schema was published for this tool.

run_diagnosticDiagnose a CRM or operational issue using AI. Provide the CRM name, symptoms, and optionally industry and company context. When an industry is specified, the diagnostic incorporates industry-specific knowledge (common systems, red flags, technology stack). Returns root causes, step-by-step fixes, v…

Diagnose a CRM or operational issue using AI. Provide the CRM name, symptoms, and optionally industry and company context. When an industry is specified, the diagnostic incorporates industry-specific knowledge (common systems, red flags, technology stack). Returns root causes, step-by-step fixes, v…

No input schema was published for this tool.

generate_reportGenerate a branded PDF report from a diagnostic or audit result. Provide an audit_id to load from history, or pass inline result data. Saves the PDF to disk and returns the file path.

Generate a branded PDF report from a diagnostic or audit result. Provide an audit_id to load from history, or pass inline result data. Saves the PDF to disk and returns the file path.

No input schema was published for this tool.

guided_auditRun a guided workflow audit through a structured multi-stage discovery process. Stages: "start" returns intake questions, "assess" scores the workflow, "followup" does a deep-dive, "complete" persists the final result. Each stage returns instructions for the next.

Run a guided workflow audit through a structured multi-stage discovery process. Stages: "start" returns intake questions, "assess" scores the workflow, "followup" does a deep-dive, "complete" persists the final result. Each stage returns instructions for the next.

No input schema was published for this tool.

query_knowledge_baseLook up discovery questions, green/red flag guides, conversation scripts, technology stack references, data governance guidance, and vendor management entries from the OpsDoctor knowledge base. Supports filtering by industry vertical and category. No AI call — instant keyword search over embedded c…

Look up discovery questions, green/red flag guides, conversation scripts, technology stack references, data governance guidance, and vendor management entries from the OpsDoctor knowledge base. Supports filtering by industry vertical and category. No AI call — instant keyword search over embedded c…

No input schema was published for this tool.

run_workflow_auditAudit an operational workflow. Supports 4 modes: "quick" (default) — single-pass AI audit returning score and recommendations. "intake" — returns 7 structured discovery questions to gather detailed workflow information (no AI call). "assess" — processes intake answers through AI for dimensional sco…

Audit an operational workflow. Supports 4 modes: "quick" (default) — single-pass AI audit returning score and recommendations. "intake" — returns 7 structured discovery questions to gather detailed workflow information (no AI call). "assess" — processes intake answers through AI for dimensional sco…

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

AI-powered operations diagnostic and workflow audit MCP server for SMB consulting — CRM diagnostics, multi-stage workflow audits, industry knowledge base, and branded PDF reports

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-11 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

63 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+51 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.