HouseCall Pro MCP icon

HouseCall Pro MCP

Interact with HouseCall Pro via MCP Server
Join our community

Overview

This node allows interaction with the HouseCall Pro system via a custom MCP (Microservice Control Protocol) server. It supports three main operations: listing available tools, calling a specific tool with arguments, and listing resources. This is useful for automating workflows that integrate with HouseCall Pro functionalities exposed through the MCP server.

Typical use cases include:

  • Retrieving a list of available tools or resources from the MCP server to dynamically build further automation.
  • Executing specific tools on the MCP server by passing JSON-formatted arguments, enabling complex interactions with HouseCall Pro services.
  • Integrating HouseCall Pro capabilities into broader n8n workflows without direct API calls, relying instead on the MCP server as an intermediary.

Properties

Name Meaning
MCP Server URL The URL endpoint of your HouseCall Pro MCP Server where requests will be sent.
MCP Method The operation to perform:
- List Tools
- Call Tool
- List Resources
Tool Name (Required if "Call Tool" selected) The name of the tool to invoke on the MCP server.
Tool Arguments (Required if "Call Tool" selected) JSON object containing arguments to pass to the tool.

Output

The node outputs an array with one item per input item processed. Each output item contains a json field with the response from the MCP server:

  • For List Tools and List Resources, the response typically includes arrays or objects describing available tools or resources.
  • For Call Tool, the response contains the result of executing the specified tool with the provided arguments.
  • If an error occurs during the request, and the node is configured to continue on failure, the output's json will contain an error field with the error message.

No binary data is produced by this node.

Dependencies

  • Requires access to a running HouseCall Pro MCP Server reachable at the specified URL.
  • No direct API keys or credentials are handled by this node; authentication must be managed by the MCP server or network configuration.
  • The node uses HTTP POST requests with JSON-RPC 2.0 format to communicate with the MCP server.

Troubleshooting

  • Common issues:

    • Incorrect MCP Server URL leading to connection failures.
    • Malformed JSON in "Tool Arguments" causing parsing errors.
    • Calling a tool name that does not exist or is misspelled.
    • MCP server returning an error response due to invalid parameters or internal errors.

  • Error messages:

    • "Error from MCP server: <message>": Indicates the MCP server responded with an error. Check the tool name, arguments, and server logs.
    • JSON parsing errors when entering tool arguments: Ensure the JSON is valid and properly formatted.
    • Network errors or timeouts: Verify the MCP Server URL and network connectivity.

  • To handle errors gracefully, enable the node’s "Continue On Fail" option to capture errors in the output rather than stopping workflow execution.

Links and References

Discussion