Heeler RV ElectricalTechnical resources

HEELER RV · AGENT CONNECTION

Connect your AI agent to Heeler RV.

Give a compatible agent direct access to public service information and documented RV field evidence. Each field record includes its source, evidence status and limitations.

Remote MCP endpoint
https://heelerrv.com/mcp
Transport
Streamable HTTP · JSON responses · stateless
Authentication
None required for these public, read-only tools
Supported protocol versions
2026-07-28 · 2025-11-25 · 2025-06-18 · 2025-03-26

What an agent can do

This connection reads public information. It does not access customer records, submit inquiries, send messages, run the calculators, provide binding quotes, book appointments or place orders.

Connect and try it

  1. In a client that supports custom remote MCP servers, add the endpoint above using Streamable HTTP and no authentication.
  2. Ask the client to list the available tools, then ask: “Does Heeler RV serve Kelowna, and what information should I prepare for an electrical review?”
  3. Try: “Find the Jayco Talon field record. Explain what was documented and what still has not been measured, with a link to the source.”

The MCP endpoint accepts protocol requests by POST. Opening it as a normal webpage returns a method-not-allowed response; use this page for instructions. Client support and connection controls vary. Publishing this endpoint does not automatically install Heeler RV in an AI assistant or guarantee recommendations.

From research to an electrical inquiry

An agent can help prepare the RV details and questions. Review those details, then submit through the existing inquiry form with your contact permission. Heeler RV confirms the work, availability and price.

Using the evidence correctly

Preserve unknowns and distinguish equipment ratings from measured results. One trailer's wiring is not a factory specification for every trailer with the same model name. Cite the linked field record when using its findings.

Developer reference: MCP Streamable HTTP. For a browser-hosted client, its exact origin must be allowed by the server; server-to-server clients normally omit Origin. Send only tool arguments, not private customer details.