[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Spectora API and MCP server: Let your AI agent book and chase your inspections. > Spectora has an official MCP server, the AI Connector, and a public API (checked 28 Oct 2026). The connector's 10 tools read agents, clients, inspections, attachments and events for a company admin, and Spectora says it "cannot book, edit, or delete anything". The API also writes client and agent records and uploads attachments, but "can't schedule inspections, make calendar changes, or edit reports". Cotlet runs 11 Spectora tools hosted, 4 of them writes, over MCP for agents and REST for scripts. Schedule inspections, add agreements and read agents and clients in Spectora. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST. [MCP setup](https://cotlet.dev/integrations/spectora-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/spectora-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Spectora - Page: https://cotlet.dev/integrations/spectora-api-mcp-server ## What can you automate in Spectora? - Book inspections from requests - Reschedule and notify the client - Chase unsigned agreements - Add a missing agreement to a job - Report which agents sent you work - Send the report link once it is published ## Does Spectora have an MCP server or an API? - Both come with every paid Spectora plan at no extra cost. API writes need the standard API plan; the free API plan gives 500 read requests a month and answers 403 to a write. - Agreements and sharing the client portal have no endpoint at all. Report content "isn't available to read". - Zapier and webhooks need Spectora Advanced ($4 per inspection). Zapier has 4 triggers on new or changed agent and client contacts and no actions. | What you need | AI Connector | Spectora API | Cotlet | |---|---|---|---| | Read inspections, agents and clients | Yes, company admin | Yes | Yes, as your role sees | | Book or reschedule an inspection | No | No | Yes, after your OK | | Add an agreement, share the client portal | No | No | Yes, after your OK | | Create and update agent and client records | No | Yes, standard API plan | Client inside a new booking | | Report link | No | Not found | Link only, no findings | | Allowed by Spectora | Yes, official | Yes, official | Uses the web app | Checked 28 Oct 2026. Sources: [Spectora: AI Connector (MCP) and API](https://www.spectora.com/integrations-mcp-api), [Spectora Developer: MCP server](https://developer.spectora.com/mcp-server), [Spectora Help: What is the MCP Server?](https://support.spectora.com/en/articles/15466037-what-is-the-mcp-server), [Spectora Help: Using the Zapier Integration](https://support.spectora.com/en/articles/5949874-using-the-zapier-integration), [Spectora API overview and quota](https://developer.spectora.com/spectora-api-overview), [Spectora pricing](https://www.spectora.com/pricing/) ## How does Cotlet connect to Spectora? 1. **Sign in to Spectora.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Spectora password, and no booking, reschedule or portal link goes out to a client until you approve it. ## Connect Spectora to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Enable Spectora for agents.** Make a Cotlet account, log in to Spectora in its Cloud Browser as the user the agent should act as, and press Enable for agents. 2. **Add the Cotlet address.** Give your agent https://cotlet.dev/mcp/v1 as a remote MCP server or custom connector. 3. **Confirm the connection.** Chat apps send you through a Cotlet sign-in. Editors, n8n and scripts use an API key from the console. `https://cotlet.dev/mcp/v1` is one address for all your apps, Spectora among them. You can keep Spectora's own connector next to it for its ready-made reports. Turned Spectora on after connecting? Refresh the connector to see its tools. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-spectora \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-spectora": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-spectora] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: spectora_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: spectora_write ``` ## How to use the Spectora REST API ### Create your Cotlet API key Create a Cotlet API key with access to Spectora and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect Spectora in Cotlet and enable it for agents. Account access: Your own Spectora account (company admin for company-wide lists and settings, inspector for your own jobs). ### Make your first Spectora API request REST: ``` curl https://cotlet.dev/api/v1/spectora/inspections \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read inspections and apply the operation limits A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "spectora", "tool": "list_inspections", "result": { "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 } } ``` 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. `from`: First day, YYYY-MM-DD. `to`: Last day, YYYY-MM-DD. `cursor`: next_cursor from the previous page. Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination. ### Spectora workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Returns one inspection with its client, agents, services and agreements. Use `get_inspection` in your configured business report. | | Make | HTTP > Make a request | Lists upcoming inspections whose agreement the client has not signed. Use `list_unsigned_inspections` in your configured business report. | | Python or Node.js | REST API | Returns the report URL of a published inspection. Use `get_report_link` in your configured business report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Spectora; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/spectora-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Spectora API endpoints and MCP tools ### Inspections and the schedule Bookings and moves trigger the client emails your Automations set up. A new booking needs square feet and year built; when Spectora cannot look them up, the call fails and names what is missing. - **List inspections** (`list_inspections`, read): Lists inspections by date range, status, inspector or address. - **Get inspection** (`get_inspection`, read): Returns one inspection with its client, agents, services and agreements. - **Create inspection** (`create_inspection`, write, asks first): Creates an inspection in the internal scheduler. - **Reschedule inspection** (`reschedule_inspection`, write, asks first): Moves an inspection to a new date, time or duration. ### Agreements, portal and reports Agreement names must match your Services & Fees. The portal link shows the client's invoice, agreements and final report, so share it only with people who may see all three. - **List inspections with unsigned agreements** (`list_unsigned_inspections`, read): Lists upcoming inspections whose agreement the client has not signed. - **Add agreement to inspection** (`add_agreement`, write, asks first): Adds an agreement from your Services & Fees to an existing inspection. - **Share inspection details** (`share_inspection_details`, write, asks first): Sends the client portal link of an inspection to an email address. - **Get report link** (`get_report_link`, read): Returns the report URL of a published inspection. ### Agents and clients Read only. Detailed agent profiles are a Spectora Advanced feature, so some agent fields stay empty on the base plan. - **List agents** (`list_agents`, read): Lists agent contacts with their company and number of inspections. - **Get agent** (`get_agent`, read): Returns one agent with the inspections they are on. - **List clients** (`list_clients`, read): Lists client contacts and the inspections they are on. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/spectora-api-mcp-server#tools ## Who can see my Spectora session, and how do I revoke it? - **What we store.** Your logged-in Spectora profile, AES-256-GCM, in Finland. Not your password. - **What your agent gets.** The 11 Spectora tools. No cookie, no login. - **What the session sees.** What your Spectora role sees: jobs, clients, agents, fees. - **What no tool touches.** Payments, payouts, report editing, templates, settings and deleting. - **If Spectora logs you out.** Your agent gets a sign-in link for you. We never log in for you. - **How to cut access.** Disable for agents, reset the browser or delete the key. The next call stops. Our site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). No SOC 2 report or third-party pentest so far. ## Is it against Spectora's terms? Account safety > use bots, scrapers, crawlers, automated tools, or excessive requests to access, collect, or extract data from the Content without Spectora's express written permission > > [Spectora Terms of Use, section 10 (c), last updated 6 Aug 2026](https://www.spectora.com/terms/) Section 6 also lets Spectora close an account "for any reason". Cotlet acts in the Spectora web app as you, and Spectora can still count that as an automated tool. Spectora's own connector and API are the routes it allows, so use them for anything they cover. We found no public case of a Spectora account closed for automation (checked 28 Oct 2026). How we keep your account looking like you: - Your own Spectora login, entered by you - One Cloud Browser with its own IP and cookies - Bookings, moves, agreements and portal links wait for your OK - No tool deletes an inspection, a client or an agent - If Spectora objects, we pause the Spectora tools for everyone within 24 h > Every booking and move emails a client and often an agent. Book a busy morning's requests one by one, not as a burst, and keep reads to what the job needs. ## What happens when Spectora changes? - **12 h** between tests of the Spectora tools - **24 h** between tests of bookings and emails a client would get - **$0** for a call to a Spectora tool paused for repair If Spectora redesigns the New Inspection form or renames a field, the repair is ours. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the request.** Address, client, date, services and the agent. 2. **Checks the calendar.** Lists that day's jobs so nothing double-books. 3. **Waits for your OK.** The booking shows up in your Cotlet console first. 4. **Reports the job.** Inspection id, time and the agreements it pulled in. | Action | Undo | |---|---| | Book an inspection | Cancel it in Spectora; the booking email is already out | | Reschedule | Move it back; a second notice goes out unless you turn notifications off | | Add an agreement | No undo tool; change the job by hand in Spectora | | Share the portal link | No, the email is out | All 4 write tools ask first, because each one can email a client or an agent. The 7 reads run at once. Switch the wait off per tool for a scheduled run. > Reschedule can turn notifications off before the move, as the Internal box on Inspection Details does. MCP call: ``` { "name": "reschedule_inspection", "arguments": { "inspection_id": "insp_81f3", "starts_at": "2026-11-07T09:00:00", "duration_hours": 3 } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/spectora/inspections/insp_81f3/reschedule \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"starts_at":"2026-11-07T09:00:00","duration_hours":3}' ``` Response: ``` { "inspection_id": "insp_81f3", "starts_at": "2026-11-07T09:00:00", "duration_hours": 3, "notifications_sent": true } ``` Cron jobs and scripts call the same tools over REST at `/api/v1/spectora`, with one key and one price. A booking with a service name Spectora does not have fails at once and costs nothing. The tools table gives each tool's REST path. ## How much does the Spectora MCP server cost? **About $17 a month** for an inspection company booking about 25 jobs a month, 3,000 credits. Spectora still bills your plan as before. | Job | Calls | Credits | |---|---|---| | Book an inspection from a request | 2 × 25 | 500 | | Reschedule and notify the client | 2 × 5 | 100 | | Chase unsigned agreements, weekly | 4 × 4 | 160 | | Add a missing pest agreement, weekly | 4 × 4 | 160 | | Agent referral report, weekly | 2 × 4 | 80 | | Report link for a published inspection | 2 × 25 | 500 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,000 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No Spectora Advanced or API plan needed The month is our example of a one or two inspector company; Spectora publishes no jobs-per-account figure. Spectora itself costs $109 a month for the first inspector. Dollars at the $29 pack rate. ## Spectora MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [Spectora AI Connector](https://developer.spectora.com/mcp-server) | Official MCP at connect.spectora.com, 10 read tools and 14 ready-made reports such as Lapsed Agent Reactivation. | Reads only, company admin only. | | [Zapier](https://support.spectora.com/en/articles/5949874-using-the-zapier-integration) | Sends new and changed agent and client contacts to a CRM. | Spectora Advanced only, no inspections, no actions. | | [InspectorHub/OpenInspection](https://github.com/InspectorHub/OpenInspection) | Open-source inspection software that aims at parity with Spectora, 11 stars, active. | A replacement: you move your business off Spectora. | | [api-evangelist/spectora](https://github.com/api-evangelist/spectora) | A third-party profile of the public API. | Description only, no server. | We found no Spectora MCP server on GitHub. For reports and questions about your business, Spectora's free connector is the simpler pick. For syncing contacts into a CRM, the API or Zapier. For booking, moving jobs and chasing agreements from an agent, Cotlet. ## Who runs Cotlet Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), has run Cotlet since it started and has been in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Spectora tools go to contact@cotlet.dev. ## Spectora API and MCP: questions ### How do I get access? Sign up free at https://cotlet.dev, find Spectora under Integrations in the console and log in to Spectora in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect Spectora to ChatGPT or Claude? Sign up at cotlet.dev, log in to Spectora once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Spectora account through Cotlet, in their phone apps too. ### What can ChatGPT do in Spectora? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Spectora: book an inspection from a request; reschedule an inspection and tell the client; chase unsigned agreements. You ask in plain words, and anything that reaches other people waits for your OK first. ### Do I need an admin account or Spectora Advanced? No Advanced plan is needed for the tools here, but your role counts. The official connector needs company admin (Spectora, checked 28 Oct 2026). Cotlet works in your own session, so it sees what your role sees. Agent profiles and agent reports are Advanced features, so those fields can be empty on the base plan. ### What happens to the emails Spectora sends clients? They go out as your Automations say. Creating and rescheduling an inspection triggers the booking and reschedule notices, which is why those calls wait for your OK by default. Reschedule can turn notifications off first, as the Internal box does. ### Should I use Spectora's AI Connector instead? For questions, yes: it is free with a paid Spectora plan and comes with ready-made reports. It cannot book, edit or delete anything. Use Cotlet for the jobs that change the schedule or reach a client, and keep both connected if you like. ### Does Spectora have webhooks? Yes, for Spectora Advanced users, set up at developer.spectora.com. Webhook calls do not count toward the API quota. Cotlet does not use them; run your agent on a schedule, for example a daily list_unsigned_inspections pass. ### Is the MCP server different from the REST API? Only the way in differs. Both carry the same 11 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Spectora? No. Cotlet is independent and not affiliated with Spectora. ### Can I use the Spectora API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.