Greptile MCP Server

Modern TypeScript MCP server for AI-powered code search and querying with Greptile API

Local serverstdioPython

What is the Greptile MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Greptile MCP MCP server moves it into the conversation instead. Modern TypeScript MCP server for AI-powered code search and querying with Greptile API.

The short version

A modern, TypeScript-powered MCP (Model Context Protocol) server that provides AI-powered code search and querying capabilities through the Greptile API. Built with the official MCP SDK and designed for seamless integration with AI tools like Claude Desktop, Continue, and other MCP-compatible clients.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Streaming — Real-time chunk delivery
  • Prerequisites — The Prerequisites tool exposed by this server

Getting it running

Installation goes through your MCP client rather than a global install: point it at greptile-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: GREPTILE_API_KEY, GITHUB_TOKEN, GREPTILE_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Greptile MCP's toolset — Streaming, Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by sosacrazy126; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Greptile MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
StreamingReal-time chunk delivery
PrerequisitesThe Prerequisites tool exposed by this server.

How to install the Greptile MCP MCP server

{
  "mcpServers": {
    "greptile": {
      "command": "npx",
      "args": ["-y", "greptile-mcp-server"],
      "env": {
        "GREPTILE_API_KEY": "your-value",
        "GITHUB_TOKEN": "your-value",
        "GREPTILE_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GREPTILE_API_KEYCredential the server authenticates with.Yes
GITHUB_TOKENCredential the server authenticates with.Yes
GREPTILE_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Greptile MCP to Streaming.
  • Use Greptile MCP to Prerequisites.

Frequently asked questions

It connects Greptile MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Streaming, Prerequisites) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Greptile MCP directly.