An astronaut overseeing a futuristic data hub

Connect Greptile to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Get instant, accurate answers about any repository through conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 11 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 11 available through Greptile.

  1. 01

    Reindex repository

    Triggers a fresh indexing pass for a specific repository.

  2. 02

    Search codebase

    Performs a semantic search across your indexed code to find relevant logic and patterns.

  3. 03

    Get greptile usage

    Checks your current API consumption and remaining rate limits.

  4. 04

    Get repository status

    Retrieves the current indexing and processing state of a repository.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 11 available through Greptile.

  1. 05

    List repositories

    Shows a list of all repositories currently managed by Greptile.

  2. 06

    Query codebase

    Sends a natural language question to the AI to get answers based on your code.

  3. 07

    Delete repository

    Removes an indexed repository from the Greptile system.

  4. 08

    Get file info

    Provides metadata and details for a specific file within a repository.

Capability set03 / 03

09-11

3 capabilities in this set.

Part of 11 available through Greptile.

  1. 09

    Index repository

    Starts the initial indexing process for a new GitHub or GitLab repository.

  2. 10

    Query with context

    Asks the codebase a question while maintaining the context of your current conversation.

  3. 11

    Search by filepath

    Limits a search to a specific file path for more precise results.

Real work

What teams actually run

01

Onboarding

New developers ask the agent how different modules interact to learn the system faster.

02

Refactoring

Find all instances where a specific pattern is used before changing a core function.

03

Bug Hunting

Trace how data flows through a specific service to find where a logic error occurs.

04

Dependency Mapping

Identify which files import a specific module to understand the impact of a change.

Automate a task

Put Greptile to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Greptile works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Greptile to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

953ms average. Fast in production.

Greptile is checked daily against the live service.

Daily averagePeak 1286ms
Oct 3Today
Fastest day
757ms
Slowest day
1286ms
14-day trend
Improving-7%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 11 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Greptile, so you can see the experience inside your AI.

It does not authenticate your account with Greptile. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Greptile Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_JjO0hZW2yPNTgFluo5v382Yb9GmYI7NAmGBDNUxG/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Greptile capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "greptile-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_JjO0hZW2yPNTgFluo5v382Yb9GmYI7NAmGBDNUxG/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Greptile in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Greptile owners hand off.

This MCP is built for technical teams who need to navigate large, complex codebases quickly.

  • 01

    Developers

    They use it to understand unfamiliar code and find specific implementations.

  • 02

    Code Reviewers

    They use it to trace dependencies and find related patterns during reviews.

  • 03

    Engineering Managers

    They use it to get quick answers about technical debt and architecture decisions.

FAQ

Questions Greptile owners ask.

  • 01

    How do I connect Greptile to my AI client?

    You subscribe to the MCP through Vinkius and enter your Greptile API key. Once connected, it is available in any compatible client like Claude or Cursor.

  • 02

    Which code hosting platforms are supported?

    This MCP supports indexing repositories from GitHub and GitLab.

  • 03

    Can I search for code in a specific file?

    Yes, you can use the search by filepath capability to target your queries to a specific location.

  • 04

    How do I know if my repository is ready to query?

    You can use the get repository status capability to check the progress of the indexing process.

  • 05

    Does the AI provide code references?

    Yes, when you query the codebase, the responses include specific code references to help you verify the answers.

  • 06

    Can I ask natural language questions about my codebase?

    Yes! The query_codebase capability sends a natural language question along with repository references and returns AI-generated answers with specific code references (file paths and line numbers). For follow-up questions, use query_with_context with the session ID from the previous response to maintain conversation continuity.

  • 07

    Do I need to index my repository before querying it?

    Yes. Use index_repository with the remote host (github or gitlab), repository path (owner/repo), and branch name. Check indexing progress with get_repository_status. Once indexed, you can query and search the repository. Use reindex_repository to refresh the index after significant code changes.

  • 08

    Can I search for specific code patterns across my repositories?

    Yes. The search_codebase capability performs semantic search across your indexed repositories to find relevant files and functions. For targeted results, use search_by_filepath to narrow the search to a specific file path. Use get_file_info to retrieve indexed metadata for any file.

Connect Greptile to Claude, Cursor, ChatGPT & more