Bring Site Safety
to Cursor
Learn how to connect SignOnSite to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the SignOnSite MCP Server?
Connect your SignOnSite account to any AI agent and take full control of your construction site safety and attendance orchestration through natural conversation. SignOnSite provides a premier platform for managing worker sign-ons, safety inductions, and site attendance, and this integration allows you to retrieve site metadata, monitor worker enrollments, and track safety briefings directly from your chat interface.
What you can do
- Worker & Site Orchestration — List all active sites and retrieve detailed worker profile metadata, including enrollment status and contact info programmatically.
- Attendance Lifecycle Management — Monitor real-time worker sign-ons and sign-offs to ensure your site attendance is always accurate directly from the AI interface.
- Safety & Permit Control — Access and monitor site permits and safety briefings to ensure your workplace compliance is always synchronized via natural language.
- Enrolment & Credential Intelligence — Access worker credentials and manage enrolment flows to keep your compliance records up to date.
- Operational Monitoring — Track site activities and manage company metadata to ensure your safety orchestration is always optimized using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your SignOnSite API Token from your dashboard
3. Start managing your site safety from Claude, Cursor, or any MCP-compatible client
No more manual sign-on sheets or chasing safety certificates. Your AI acts as a dedicated safety officer or site manager.
Who is this for?
- Site Managers & Foremen — quickly retrieve worker attendance and monitor safety induction statuses without switching apps.
- Safety Officers — automate the retrieval of site permits and track compliance credentials via natural conversation.
- Operations Teams — streamline the retrieval of site-user metadata and monitor multi-site activities directly within the chat.
Built-in capabilities (12)
Enrol a new worker
Get details for a specific site
Get details for a specific worker
List all associated companies
List all construction sites
List all site workers
Query completed safety forms
g., Hot Works, Confined Space) for your projects. Query safety permits
Supports filtering by site and date. Query worker attendance records
Check worker licenses and inductions
Record a manual sign-off for a worker
Record a manual sign-on for a worker
Why Cursor?
Cursor's Agent mode turns SignOnSite into an in-editor superpower. Ask Cursor to generate code using live data from SignOnSite and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
SignOnSite in Cursor
SignOnSite and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect SignOnSite to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for SignOnSite in Cursor
The SignOnSite MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
SignOnSite for Cursor
Every tool call from Cursor to the SignOnSite MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find which workers are currently signed onto a specific construction site?
Yes! Use the query_attendance tool. Provide the Site ID, and your agent will return the list of currently present workers and their sign-on times in seconds.
How do I check if a specific worker has completed their safety induction for a site?
Simply ask the agent to run the get_worker or query_credentials action. It will retrieve the enrollment status and safety credentials for that individual.
How do I find my SignOnSite API Token?
Log in to your SignOnSite web dashboard, navigate to the Settings > API section, and you will find your unique Company API Token there.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.