GitHub Actions MCP Server
Allows managing GitHub Actions workflows in repositories, including listing workflows, retrieving workflow details, triggering workflow_dispatch events, checking and canceling workflow runs, and triggering repository_dispatch events.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitHub Actions MCP Serverlist all workflows in octocat/hello-world"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitHub Actions MCP Server
MCP server for managing GitHub Actions workflows. Supports both stdio (default) and HTTP (Streamable HTTP) transports.
Features
7 tools:
Tool | Description |
| Parse a GitHub URL or |
| List all workflows in a repo |
| Get a specific workflow by ID or filename |
| Trigger a |
| Get latest or specific workflow run status |
| Cancel a running workflow |
| Trigger a |
Related MCP server: N8N MCP Server
Requirements
Node.js >= 18
A GitHub token with
reposcope (workflowscope for triggering workflows):GITHUB_TOKENenv var
Build
npm install
npm run buildRun
stdio (default, for MCP hosts that spawn a child process)
GITHUB_TOKEN=xxx node dist/index.jsHTTP (Streamable HTTP transport)
GITHUB_TOKEN=xxx node dist/index.js --transport http --port 3000
# → http://127.0.0.1:3000/mcpVia npx (after publishing)
GITHUB_TOKEN=xxx npx github-actions-mcp --transport http --port 3000Usage with opencode
Add to opencode.json:
{
"mcp": {
"github-actions": {
"type": "local",
"command": ["node", "/path/to/dist/index.js"],
"environment": { "GITHUB_TOKEN": "{env:GITHUB_TOKEN}" }
}
}
}Or run over HTTP:
{
"mcp": {
"github-actions": {
"type": "remote",
"url": "http://127.0.0.1:3000/mcp"
}
}
}Deploy on Vercel
The server can be deployed as a Vercel Node.js function that exposes the HTTP (Streamable HTTP) transport at https://<your-app>.vercel.app/api/mcp.
Files
api/mcp.ts— Vercel function adapter (Web Standardfetchexport: rejects GET, proxies the POST body to the MCP handler)vercel.json— Node 20 runtime,maxDuration: 30.env.example— lists requiredGITHUB_TOKENenvironment variable
Steps
Set the
GITHUB_TOKENenvironment variable in the Vercel project settings (or viavercel env add GITHUB_TOKEN).Deploy:
vercel --prodThe MCP endpoint is
https://<your-app>.vercel.app/api/mcp.
Use with an MCP host
{
"mcpServers": {
"github-actions": {
"url": "https://<your-app>.vercel.app/api/mcp"
}
}
}Run locally with Vercel CLI
vercel dev
# → http://localhost:3000/api/mcpTest with MCP Inspector
npx @modelcontextprotocol/inspector node dist/index.jsProject Structure
src/
├── index.ts # Entry point — transport selection (stdio|http)
├── server.ts # McpServer factory, registers all tools
├── github.ts # GitHub REST API client
└── tools/ # Zod input schemas per toolMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseCqualityFmaintenanceAn MCP server that enables AI assistants to manage GitHub Actions workflows by providing tools for listing, viewing, triggering, canceling, and rerunning workflows through the GitHub API.94541MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of multiple N8N workflow automation instances through MCP. Supports listing, creating, updating, deleting, executing workflows and monitoring their executions across different N8N environments.200MIT
- FlicenseNot gradedqualityDmaintenanceEnables managing GitHub repositories, files, and user information through MCP, with support for creating, updating, and deleting repository contents, as well as fetching user profiles.1
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with GitHub issues, pull requests, and Actions workflows through MCP tools.
Related MCP Connectors
GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Build and manage Cloudgate workflow-APIs: controllers, actions, workflow graphs, and databases.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lockround/github-actions-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server