MCP server

The server lives at https://mcp.terminal.house/mcp and speaks the standard streamable-HTTP transport. Auth is the same bearer API key you use for REST — no separate key, no separate dashboard.

We expose 10 tools covering every read-mostly REST endpoint plus the watchlist lifecycle. Tools that touch parcels consume lead-views against the same monthly quota as REST; tools that touch watchlists and metadata are free. See Rate limits & quotas.

Quick test once configured — ask your agent:

// In Claude / Cursor / Windsurf with terminal.house MCP wired:> Use list_leads with recipe "oos_long_tenure_high_signal" and limit 5. // The agent calls the tool. Returns:{  "results": [    {      "folio":   "30-3122-008-0440",      "address": "4567 NW 22nd Av, Miami FL 33125",      "score":   0.78,      "signals_fired": ["out_of_state_owner", "tenure_years_long",                       "no_homestead", "code_violation"],      "observed_at": "2026-05-28T10:14:00Z"    }    // ...4 more  ],  "cursor": "eyJv...A3",  "total":  340}

Claude Desktop's MCP config file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows. Claude Desktop only speaks the stdio transport natively, so we proxy our streamable-HTTP endpoint through mcp-remote.

{  "mcpServers": {    "terminal.house": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.terminal.house/mcp",        "--header",        "Authorization: Bearer ${TERMINAL_HOUSE_API_KEY}"      ],      "env": {        "TERMINAL_HOUSE_API_KEY": "th_live_...your-key..."      }    }  }}

Restart Claude Desktop. The terminal.house tools appear under the wrench icon in the chat input.

Cursor's MCP config lives at ~/.cursor/mcp.json. Cursor speaks streamable-HTTP natively, so no proxy needed.

{  "mcpServers": {    "terminal.house": {      "url": "https://mcp.terminal.house/mcp",      "headers": {        "Authorization": "Bearer ${TERMINAL_HOUSE_API_KEY}"      },      "env": {        "TERMINAL_HOUSE_API_KEY": "th_live_...your-key..."      }    }  }}

Windsurf's MCP config lives at ~/.codeium/windsurf/mcp_config.json. Same streamable-HTTP transport as Cursor.

{  "mcpServers": {    "terminal.house": {      "serverUrl": "https://mcp.terminal.house/mcp",      "headers": {        "Authorization": "Bearer ${TERMINAL_HOUSE_API_KEY}"      }    }  }}

VS Code 1.99+ supports MCP servers natively through GitHub Copilot Chat. Add the server to your workspace at .vscode/mcp.json or globally via Command Palette → MCP: Add Server.

{  "servers": {    "terminal.house": {      "type": "http",      "url": "https://mcp.terminal.house/mcp",      "headers": {        "Authorization": "Bearer ${env:TERMINAL_HOUSE_API_KEY}"      }    }  }}

VS Code resolves ${env:TERMINAL_HOUSE_API_KEY} from your shell environment, so set the key in your shell rc or in the workspace's .env (don't commit it).

Any MCP-compliant client speaking streamable-HTTP works. Common combos:

• LangGraph — use langchain-mcp-adapters to mount the server as a tool group.
• Mastra — use @mastra/mcp to wire the server into your agent's tool registry.
• GPT custom tools / Assistants API — proxy via mcp-remote or call the REST surface directly with the same Bearer key.
• Custom MCP client — follow the MCP transport spec. Endpoint: POST https://mcp.terminal.house/mcp; Bearer auth in the Authorization header on every request.

Every tool's parameter shape is published in the MCP server's tools/list response — your client renders it natively (e.g. Claude Desktop shows it under the wrench icon; Cursor in the MCP panel). The summaries below cover the surface; deep-detail lives in the REST analogue at REST API · v1.