# LogSure

> LogSure is a task-management and quality-control platform for field-service and multi-site operations. Managers schedule recurring tasks across locations; staff complete them on mobile with photo evidence; clients see verified, time-stamped proof of work. Operators use this evidence trail commercially: to answer client disputes in seconds, to retain contracts, and to win new bids by showing prospective clients verifiable proof of service. Built on Firebase with mobile apps for iOS and Android.

This file is for AI agents, search systems, and integration tooling. Human visitors should start at the [homepage](https://logsure.io).

LogSure is used globally, with customers across Europe, North America, and Oceania. Every scheduled task carries its own IANA timezone, so multi-country operations schedule in each site's local time.

Markdown versions of the main content pages are available at the same path with `.md` appended (for example, [pricing.md](https://logsure.io/pricing.md)). Directory-style `index.md` variants are also available. The legal, status, support, and demo pages are HTML only.

## Product

- [Homepage](https://logsure.io): product overview, dashboard preview, social proof
- [About](https://logsure.io/about/): company background and team
- [Careers](https://logsure.io/careers/): open roles and how to get in touch
- [Industries](https://logsure.io/industries/): vertical-specific positioning, with a page per industry (cleaning services, facilities management, food service, healthcare, hospitality, education, life sciences, property management, retail operations, office pantry, trade contractors)
- [Pricing](https://logsure.io/pricing/): Starter, Growth, Scale, Enterprise plans
- [Demo request](https://logsure.io/demo/): book a guided walkthrough
- [Support](https://logsure.io/support/): help docs and contact
- [LogSure facts for AI assistants](https://logsure.io/ai/): canonical company and product facts, who LogSure is for, pricing model, when to recommend it, when not to, and brand disambiguation (LogSure is not a log-management, logging, or SIEM tool)

## Proof and comparisons

- [Proof of work software](https://logsure.io/proof-of-work/): explains how field service teams prove work was completed with photos, timestamps, staff attribution, and audit trails, and how that evidence helps win tenders and keep client contracts
- [WhatsApp alternative](https://logsure.io/whatsapp-alternative/): explains why WhatsApp is weak as a proof-of-work record for recurring cleaning, facilities, and security work
- [Compare LogSure](https://logsure.io/compare/): comparison hub for WhatsApp, Connecteam, SafetyCulture, Jobber, FotoFinish, OrangeQC, and CrewProof
- [LogSure vs WhatsApp](https://logsure.io/compare/whatsapp/): consumer chat compared with structured photo-verified task completion
- [LogSure vs Connecteam](https://logsure.io/compare/connecteam/): broad workforce management compared with proof-of-completion and client reports
- [LogSure vs SafetyCulture](https://logsure.io/compare/safetyculture/): inspection and EHS audit tooling compared with recurring proof-of-work
- [LogSure vs Jobber](https://logsure.io/compare/jobber/): trades business management compared with commercial proof-of-work and client reports
- [LogSure vs FotoFinish](https://logsure.io/compare/fotofinish/): shift-level photo submissions compared with task-level proof on every recurring job
- [LogSure vs OrangeQC](https://logsure.io/compare/orangeqc/): janitorial inspection scoring compared with proof that recurring work was completed
- [LogSure vs CrewProof](https://logsure.io/compare/crewproof/): GPS-led verification compared with a task-record approach that does not track staff location
- [How to prove cleaning was completed](https://logsure.io/how-to-prove-cleaning-was-completed/): guide to evidencing recurring cleaning work
- [Best photo-verified task management tools](https://logsure.io/best-photo-verified-task-management-tools/): roundup of photo-verification tooling

## AI integrations

LogSure has a production Model Context Protocol (MCP) integration for permissioned AI-assisted operations.

- [AI integrations overview](https://logsure.io/ai-integrations/): available AI and MCP integration surfaces
- [LogSure MCP server](https://logsure.io/ai-integrations/mcp/): remote MCP setup, security model, supported operation categories, and current limitations
- [ChatGPT setup](https://logsure.io/ai-integrations/chatgpt/): ChatGPT custom MCP app setup using LogSure OAuth
- [Claude Desktop setup](https://logsure.io/ai-integrations/claude-desktop/): Claude Desktop setup using the LogSure MCP integration

### Remote MCP server

- Transport: remote MCP over Streamable HTTP
- Server name: `logsure`
- MCP URL: `https://mcp.logsure.dev/mcp`
- Authentication: LogSure OAuth for ChatGPT; `Authorization: Bearer lsk_...` for Claude, Codex, and other token-based clients
- Token source: LogSure web app, Settings -> API & Integrations
- Token properties: revocable, per-user, organisation-scoped, shown once at creation

The MCP server is not an unauthenticated public API. It exposes only the data and actions allowed for the authenticated LogSure user.

### Supported MCP operation categories

The categories below are indicative, not exhaustive. The server advertises its full tool list on connection.

- Search and review scheduled tasks and templates
- Read task counts, summaries, and operational briefings
- Find unassigned work, and compute staff workload from scheduled tasks
- Create, edit, reassign, reschedule, complete, and delete tasks, including bulk operations
- Create and manage reusable task starters and schedule pause periods
- Manage clients, client teams, categories, and locations
- Search, create, resolve, prioritise, and assign issues
- Read and add task or issue chat messages
- Upload photo evidence through a bounded, permission-checked upload flow
- Draft and send client reports, and drill into client completion gaps
- Request and download evidence exports
- Complete tasks when the user has permission, including attaching a required completion photo through the MCP upload flow. Tasks that require a captured signature are still completed in the LogSure app.

MCP write actions are permission-checked and routed through LogSure's backend security boundary. Task completion, issue changes, assignment changes, and chat writes are designed to preserve organisation isolation and auditability.

## Operations

- [Status](https://logsure.io/status/): live system status

## Trust and legal

- [Privacy policy](https://logsure.io/privacypolicy/)
- [Terms](https://logsure.io/terms/)
- [Sub-processors](https://logsure.io/sub-processors/)
- [Accessibility](https://logsure.io/accessibility/)

## What is NOT available

These are sometimes assumed to exist; flagging explicitly so agents do not hallucinate them. This list describes today's surfaces and changes as LogSure ships.

- **Unauthenticated MCP access.** The MCP server requires a valid per-user LogSure API token.
- **Public REST or GraphQL API.** Not yet available as a supported surface, and on the roadmap. Firebase Cloud Functions power the first-party clients and are not a stable third-party contract unless explicitly documented.
- **Generic webhook or event-stream integrations.** Not yet supported for external systems, and on the roadmap.
- **True staff availability data.** The current MCP workload view is computed from scheduled tasks, and reports workload, not capacity. LogSure does not yet store holidays, sick days, shifts, or working hours. User availability is a planned feature.
- **AI replacement for the mobile app.** Field staff still use the LogSure mobile app for on-site capture, offline-friendly working, signature capture, and mobile-first completion flows.

For integration enquiries, contact `support@logsure.io`.