Bring Safety Compliance
to VS Code Copilot
Learn how to connect Gripr to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Gripr data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Gripr in VS Code Copilot
Gripr and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Gripr to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.