How to Use GitHub MCP Server with CrewAI using Vinkius

Give CrewAI instant access to 12 tools to Create New Issue, Get File Contents, Get My Github Profile, and more using Vinkius.

GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

ChatGPT Claude Perplexity

The GitHub MCP Server for CrewAI is a standout in the Industry Titans category, giving your AI agent 12 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="GitHub Specialist",
    goal="Help users interact with GitHub effectively",
    backstory=(
        "You are an expert at leveraging GitHub 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 GitHub "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedNo server setup

Plug & PlayNo coding needed

SecurePrivacy protected

PrivateYour data is safe

Cost ControlBudget limits

Control1-click disconnect

Auto-UpdatesMaintenance free

High SpeedOptimized for AI

Reliable99.9% uptime

Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

About GitHub MCP Server

Connect your GitHub account to any AI agent to automate your software development lifecycle and code management through the Model Context Protocol (MCP). GitHub is the world's leading AI-powered developer platform. This MCP server enables you to retrieve repository metadata, manage issues, track pull requests, and search for code directly through natural conversation.

CrewAI does not assign one agent to do everything. It builds teams. When you connect GitHub through Vinkius, each agent in the crew can call 12 tools with role-based precision: a research agent queries raw data, an analyst agent cross-references findings, a reporting agent compiles actionable output. They share memory. They delegate tasks. They negotiate priorities. The result is not a single-threaded chatbot interaction. It is a coordinated intelligence operation executed at machine speed.

Key Features

Repository Oversight. List all repositories for any user or organization, and fetch detailed configuration metadata for specific projects.
Issue & PR Management. List issues and pull requests, track their lifecycle status, and programmatically open new issues from your chat interface.
Code Content Discovery. Retrieve the contents of files or directories within any repository to understand codebase structures.
Advanced Code Search. Execute powerful searches across GitHub's massive database to isolate specific code snippets or repositories.
Collaboration Tracking. Monitor forks and contributors to understand project community engagement.
Identity Oversight. Access detailed profile information for the authenticated GitHub user to verify permissions and account context.
Real-time Synchronization. Keep your source control and development data accessible to your AI assistant without leaving your primary workspace.

The GitHub MCP Server exposes 12 tools through Vinkius. Connect it to CrewAI in under two minutes. Fully managed, no infrastructure to provision, no vendor lock-in.

12 tools included

Explore every tool GitHub exposes to CrewAI through Vinkius.

View all 12 tools

Connect GitHub to CrewAI via MCP

Follow these steps to connect GitHub to CrewAI. The setup takes under two minutes and requires no coding or server hosting.

Get your Vinkius Access Token

Go to cloud.vinkius.com to log in or create a free account, and retrieve your personal access token from the dashboard. This token is required to authenticate your connection to the hosted GitHub MCP server.

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 12 tools from GitHub

Why Use CrewAI with the GitHub MCP Server

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

Multi-agent crews give each role precise access to GitHub through Vinkius: a research agent queries raw data, an analyst cross-references findings, a reporter compiles actionable output

Native MCP integration: pass the Vinkius Edge URL in the `mcps` parameter. Zero adapter code. Agents discover all 12 tools from GitHub at crew startup

Shared memory between crew members means GitHub data from one agent's query through Vinkius is immediately available to the next agent's analysis. No manual state passing

Sequential and hierarchical crew patterns map to real workflows: gather GitHub data, analyze trends, flag anomalies, generate reports. Each step handled by a specialist agent

GitHub + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries GitHub 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 GitHub, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain GitHub 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 GitHub against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for GitHub in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with GitHub immediately.

"List the last 5 open issues in the 'facebook/react' repository."

"Find all repositories for the organization 'vinkius'."

"Read the content of the 'README.md' file in 'vinkius/vurb-docs'."

Troubleshooting GitHub MCP Server with CrewAI

Common issues when connecting GitHub to CrewAI through 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.

GitHub + CrewAI FAQ

Common questions about integrating GitHub 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.

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents

Complete visibility into every agent action

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect GitHub using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Explore Analytics