3,400+ MCP servers ready to use
Vinkius

Bring Codebase Intelligence
to Cline

Learn how to connect Greptile to Cline and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Delete RepositoryGet File InfoGet Greptile UsageGet Repository StatusIndex RepositoryList RepositoriesQuery CodebaseQuery With ContextReindex RepositorySearch By FilepathSearch Codebase

What is the Greptile MCP Server?

Connect your Greptile account to any AI agent and unlock AI-powered codebase understanding through natural conversation.

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

How it works

1. Subscribe to this server
2. Enter your Greptile API Key from the developer dashboard
3. Start querying your codebase from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Developers — understand unfamiliar codebases, find implementations, and navigate large repositories through conversation
  • Code Reviewers — search for related patterns, understand code context, and trace dependencies
  • Engineering Managers — get quick answers about architecture decisions, coding patterns, and technical debt

Built-in capabilities (11)

delete_repository

Delete indexed repository

get_file_info

Get file info

get_greptile_usage

Check API usage

get_repository_status

Get repository status

index_repository

Index a repository

list_repositories

List indexed repositories

query_codebase

Query codebase with AI

query_with_context

Query with session context

reindex_repository

Reindex a repository

search_by_filepath

Search in specific file

search_codebase

Search codebase

Why Cline?

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Greptile tool calls without waiting for prompts between steps. Connect 11 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

  • Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

  • Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

  • Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

  • Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

See it in action

Greptile in Cline

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Greptile and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Greptile to Cline 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.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Greptile in Cline

The Greptile 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 Cline 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.

Greptile
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Greptile for Cline

Every tool call from Cline to the Greptile MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I ask natural language questions about my codebase?

Yes! The query_codebase tool 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.

02

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.

03

Can I search for specific code patterns across my repositories?

Yes. The search_codebase tool 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.

04

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.

05

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.

06

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

07

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.