Gripr MCP Server for VS Code CopilotGive VS Code Copilot instant access to 11 tools to Create Customer, Create Project, Create Task, and more
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
Ask AI about this App Connector for VS Code Copilot
The Gripr app connector for VS Code Copilot is a standout in the Construction category — giving your AI agent 11 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Gripr and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"gripr": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About 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.
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.
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
The Gripr MCP Server exposes 11 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 11 Gripr tools available for VS Code Copilot
When VS Code Copilot connects to Gripr through Vinkius, your AI agent gets direct access to every tool listed below — spanning safety-compliance, risk-assessment, time-tracking, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect Gripr to VS Code Copilot via MCP
Follow these steps to wire Gripr into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Gripr
Why Use VS Code Copilot with the Gripr MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Gripr through the Model Context Protocol.
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 + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Gripr MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for Gripr in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Gripr immediately.
"List all my active construction projects."
"Register 120 minutes of work for project 'p_123' today."
"Show me a list of all customers in Gripr."
Troubleshooting Gripr MCP Server with VS Code Copilot
Common issues when connecting Gripr to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Gripr + VS Code Copilot FAQ
Common questions about integrating Gripr MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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.