Greptile MCP Server for VS Code CopilotGive VS Code Copilot instant access to 11 tools to Delete Repository, Get File Info, Get Greptile Usage, 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 Greptile app connector for VS Code Copilot is a standout in the Developer Tools 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 Greptile and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"greptile": {
"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 Greptile MCP Server
Connect your Greptile account to any AI agent and unlock AI-powered codebase understanding through natural conversation.
GitHub Copilot Agent mode brings Greptile 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
- AI Codebase Q&A — Ask natural language questions about one or more repositories and receive AI-generated answers with code references
- Contextual Follow-ups — Continue conversations with session context for multi-turn codebase exploration
- Semantic Code Search — Search across indexed repositories to find relevant files, functions, and code patterns
- File-Specific Search — Target searches within a specific file path for precise results
- Repository Indexing — Submit GitHub or GitLab repositories for indexing, check progress, and trigger re-indexing
- Repository Management — List all indexed repos, inspect file metadata, and remove outdated indexes
- Usage Monitoring — Track API consumption and rate limits
The Greptile 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 Greptile tools available for VS Code Copilot
When VS Code Copilot connects to Greptile through Vinkius, your AI agent gets direct access to every tool listed below — spanning codebase-intelligence, semantic-search, repository-indexing, 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.
Delete indexed repository
Get file info
Check API usage
Get repository status
Index a repository
List indexed repositories
Query codebase with AI
Query with session context
Reindex a repository
Search in specific file
Search codebase
Connect Greptile to VS Code Copilot via MCP
Follow these steps to wire Greptile 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 Greptile
Why Use VS Code Copilot with the Greptile MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Greptile 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
Greptile + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Greptile 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 Greptile in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Greptile immediately.
"How does the authentication middleware work in our backend repository?"
"Search for all files that import the database connection module and show me the file info."
"Index our new frontend repository and check the indexing status."
Troubleshooting Greptile MCP Server with VS Code Copilot
Common issues when connecting Greptile to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Greptile + VS Code Copilot FAQ
Common questions about integrating Greptile 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.