Bring Safety Compliance
to Claude Desktop
Learn how to connect Gripr to Claude Desktop and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Gripr MCP Server?
Connect your Gripr (Goliath Systemer) account to any AI agent and take full control of your construction projects and craft business workflows through natural conversation.
What you can do
- Project Orchestration — List and manage all active construction projects and retrieve detailed technical metadata and status
- Time Tracking — Programmatically register work hours for specific projects and retrieve history to ensure accurate billing and labor oversight
- Task Lifecycle — Create and manage project tasks to coordinate on-site activities and maintain a high-fidelity project schedule
- Customer CRM — Manage customer profiles and retrieve detailed contact information to streamline client communication
- Field Compliance — Access HSE (Health, Safety, and Environment) and QA (Quality Assurance) forms directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Gripr account (Settings > Integrations / API)
3. Start managing your construction workflows from Claude, Cursor, or any MCP client
No more manual time logging or complex navigation through fragmented project lists. Your AI acts as your dedicated construction project manager.
Who is this for?
- Project Managers — instantly register site hours and update task statuses using natural language queries
- Company Owners — monitor project progress and retrieve customer data without leaving your workspace
- Field Supervisors — quickly access compliance forms and manage team assignments across multiple construction sites
Built-in capabilities (11)
Create a new customer
Create a new project
Create a new task
Get details for a project
List all customers
List HSE/QA forms
List all projects
List all registered hours
Optionally filter by project ID. List tasks
List all users in the workspace
Register work hours
Why Claude Desktop?
Claude Desktop is the definitive way to connect Gripr to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Gripr in Claude Desktop
Gripr and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Gripr to Claude Desktop 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 Gripr in Claude Desktop
The Gripr 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 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop 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
Gripr for Claude Desktop
Every tool call from Claude Desktop to the Gripr MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my API Key in Gripr?
Log in to your Gripr account and navigate to Settings > Integrations / API to generate your unique key.
Can I register hours for a specific project?
Yes! The register_hours tool allows you to provide the projectId, duration in minutes, and a description for each entry.
How do I access compliance forms?
Use the list_forms tool to retrieve a directory of all available HSE and QA forms configured in your workspace.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.