Schema | GitHub Actions MCP Server

GitHub Actions MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`GITHUB_TOKEN`	Yes	GitHub token with repo scope (workflow scope for triggering workflows)

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
parse-github-repoA	Parse a GitHub URL or "owner/repo" string into structured owner and repo fields.
list-workflowsA	List all GitHub Actions workflows for a repository.
get-workflowC	Get details of a specific GitHub Actions workflow by ID or filename.
trigger-workflowB	Trigger a GitHub Actions workflow via workflow_dispatch event.
get-workflow-runB	Get the latest or a specific GitHub Actions workflow run status.
cancel-workflow-runA	Cancel a running GitHub Actions workflow.
trigger-repository-dispatchC	Trigger a repository_dispatch event to start a workflow.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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