How do I create a GitHub Personal Access Token?

Go to [**Settings > Developer settings > Personal access tokens**](https://github.com/settings/tokens), click **Generate new token (classic)**, give it a descriptive name, select the scopes you need (recommended: repo, workflow, read:org) and click **Generate token**. Copy the token immediately — it starts with `ghp_` and won't be shown again.

Can I create issues with labels via the agent?

Yes! Use the `create_issue` tool with the owner, repo and title parameters. Optionally provide a Markdown body and comma-separated labels (e.g. "bug,high-priority"). The agent will create the issue and return its number, title and URL.

How do I search for repositories with specific criteria?

Use the `search_repos` tool with GitHub's query syntax. Examples: "machine learning in:name language:python stars:>1000" finds Python ML repos with 1k+ stars; "org:microsoft pushed:>2024-01-01" finds Microsoft repos updated in 2024. The query supports qualifiers for language, stars, forks, org, topic, size and more.

Does this tool support GitHub Actions workflow monitoring?

Yes! Use `list_workflow_runs` to see recent CI/CD executions for a repository. You can filter by branch and see each run's status (queued, in_progress, completed) and conclusion (success, failure, cancelled). This is useful for checking if recent deployments or builds passed without opening the Actions tab.

GitHub Alternative MCP Server for CrewAI 14 tools — connect in under 2 minutes

Name: GitHub Alternative
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 14 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="GitHub Alternative Specialist",
    goal="Help users interact with GitHub Alternative effectively",
    backstory=(
        "You are an expert at leveraging GitHub Alternative 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 Alternative "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 14 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 GitHub Alternative MCP Server

Connect your GitHub account to any AI agent and take full control of your development workflows through natural conversation.

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

What you can do

User & Repository Discovery — View your profile and list all repositories with visibility, language and star counts
Issue Management — List, inspect and create issues with labels and Markdown descriptions
Pull Request Tracking — Browse and review pull requests with merge status, draft state and review info
Commit History — Review commit logs across branches with author, message and timestamp
Release Management — List releases and fetch specific release details by git tag
CI/CD Monitoring — Check recent GitHub Actions workflow runs with status and conclusion
Advanced Search — Search repositories using GitHub's powerful query syntax with language, stars and org qualifiers

The GitHub Alternative MCP Server exposes 14 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.

How to Connect GitHub Alternative to CrewAI via MCP

Follow these steps to integrate the GitHub Alternative MCP Server with CrewAI.

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 14 tools from GitHub Alternative

Why Use CrewAI with the GitHub Alternative MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with GitHub Alternative 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 the 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

GitHub Alternative + CrewAI Use Cases

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

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

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

GitHub Alternative MCP Tools for CrewAI (14)

These 14 tools become available when you connect GitHub Alternative to CrewAI via MCP:

create_issue

Requires the owner, repo and title. Optionally set the issue body (Markdown text) and labels (comma-separated). Returns the created issue with its number, title and URL. Create a new GitHub issue

get_issue

Provide the owner, repo and issue number. Get details for a specific GitHub issue

get_pull_request

Provide the owner, repo and PR number. Get details for a specific GitHub pull request

get_release_by_tag

Returns the release name, tag name, body (Markdown), draft/prerelease status, publish date and attached assets. Provide the owner, repo and tag name. Get a GitHub release by its tag name

get_repo

Provide the owner (org or user) and repo name. Get details for a specific GitHub repository

get_user

Returns login, name, email, avatar URL, company, bio, public repos count, followers and following counts. Use this to verify your token is working correctly. Get the authenticated GitHub user

list_branches

Each branch includes its name, commit SHA and whether it is the default (protected) branch. List branches in a GitHub repository

list_commits

Optionally filter by branch (sha parameter) and set the number of results. Each commit includes the SHA, author, commit message and date. Results are ordered newest first. List commits on a GitHub repository branch

list_issues

Optionally filter by state (open, closed, all). Note: GitHub's issues endpoint includes pull requests — use list_pull_requests for PRs only. Returns issue number, title, state, labels, assignee and creation date. List issues in a GitHub repository

list_pull_requests

Optionally filter by state (open, closed, all). Returns PR number, title, state, author, draft status, creation date and merge status. Use get_pull_request for full details on a specific PR. List pull requests in a GitHub repository

list_releases

Each release includes its tag name, name, draft/prerelease status, author, publish date and asset downloads info. Returns the most recent releases first. List releases for a GitHub repository

list_repos

Optionally filter by type (all, owner, public, private, member) and set the number of results per page. Returns repo name, full_name, description, visibility, language, stars, forks and creation date. List repositories for the authenticated user

list_workflow_runs

Optionally filter by branch and set the number of results. Each run includes its ID, workflow name, event trigger, status (queued, in_progress, completed), conclusion (success, failure), branch and creation date. List GitHub Actions workflow runs for a repository

search_repos

The query supports qualifiers like "language:typescript", "stars:>1000", "org:microsoft", "pushed:>2024-01-01" and free-text search. Results include repo name, description, stars, forks, language and creation date. Search GitHub repositories

Example Prompts for GitHub Alternative in CrewAI

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

"Show me all open issues in my backend-api repo."

"What's the status of recent workflow runs on main branch?"

"Search for popular Python machine learning repos with over 1000 stars."

Troubleshooting GitHub Alternative MCP Server with CrewAI

Common issues when connecting GitHub Alternative 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

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

GitHub Alternative + CrewAI FAQ

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