Does Codex support the GitHub Actions MCP server?

Yes. Codex connects to the GitHub Actions MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.

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

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

Which GitHub Actions tools can Codex 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 Codex?

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

What if Codex doesn't show GitHub Actions tools?

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Connect GitHub Actions to Codex (MCP setup guide)

Ask Codex to use the manage variables tool in GitHub Actions
Ask Codex to use the list artifacts tool in GitHub Actions
Ask Codex to use the manage artifact tool in GitHub Actions
Ask Codex to use the list workflows tool in GitHub Actions
Ask Codex to use the manage caches 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 the server and sign in
The Codex CLI, IDE extension and ChatGPT desktop app share this config.
```
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
```
3. Check the connection
Type /mcp in Codex to see Metorial and its GitHub Actions tools.

Once GitHub Actions is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, 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.

Limit which GitHub Actions tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
Type /mcp in the composer to see the connected servers.
Override the approval behavior for a single GitHub Actions tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing: Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.
Metorial times out at startup: Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.
Long tool calls fail after a minute: The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.

Frequently asked questions

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

Does Codex support the GitHub Actions MCP server?
Yes. Codex connects to the GitHub Actions MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
Do I need an API key to connect GitHub Actions to Codex?
No. You sign in to GitHub Actions once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which GitHub Actions tools can Codex 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 Codex?
Yes. Role-based access control decides who can use GitHub Actions and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show GitHub Actions tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.