Does Claude support the GitHub Actions MCP server?

Yes. Claude connects to the GitHub Actions MCP server through its connector settings, pointed at your Metorial URL. You need any Claude plan; Free plans allow one custom connector.

Do I need an API key to connect GitHub Actions to Claude?

No. You sign in to GitHub Actions once through Metorial, and Claude uses that connection. No API keys go into Claude's settings.

Which GitHub Actions tools can Claude use?

All 16 GitHub Actions tools your team allows, such as Manage Secrets, Control Workflow Run, Trigger Workflow. Admins can narrow that list per team.

Can I control which teammates use GitHub Actions in Claude?

Yes. Role-based access control decides who can use GitHub Actions and which of its tools appear in Claude, and every call is logged with the person's identity.

What if Claude doesn't show GitHub Actions tools?

On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.

Connect GitHub Actions to Claude

Ask Claude to use the manage secrets tool in GitHub Actions
Ask Claude to use the control workflow run tool in GitHub Actions
Ask Claude to use the trigger workflow tool in GitHub Actions
Ask Claude to use the get workflow run tool in GitHub Actions
Ask Claude to use the manage variables tool in GitHub Actions

1. Enable GitHub Actions in Metorial
In your Metorial portal, enable the GitHub Actions MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add a custom connector
Open Customize, then Connectors. Select Add, then Custom, then Web.
3. Paste your Metorial MCP URL
Name it Metorial, paste your Magic MCP URL (<your-magic-mcp-url>) and continue.
4. Sign in
Select Add and sign in to load GitHub Actions tools.

Once GitHub Actions is enabled in Metorial, teammates sign in with SSO and get the same connection in Claude, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Manage Secrets: List, get, create/update, or delete Actions secrets at the repository, organization, or environment level.
Control Workflow Run: Cancel, force-cancel, re-run, or delete a workflow run.
Trigger Workflow: Trigger a GitHub Actions workflow run via the `workflow_dispatch` event.
Get Workflow Run: Get detailed information about a specific workflow run, including its status, conclusion, timing, and associated commit.
Manage Variables: List, get, create, update, or delete Actions configuration variables at the repository, organization, or environment level.
List Artifacts: List workflow artifacts for a repository or a specific workflow run.
Manage Artifact: Inspect, download a ZIP archive of, or permanently delete a workflow artifact.
List Workflows: List GitHub Actions workflows defined in a repository.
Manage Caches: List, inspect, and delete GitHub Actions caches for a repository.
Manage Runners: List, inspect, remove, and manage self-hosted runners at the repository or organization level.
Manage Permissions: Get or set GitHub Actions permissions for a repository.
Get Workflow Run Logs: Download workflow run logs as a ZIP archive or individual job logs as text.
List Workflow Runs: List workflow runs for a repository, optionally filtered by a specific workflow, branch, event, status, or actor.
Manage Workflow State: Enable or disable a GitHub Actions workflow.
Get Current User: Identify the GitHub user represented by the connected OAuth token or personal access token.
And 1 more on the GitHub Actions MCP server page.

Turn Metorial on for a conversation with the + button, then Connectors; each connector has its own toggle.
Claude asks before it runs a GitHub Actions tool. Choose Allow always only for tools you trust to run unsupervised.
Use the Search and tools menu to switch off tools you do not need in the current conversation.
Remove the connector from Customize, then Connectors. Team and Enterprise owners can do this for the whole organization.

Members on a Team or Enterprise plan cannot add the connector: On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.
The Free plan only allows one custom connector: One is enough: your Metorial URL carries every app your team approves, so you never need a second connector.
Tools do not show up in a chat: Connectors are switched on per conversation. Open the + menu in the chat, choose Connectors, and turn Metorial on.

Based on the Claude MCP documentation.

Frequently asked questions

Common questions about connecting GitHub Actions to AI agents with Metorial.

Does Claude support the GitHub Actions MCP server?
Yes. Claude connects to the GitHub Actions MCP server through its connector settings, pointed at your Metorial URL. You need any Claude plan; Free plans allow one custom connector.
Do I need an API key to connect GitHub Actions to Claude?
No. You sign in to GitHub Actions once through Metorial, and Claude uses that connection. No API keys go into Claude's settings.
Which GitHub Actions tools can Claude use?
All 16 GitHub Actions tools your team allows, such as Manage Secrets, Control Workflow Run, Trigger Workflow. Admins can narrow that list per team.
Can I control which teammates use GitHub Actions in Claude?
Yes. Role-based access control decides who can use GitHub Actions and which of its tools appear in Claude, and every call is logged with the person's identity.
What if Claude doesn't show GitHub Actions tools?
On Team and Enterprise plans an Owner adds custom connectors in Organization settings, then Connectors. Members then connect it with their own account.