GitHub Alternative MCP. Audit commits, manage PRs, and track CI/CD status instantly.

Q: How do I use the listissues tool to find open bugs?

Use listissues(owner, repo, state='open'). This returns a list of issues with their number, title, state, and labels, letting you quickly see all active bugs without filtering manually.

Q: What is the difference between listissues and listpullrequests?

Use listissues for bug reports or general feature requests. Use listpullrequests when you specifically need to see code changes submitted for review. The two endpoints track different GitHub artifacts.

Q: Can I use getrepo to find out if a repo is private?

Yes, getrepo(owner, repo) returns detailed metadata, including the repository's visibility status. This helps you confirm if the repo is private or public.

Q: How do I check the status of the latest GitHub Actions run?

Call listworkflowruns(owner, repo). This gives you the ID, workflow name, status (queued/inprogress/completed), and conclusion (success/failure) of the most recent runs.

Q: What should I call if I want to create a new feature request?

Use createissue(owner, repo, title, body, labels). This tool handles the creation of a new issue and lets you set the title, body, and initial labels in one call.

Q: When should I use listcommits instead of listissues?

Use listcommits when you need to track the technical changes made to code. This tool gives you the SHA, author, and commit message history, while listissues focuses only on discussions, bugs, and feature requests.

Q: Can I use searchrepos to find repos in a specific organization?

Yes, you can use searchrepos by adding the org: qualifier to your query. For example, searching for org:microsoft lets you limit results to a specific organization's repositories.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Just plug in your AI agents and start using Vinkius.

GitHub Alternative. Manages your entire development lifecycle—repos, issues, PRs, and CI/CD—directly from your AI agent. Get full visibility into commit history, track merge status, and audit releases without leaving your IDE.

It lets your agent act like a dedicated engineering lead for your code base.

What your AI agents can do

Create issue

Creates a brand new GitHub issue for a specified repository.

Get issue

Retrieves the details for a specific GitHub issue number.

Get pull request

Gets the current status and details for a specific pull request.

+ 11 more capabilities included

Manage Code Repositories

Get details about a specific repository, list all repos for your account, or search across many organizations.

Track Issues and PRs

List, read, create, and review issues or pull requests using their number or status.

Audit Code Changes

List commit logs or list all branches in a repo to trace changes over time.

Monitor Releases and Workflows

Fetch specific release details by tag name or check the status of recent CI/CD workflow runs.

Identify Users and Accounts

Retrieve details about the authenticated GitHub user, including their bio and public repo count.

Ask AI about this MCP

Ask ChatGPT

Ask Claude

Ask Perplexity

Supported MCP Clients

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Lists the most recent GitHub Actions workflow runs for a repository.

search019d8440

search repos

Searches GitHub repositories using advanced query filters like language or star count.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with GitHub Alternative, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 4,700+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

What you can do with this MCP connector

Manage Code Repositories gets you all the metadata for a specific repo, or lets you list every repo you own, or search across multiple organizations using advanced queries like language or star count. Track Issues and PRs lets you list, read, or create issues, and it lets you list, read, or check the status of pull requests by number or status. Audit Code Changes lets you list commit logs for any branch in a repo and list all branches for a repo, letting you trace changes over time. Monitor Releases and Workflows lets you fetch specific release details using a git tag, list all published releases for a repo, and check the status of the most recent CI/CD workflow runs. Identify Users and Accounts lets you pull the profile info for the authenticated GitHub user, including their bio and public repo count.

How GitHub Alternative MCP Works

1 Subscribe to the server and provide your GitHub Personal Access Token.
2 Your AI client connects and authenticates against your GitHub account using the token.
3 You instruct your agent to perform a task (e.g., 'Show me the open issues for repo X'). The agent calls the relevant tool.

The bottom line is, your AI client runs the necessary GitHub API calls for you, keeping all the data inside your current workspace.

Who Is GitHub Alternative MCP For?

This is for the developer who can't afford to context-switch. If you spend time jumping between your IDE, GitHub.com, and Jira just to track a simple PR status or audit a commit, this server saves you minutes, and those minutes add up fast.

Software Developer

Reviews PRs, checks issue status, and inspects commit logs without leaving their IDE or local terminal.

Engineering Manager

Audits open issues, tracks release progress, and monitors CI/CD health across multiple repositories via natural conversation.

Open Source Maintainer

Triages community issues, manages release tags, and reviews community-submitted pull requests via conversation.

What Changes When You Connect

Check the status of a PR (using get_pull_request) and immediately see if it's marked 'Draft' or if it's already merged, all without leaving your chat window.
Audit a project's history by calling list_commits on a specific branch. You see the commit SHA, author, message, and exact date for every change.
Keep tabs on development progress by calling list_issues to see all open or closed bugs and features in a repo. You can even use create_issue on the fly.
Monitor CI/CD health using list_workflow_runs. You get the ID, workflow name, status (success/failure), and conclusion (failure/success) of the last runs.
Find niche projects or competitors by running search_repos. You can filter by language:typescript or stars:>1000 to narrow down results.
Review major milestones by calling list_releases or get_release_by_tag. You instantly get the tag name, publish date, and asset download info.

Real-World Use Cases

Investigating a Broken Build

A developer sees a build failure. Instead of navigating to the CI/CD tab, they ask their agent: 'What's the status of recent workflow runs on main?' The agent calls list_workflow_runs, showing the failure status and the exact workflow name, letting the dev know exactly where to start debugging.

Triaging a Feature Request

An Open Source Maintainer gets a new issue. They ask: 'Show me all open issues in my backend-api repo.' The agent calls list_issues, providing the issue number, title, and assignee. The maintainer can then use create_issue to assign a specific label and update the description.

Reviewing a Code Contribution

An Engineering Manager wants to review a PR. They ask the agent to 'Get details for PR #123.' The agent calls get_pull_request, confirming the merge status and if it's marked as draft, allowing the manager to decide if it needs more review.

Finding a Relevant Template Repo

A new developer needs a boilerplate repo. They ask the agent: 'Search for popular Python machine learning repos with over 1000 stars.' The agent calls search_repos, returning highly-starred examples like tensorflow/tensorflow and pytorch/pytorch, guiding the developer to the right starting point.

The Tradeoffs

Manual Context Switching

When a PR fails, the developer has to open GitHub.com, find the PR, click the 'Checks' tab, and then look for the specific workflow run ID. This takes 3-5 minutes of clicks and navigation.

→ Just ask your agent: 'What's the status of recent workflow runs on main?' The agent calls list_workflow_runs and gives you the status and conclusion right away.

Guessing the Right Tool

A user needs to check if a repo exists. They might try calling list_repos (which lists all repos) and manually scrolling to find the one they want, wasting time.

→ If you only care about one repo, use get_repo(owner, repo) directly. It gives you the metadata for that single repo without listing everything else.

Ignoring Specificity

When listing bugs, a user might just ask 'Show me issues.' The agent might return a mix of PRs and issues, forcing the user to filter manually.

→ Use the dedicated list_issues tool. It returns only issue numbers, titles, states, and labels, keeping your results clean and focused.

When It Fits, When It Doesn't

Use this if you need to audit, track, or manage the lifecycle of existing code artifacts. You're checking status (e.g., 'Is this PR merged?'), listing historical data (e.g., 'Show me all commits from last week'), or creating structured records (e.g., 'Create a bug issue').

Don't use this if you just need general documentation or simple reading. For instance, if you just want to see the name of your profile, get_user works. But if you need to find the most current project status, you'll need list_workflow_runs or get_pull_request.

If you need to find a project based on keywords (e.g., 'Python ML'), use search_repos. If you need to check the status of a specific item (like PR #45), use get_pull_request. It's about whether you need a list or a specific deep dive.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GitHub. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 14 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

create_issue get_issue get_pull_request get_release_by_tag get_repo get_user list_branches list_commits list_issues list_pull_requests list_releases list_repos list_workflow_runs search_repos

Checking a PR status shouldn't require jumping between tabs.

Right now, checking a single PR status is a click-fest. You navigate to the repo, click the 'Pull Requests' tab, find the right number, and then check the 'Checks' tab to see if the build passed. It's slow, and you're always jumping between tabs and pages.

With the GitHub Alternative MCP Server, you just ask your agent: 'What's the status of PR #123?' The agent calls `get_pull_request` and gives you the merge status, draft status, and review info—all in one clean response.

list_commits: Get the full history of a branch in seconds.

Before, auditing a commit history meant opening the repo and navigating to the 'History' view. You'd scroll through pages of commit logs, manually checking the author and date to figure out when a specific change was introduced.

Now, you tell your agent to 'List commits on the main branch.' The agent calls `list_commits` and spits out a clean list: SHA, author, message, and date. It's immediate, and you never lose context.

Common Questions About GitHub Alternative MCP

How do I use the `list_issues` tool to find open bugs? +

Use list_issues(owner, repo, state='open'). This returns a list of issues with their number, title, state, and labels, letting you quickly see all active bugs without filtering manually.

What is the difference between `list_issues` and `list_pull_requests`? +

Use list_issues for bug reports or general feature requests. Use list_pull_requests when you specifically need to see code changes submitted for review. The two endpoints track different GitHub artifacts.

Can I use `get_repo` to find out if a repo is private? +

Yes, get_repo(owner, repo) returns detailed metadata, including the repository's visibility status. This helps you confirm if the repo is private or public.

How do I check the status of the latest GitHub Actions run? +

Call list_workflow_runs(owner, repo). This gives you the ID, workflow name, status (queued/in_progress/completed), and conclusion (success/failure) of the most recent runs.

What should I call if I want to create a new feature request? +

Use create_issue(owner, repo, title, body, labels). This tool handles the creation of a new issue and lets you set the title, body, and initial labels in one call.

How do I use `get_user` to confirm my token permissions? +

It confirms your token's permissions by listing your account details. This function returns your login, email, and public repo/follower counts, letting you immediately verify if the token has been set up correctly.

When should I use `list_commits` instead of `list_issues`? +

Use list_commits when you need to track the technical changes made to code. This tool gives you the SHA, author, and commit message history, while list_issues focuses only on discussions, bugs, and feature requests.

Can I use `search_repos` to find repos in a specific organization? +

Yes, you can use search_repos by adding the org: qualifier to your query. For example, searching for org:microsoft lets you limit results to a specific organization's repositories.

How do I create a GitHub Personal Access Token? +

Go to Settings > Developer settings > Personal access 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.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript