Remote MCP server

LogSure MCP Server

Connect compatible AI assistants to LogSure using the Model Context Protocol. The server lets authorised users work with tasks, issues, locations, chats, and operational workload data from an AI client.

MCP connection details

Transport: Remote URL
Server name: logsure
MCP URL: https://mcp-server-phi-mauve.vercel.app/mcp
Bearer token: Paste your lsk_... token, or set Authorization: Bearer lsk_... if your client asks for headers.

Tasks and briefings

Search scheduled tasks, find unassigned work, review daily status, and generate operational briefings.

Users and workloads

Search assignable users and compare scheduled-task workload for a date range. This is workload, not true availability.

Issues and chat

Search, create, resolve, assign, and prioritise issues. Read and add task or issue chat messages.

Security model

MCP access is per user. LogSure validates the token server-side, derives the organisation from that token, checks permissions, and keeps cross-organisation data isolated.

Token setup

Generate a token in Settings -> API & Integrations. The raw token is shown once, starts with lsk_, and can be revoked any time.

Current limitations

There is no unauthenticated public MCP access.
LogSure does not expose a public REST or GraphQL API.
Staff workload is computed from scheduled tasks. It is not yet a holiday, shift, sick-day, or capacity calendar.
Tasks that require photo evidence are best completed in the LogSure mobile app.

Want to use LogSure with Claude Desktop?

Claude Desktop can use the same LogSure MCP tools and the same revocable API token.

Claude Desktop Setup Contact Support