Skip to content

Grok Propertyware MCP by usefulapi propertyware_list_lease_notes

How to: Grok Propertyware MCP by usefulapi propertyware_list_lease_notes

client:Grok transport:streamable-http tool:propertyware_list_lease_notes

Add Propertyware MCP by usefulapi to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "propertyware": {
      "type": "http",
      "url": "https://propertyware.usefulapi.io/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    Ask for something propertyware_list_lease_notes does. Grok lists the server's tools on connect and calls propertyware_list_lease_notes itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Propertyware MCP by usefulapi's identifier in your config matches the one above exactly.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.