Skip to content

n8n

n8n can talk to the Estaite MCP server in two ways:

  1. The MCP Client node (n8n 1.69+), which speaks Streamable HTTP MCP directly.
  2. A plain HTTP Request node that calls the JSON-RPC endpoint by hand.

Use the MCP Client node when you can — it discovers the tool catalog automatically.

Prerequisites

Option A — MCP Client node

  1. Add an MCP Client node to your workflow.
  2. Set:
    • Transport: HTTP
    • URL: https://mcp.estaite.com
    • Headers: add x-api-key with your API key as the value.
  3. Pick the operation (e.g. List Tools to verify the connection, or Execute Tool to call one of the 13 tools).
  4. For Execute Tool, set the tool name (e.g. query_estaite_submarket_index) and the tool arguments as JSON.

Option B — HTTP Request node

For older n8n versions, call the MCP tools/call JSON-RPC method directly:

  • Method: POST
  • URL: https://mcp.estaite.com
  • Headers:
    • Content-Type: application/json
    • Accept: application/json, text/event-stream
    • x-api-key: YOUR_API_KEY
  • Body (JSON):
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_estaite_submarkets",
"arguments": { "query": "Carmel Valley" }
}
}

The response body is a JSON-RPC envelope with result.content[0].text containing the JSON payload. Parse that string in a Set or Code node to get the structured result.

Use it

Common workflow patterns:

  • Lead enrichment — given a ZIP, look up get_estaite_zip_metrics and attach the result to the lead.
  • Daily watch — schedule find_estaite_submarkets_by_criteria and email the result to a Slack channel.
  • Comparable shortlist — input a submarket id, call get_estaite_comparable_markets, format as Markdown.

Troubleshooting

  • 401 — the API key is wrong or revoked.
  • 429 — you hit the per-second rate limit (Free is 2 req/s). Add a Wait node or upgrade your tier.