Bring Source Control
to Mastra AI
Learn how to connect GitHub to Mastra AI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the GitHub MCP Server?
Connect your GitHub account to any AI agent and take full control of your source control and development workflows through natural conversation.
What you can do
- Repository Orchestration — List and manage your repositories programmatically, including retrieving star counts, languages, and detailed metadata
- Issue Lifecycle — Monitor project status by listing open issues and creating new ones directly through your agent to maintain momentum
- Code Intelligence — Search through repositories and files programmatically to find specific logic and retrieve raw file contents (base64) for analysis
- Collaboration Visibility — Monitor pull requests and recent notifications to stay updated on team-wide development activity and code reviews
- Resource Management — Access user profiles, organization memberships, and Gists to manage your complete GitHub presence programmatically
How it works
1. Subscribe to this server
2. Retrieve your Personal Access Token (PAT) from GitHub (Settings > Developer Settings > PAT)
3. Ensure your token has the required scopes (repo, user, notifications)
4. Start managing your code and projects from Claude, Cursor, or any MCP client
No more manual toggling between browser tabs to check issue statuses. Your AI acts as your dedicated engineering coordinator.
Who is this for?
- Software Engineers — instantly find code snippets across repositories and retrieve file contents using natural language
- Team Leads — monitor repository activity and triage issues without leaving your communication tools
- DevOps Engineers — automate repository discovery and monitor project notifications through simple AI queries
Built-in capabilities (12)
Open GitHub issue
Read file from repo
Get account info
Get repo info
List code snippets
List user orgs
List your GitHub repos
List repo PRs
Check GitHub inbox
Check repo branches
List repo issues
Find GitHub projects
Why Mastra AI?
Mastra's agent abstraction provides a clean separation between LLM logic and GitHub tool infrastructure. Connect 12 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.
- —
Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add GitHub without touching business code
- —
Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation
- —
TypeScript-native: full type inference for every GitHub tool response with IDE autocomplete and compile-time checks
- —
One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure
GitHub in Mastra AI
GitHub and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect GitHub to Mastra AI 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for GitHub in Mastra AI
The GitHub 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 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Mastra AI 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.
* 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
How Vinkius secures
GitHub for Mastra AI
Every tool call from Mastra AI to the GitHub MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I read private repositories?
Yes, provided your Personal Access Token (PAT) has the 'repo' scope or appropriate fine-grained permissions for those repositories.
How do I find a repository owner and name?
In a GitHub URL like github.com/vinkius/mcp-server, the owner is vinkius and the repository name is mcp-server.
Does it support creating pull requests?
This version supports listing pull requests and issues. PR creation is currently handled through the web interface or other specialized tools.
How does Mastra AI connect to MCP servers?
Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
Can Mastra agents use tools from multiple servers?
Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
Does Mastra support workflow orchestration?
Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.
createMCPClient not exported
Install: npm install @mastra/mcp