Back in May I wrote about my Zerto Docs MCP server, the thing that lets Claude, Copilot, or Cursor answer Zerto questions straight from help.zerto.com with citations. It works well, but it has one catch: you need an AI client that speaks MCP, and you need to know how to add a custom connector to it. That’s a lot of setup for someone who just wants to know whether their Hyper-V hosts are supported in 10.9.
So I put a chat window in front of it. It’s at chat.jpaul.me, and I call it chatJPt. Yes, the name is a pun. Sorry, not sorry.:)
Disclaimer up front
This is a personal side project. It’s not a Zerto or HPE product, it’s not supported by Zerto or HPE, and it’s not endorsed by my employer. Everything it knows comes from publicly available documentation, the same pages anyone can read in a browser. No internal docs, no support tickets, no roadmap. It can be wrong, so verify anything important against the source page it links to, and test in non-production before you change anything in production.
What it is
You go to chat.jpaul.me, type your email, and click the sign-in link it sends you. No password, no account to set up. Then you ask a question the way you’d ask a coworker who has read every doc.
Behind the chat window, Claude Sonnet 5.5 searches the same docs MCP servers I’ve been building, pulls the relevant pages, and writes an answer with links back to the exact pages it used. It’s version-aware: tell it you’re on Zerto 10.8 or Morpheus 9.0.1 and it scopes the search to those docs.
A few other things it does:
- Keeps your chats in a sidebar so you can come back to them.
- Exports any answer to Word or PDF, which is handy for dropping a procedure into a change ticket.
- Puts a copy button on every code block, because nobody wants to hand-select a PowerShell snippet.
What it can answer questions about
When I first built it, chatJPt only knew Zerto. As of this week it covers four HPE products, about 29,400 pages of documentation in total:
- Zerto: 22,318 pages across 373 doc bundles. Install and admin guides, release notes, API references, the KB archive, and the interoperability matrix, refreshed every week.
- HPE Morpheus Enterprise: 3,265 pages of user manuals and release notes, including the 9.0.x releases.
- HPE Morpheus VM Essentials (HVM): 2,450 pages, including the user manual, the deployment guide, release notes, and the qualification matrix for HVM clusters.
- HPE OpsRamp: 1,366 pages covering integrations, platform features, solutions, support articles, and the 2026 release notes.
The part I like most is that it can cross products in one question. I asked it “Can Zerto protect VMs running on HPE Morpheus VM Essentials? Which versions are supported?” It searched the Zerto docs and the HVM docs, then came back with a feature table (cross-platform replication between VMware and HVM, failover tests, moves from VMware to HVM, three of those new in Zerto 10.9), the Morpheus version requirement, the ZVM appliance sizing, and these sources at the bottom:
Those links go to the actual help pages, so you can check its work. Please do.
Some other questions worth trying:
- “What’s new in Zerto 10.9?”
- “How do I add a VMware vCenter cloud in Morpheus?”
- “What are the minimum host requirements for an HVM cluster?”
- “How do I install the OpsRamp NextGen gateway?”
- “Can OpsRamp monitor HPE Morpheus VM Essentials hosts?”
- “Create a POC guide for Zerto on Morpheus Essentials from Hardware requirements to VPG failover test.”
The first problem was a naming collision. All four docs servers expose a tool called search_docs, plus get_page, list_versions, and a few others. Hand Claude four tools with the same name and it has no way to tell which product it’s searching. The fix was to prefix every tool with its product (zerto__search_docs, hvm__search_docs, and so on) and route each call back to the right server.
The second one took the site down. The app’s Python requirements only set minimum versions, so when it rebuilt, it pulled the brand-new 2.x release of the MCP Python SDK. That release renamed a function the app imports, and the container crashed on startup. chat.jpaul.me returned 502 errors for about four minutes, until the previous image was rolled back into place. I did this work with Claude Code. It was fast, and it was also the one that shipped that change without testing the freshly built image first. To its credit, it spotted the crash and did the rollback in those same four minutes. Since then every image gets built and tested against the real docs servers before it merges, and the app now runs on the current 2.x SDK.
The third was smaller and a little embarrassing. I built the OpsRamp docs server from the same template as the HVM one, and several of its tool descriptions still said “HVM docs.” Claude didn’t get confused because chatJPt labels each tool by product, but anyone connecting to that server directly saw the wrong text. That’s fixed.
Want it in your own AI client instead?
The chat site is the easy path, and there’s a monthly usage limit per person to keep my Anthropic bill sane. If you live in Claude Desktop, Claude Code, Copilot, or Cursor already, you can skip the website and connect the docs servers directly. They’re public, no auth required:
Zerto: https://mcp.jpaul.io/metamcp/zerto-docs/mcp
HPE Morpheus Enterprise: https://mcp.jpaul.io/metamcp/morpheus-docs/mcp
HPE Morpheus VM Essentials: https://mcp.jpaul.io/metamcp/hvm-docs/mcp
HPE OpsRamp: https://mcp.jpaul.io/metamcp/opsramp-docs/mcpThe setup steps for each client are in the original Zerto Docs MCP post. Swap in whichever URL you need.
What’s next
I’d like to know what it gets wrong. If chatJPt gives you a bad answer, or misses a page you know exists, email me at [email protected] with the question you asked. That’s the fastest way for me to find gaps in the search. And if there’s another product’s docs you’d want in here, tell me that too.
Go ask it something: chat.jpaul.me.
