Bring Safety Compliance
to Claude Code
Learn how to connect Gripr to Claude Code 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 Code?
Claude Code registers Gripr as an MCP server in a single terminal command. Once connected, Claude Code discovers all 11 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Gripr data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Gripr tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Gripr in Claude Code
Gripr and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Gripr to Claude Code 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 Code
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 Code 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 Code
Every tool call from Claude Code 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 do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable