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.

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.

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.

INSTANT PLUG AND PLAY

Greptile MCP Server for CrewAIGive CrewAI instant access to 11 tools to Delete Repository, Get File Info, Get Greptile Usage, and more

Name: Greptile
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to Greptile through Vinkius, pass the Edge URL in the `mcps` parameter and every Greptile tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Greptile app connector for CrewAI 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

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Greptile Specialist",
    goal="Help users interact with Greptile effectively",
    backstory=(
        "You are an expert at leveraging Greptile tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Greptile "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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

About Greptile MCP Server

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

When paired with CrewAI, Greptile becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Greptile tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI

When CrewAI 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_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

Connect Greptile to CrewAI via MCP

Follow these steps to wire Greptile into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 11 tools from Greptile

Why Use CrewAI with the Greptile MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Greptile through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Greptile + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Greptile MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Greptile for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Greptile, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Greptile tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Greptile against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Greptile in CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

Common issues when connecting Greptile to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Greptile + CrewAI FAQ

Common questions about integrating Greptile MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.