Spectora API and MCP server Let your AI agent book and chase your inspections.

ToolWhat it doesAccess

• list_inspections Lists inspections by date range, status, inspector or address. read

  Returns inspection_id, address, date and time, inspector, client name, services and the agreement state for each job, in the order Spectora lists them. Follow next_cursor until it is empty. Canceled inspections are included only when you search for them. The account sees the inspections its role allows.

  MCP callspectora_read → list_inspections

  REST endpointGET https://cotlet.dev/api/v1/spectora/inspections

  Parameters

  Parameters: list_inspections

  Name	Type	Description
  from string	string	First day, YYYY-MM-DD.
  to string	string	Last day, YYYY-MM-DD.
  search string	string	Address or client name, as in the Inspections search.
  inspector string	string	Inspector name, as shown in Spectora.
  cursor string	string	next_cursor from the previous page.

  Example response

  {
    "inspections": [
      {
        "inspection_id": "insp_81f3",
        "address": "14 Maple Street, Springfield",
        "starts_at": "2026-11-03T09:00:00",
        "inspector": "Dana Whitt",
        "client": "Priya Nair",
        "services": [
          "Home Inspection"
        ],
        "agreements_signed": false
      }
    ],
    "next_cursor": null
  }

• get_inspection Returns one inspection with its client, agents, services and agreements. read

  Reads the Inspection Details page. It returns the address, time, services, agreements with their signed state, the client, the buyer's and listing agent, and notes. Report content is not returned, only the link from get_report_link.

  MCP callspectora_read → get_inspection

  REST endpointGET https://cotlet.dev/api/v1/spectora/inspections/{inspection_id}

  Parameters

  Parameters: get_inspection

  Name	Type	Description
  inspection_id string required	string	Id from list_inspections.

  Example input

  {
    "inspection_id": "inspection_8c41d2"
  }

  Example response

  {
    "inspection_id": "insp_81f3",
    "address": "14 Maple Street, Springfield",
    "starts_at": "2026-11-03T09:00:00",
    "inspector": "Dana Whitt",
    "client": {
      "name": "Priya Nair",
      "email": "priya@example.com"
    },
    "buyer_agent": "Marcus Lee",
    "listing_agent": "Elena Cruz",
    "services": [
      "Home Inspection"
    ],
    "agreements": [
      {
        "name": "Pre-Inspection Agreement",
        "signed": false
      }
    ]
  }

• create_inspection Creates an inspection in the internal scheduler. writeasks first

  Fills the New Inspection form and saves it. Choosing a service pulls in the templates, agreements and fees set up for it, and Spectora then sends the client the booking email with the sign and pay link as your Automations say. The address needs square feet and year built; when Spectora cannot look them up, the call fails and lists what is missing. A service name Spectora does not have fails at once. By default you confirm each call; you can switch that off for this tool.

  MCP callspectora_write → create_inspection

  REST endpointPOST https://cotlet.dev/api/v1/spectora/inspections

  Parameters

  Parameters: create_inspection

  Name	Type	Description
  address string required	string	Street address, city and state.
  starts_at string required	string	Local start time, ISO 8601.
  inspector string	string	Inspector name; defaults to the signed-in account.
  client_name string required	string	Client full name.
  client_email string required	string	Client email.
  services array required	array	Service names exactly as in Settings > Services.
  listing_agent_email string	string	Listing agent email.

  Example input

  {
    "address": "address",
    "starts_at": "starts at",
    "client_name": "client name",
    "client_email": "jane@example.com",
    "services": "services"
  }

  Example response

  {
    "inspection_id": "insp_81f3",
    "status": "scheduled",
    "address": "14 Maple Street, Springfield",
    "starts_at": "2026-11-03T09:00:00",
    "agreements": [
      "Pre-Inspection Agreement"
    ]
  }

• reschedule_inspection Moves an inspection to a new date, time or duration. writeasks first

  Does what Reschedule does on Inspection Details, also for a canceled inspection. Unless you turn notifications off, Spectora sends the reschedule notices, re-queues reminders and updates the agreements to the new date. With Trigger Once on, a second reschedule does not send again. Deleted inspections cannot be rescheduled. By default you confirm each call; you can switch that off for this tool.

  MCP callspectora_write → reschedule_inspection

  REST endpointPOST https://cotlet.dev/api/v1/spectora/inspections/{inspection_id}/reschedule

  Parameters

  Parameters: reschedule_inspection

  Name	Type	Description
  inspection_id string required	string	Id from list_inspections.
  starts_at string required	string	New local start time, ISO 8601.
  duration_hours number	number	New length in hours.
  disable_notifications boolean	boolean	Turn off all notifications before moving, as in the Internal box.

  Example input

  {
    "inspection_id": "insp_81f3",
    "starts_at": "2026-11-07T09:00:00",
    "duration_hours": 3
  }

  Example response

  {
    "inspection_id": "insp_81f3",
    "starts_at": "2026-11-07T09:00:00",
    "duration_hours": 3,
    "notifications_sent": true
  }

ToolWhat it doesAccess

• list_unsigned_inspections Lists upcoming inspections whose agreement the client has not signed. read

  Reads the same unsigned-jobs view Spectora has in its business reports. Each row has the inspection_id, client, date and the names of the agreements still unsigned, soonest inspection first. It reports agreements only.

  MCP callspectora_read → list_unsigned_inspections

  REST endpointGET https://cotlet.dev/api/v1/spectora/unsigned-inspections

  Parameters

  Parameters: list_unsigned_inspections

  Name	Type	Description
  from string	string	First day, YYYY-MM-DD.
  to string	string	Last day, YYYY-MM-DD.

  Example response

  {
    "inspections": [
      {
        "inspection_id": "insp_81f3",
        "client": "Priya Nair",
        "starts_at": "2026-11-03T09:00:00",
        "unsigned_agreements": [
          "Pre-Inspection Agreement"
        ]
      }
    ]
  }

• add_agreement Adds an agreement from your Services & Fees to an existing inspection. writeasks first

  Uses Add Agreement in the Agreements box of Inspection Details. The agreement shows as unsigned until the client signs it in the Client Portal. A name that is not in the dropdown fails and lists the available agreements. By default you confirm each call; you can switch that off for this tool.

  MCP callspectora_write → add_agreement

  REST endpointPOST https://cotlet.dev/api/v1/spectora/inspections/{inspection_id}/agreements

  Parameters

  Parameters: add_agreement

  Name	Type	Description
  inspection_id string required	string	Id from list_inspections.
  agreement string required	string	Agreement name exactly as in the dropdown.

  Example input

  {
    "inspection_id": "inspection_8c41d2",
    "agreement": "agreement"
  }

  Example response

  {
    "inspection_id": "insp_81f3",
    "agreement": "Pest Agreement",
    "signed": false
  }

• share_inspection_details Sends the client portal link of an inspection to an email address. writeasks first

  Uses Share Details. The recipient gets the client portal link, which shows what the client sees: the invoice, the agreements and the final report. Send it only to people who may see all of that. By default you confirm each call; you can switch that off for this tool.

  MCP callspectora_write → share_inspection_details

  REST endpointPOST https://cotlet.dev/api/v1/spectora/inspections/{inspection_id}/details/share

  Parameters

  Parameters: share_inspection_details

  Name	Type	Description
  inspection_id string required	string	Id from list_inspections.
  email string required	string	Recipient email.

  Example input

  {
    "inspection_id": "inspection_8c41d2",
    "email": "jane@example.com"
  }

  Example response

  {
    "inspection_id": "insp_81f3",
    "shared_with": "priya@example.com",
    "sent": true
  }

• get_report_link Returns the report URL of a published inspection. read

  Returns the URL behind View next to the report name on the Inspection Details page, and whether the report is published. It returns the link only, never the findings. Spectora does not send reports to the listing agent, so sharing this link with them is your decision.

  MCP callspectora_read → get_report_link

  REST endpointGET https://cotlet.dev/api/v1/spectora/inspections/{inspection_id}/report-link

  Parameters

  Parameters: get_report_link

  Name	Type	Description
  inspection_id string required	string	Id from list_inspections.

  Example input

  {
    "inspection_id": "inspection_8c41d2"
  }

  Example response

  {
    "inspection_id": "insp_81f3",
    "published": true,
    "report_url": "https://app.spectora.com/reports/example-report"
  }

ToolWhat it doesAccess

• list_agents Lists agent contacts with their company and number of inspections. read

  Returns agent_id, name, company, email, phone and the count of your inspections that agent is on. Agents come in the order of the Agents list. Follow next_cursor to the end.

  MCP callspectora_read → list_agents

  REST endpointGET https://cotlet.dev/api/v1/spectora/agents

  Parameters

  Parameters: list_agents

  Name	Type	Description
  search string	string	Name, company or email.
  cursor string	string	next_cursor from the previous page.

  Example response

  {
    "agents": [
      {
        "agent_id": "agt_204",
        "name": "Marcus Lee",
        "company": "Hillside Realty",
        "email": "marcus@example.com",
        "inspections": 11
      }
    ],
    "next_cursor": null
  }

• get_agent Returns one agent with the inspections they are on. read

  Returns the agent profile and their inspections, newest first. Detailed agent profiles and agent reports are a Spectora Advanced feature, so fields only filled there come back empty on the base plan.

  MCP callspectora_read → get_agent

  REST endpointGET https://cotlet.dev/api/v1/spectora/agents/{agent_id}

  Parameters

  Parameters: get_agent

  Name	Type	Description
  agent_id string required	string	Id from list_agents.

  Example input

  {
    "agent_id": "agent_8c41d2"
  }

  Example response

  {
    "agent_id": "agt_204",
    "name": "Marcus Lee",
    "company": "Hillside Realty",
    "email": "marcus@example.com",
    "inspections": [
      {
        "inspection_id": "insp_81f3",
        "starts_at": "2026-11-03T09:00:00"
      }
    ]
  }

• list_clients Lists client contacts and the inspections they are on. read

  Returns client_id, name, email, phone and the addresses of their inspections. Follow next_cursor to the end of the list.

  MCP callspectora_read → list_clients

  REST endpointGET https://cotlet.dev/api/v1/spectora/clients

  Parameters

  Parameters: list_clients

  Name	Type	Description
  search string	string	Name, email or address.
  cursor string	string	next_cursor from the previous page.

  Example response

  {
    "clients": [
      {
        "client_id": "cli_552",
        "name": "Priya Nair",
        "email": "priya@example.com",
        "inspections": [
          "14 Maple Street, Springfield"
        ]
      }
    ],
    "next_cursor": null
  }